Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_2019_sp_banner.thumb.jpg.a0ff260c05b90dead5c594e9b4ee9fd0.jpg

IanL

Script to make Stellarium easier to use with EQMOD

Recommended Posts

I have worked up a script to make it easier to use Stellarium with EQMOD. At the moment, issuing a commands to EQMOD from Stellarium requires one to press the CTRL key and a number key, specifically CTRL-1 to slew to the selected target, CTRL-3 to Sync to the current target and CTRL-5 to cancel the slew. I find this rather inconvenient when working in the dark, on a small notebook keypad and with gloves on.

It is believed that in forthcoming versions of Stellarium (e.g. v0.12.x) it will be possible to re-map the telescope control keys. Even so, I'd prefer to use my wireless game pad for the job, as it has chunky buttons, is portable and already works with EQMOD to control scope pointing and other functions. About a year ago I read somewhere that a free utility called AutoHotkey can be used to assist with this, so I bookmarked the download page, but never took it any further (and can't find the original source of the info amongst my many bookmarks).

Finally I got round to working on the issue, and here is my solution:

You will need the following:

- A working installation of EQMOD, StellariumScope and Stellarium.

- A compatible gamepad, joystick or similar controller. Test this in EQMOD first under the game pad configuration screen.

- Download and install a copy of AutoHotkey from http://www.autohotkey.com/ .

The AutoHotkey installation is pretty simple, just follow the instructions. Now you need to create your Stellarium AutoHotkey script. To do this:

1. Open NotePad.

2. Cut and paste the script below in to NotePad.

3. Save the file somewhere convenient (e.g. the desktop). Make sure you give the file name the extension .ahk and not the default .txt that NotePad suggests. This will ensure that the script launches AutoHotkey when you double click it, and it also adds an 'edit script' option to the Windows right-click context menu which makes life a bit easier when debugging.

4. Plug in or switch on your game pad/controller. The script will auto-detect the first joystick/controller and use that one, or pop up an error and quit if it can't find a controller. (See below in configuration for help if this happens).

5. Double click the script file and AutoHotkey should launch and put a small 'H' icon in the system tray at the bottom right of the screen to show this script is running. You can right-click the system tray icon to pause or stop the script, or to re-load it from the file if you have edited it during testing.

6. If you get any errors at this point, make sure you have pasted the script exactly as shown below!

All the configurable values are in the CONFIGURATION section of the script. Here are the things you may want to change:

- StellariumWindow holds the window title of Stellarium. The default setting should match any version, but if the window title changes in future, just edit this value. You can either use the whole window title or just some text from the start. Make sure the text doesn't match multiple windows (e.g. StellariumScope might clash if you only used the first few letters).

- JoystickNumber is set to 0 by default, which means "search all controllers and use the first one you find". If you have several controllers connected, you can set this value to the specific controller number (between 1 and 16) and the script will use that one.

- SlewButton / SyncButton / CancelButton hold the button names to activate each of the three functions. These will be in the format of Joy<n> where <n> is a number between 1 and 32. To find out which button is which on your controller, download the joystick test script here (http://www.autohotke...oystickTest.htm) and run it, but make sure you exit the Stellarium script first. A tool-tip will appear and update as you press the various keys on your controller so you can see which button is which. Again make sure you quit the joystick test script when done to avoid conflicts with the Stellarium AutoHotkey script.

IMPORTANT: Make sure you DO NOT use the SlewButton and SyncButton in the EQMOD game pad configuration screen. If you do, you may find EQMOD ends up doing two things at once, since (for controller keys), AutoHotkey activates its script AND passes the controller button press through to any other application that is waiting for it. Conversely, you may wish to map your chosen CancelButton to 'Emergency Stop' in EQMOD. This will ensure that the mount stops (and parks in the current position) even if your script, AutoHotkey or Stellarium/StellariumScope fails for some reason. Safety first.

See below for an example of how I have configured the EQMOD game pad screen for my XBox wireless controller:

post-18840-0-04114100-1362932023_thumb.p

I'd also recommend turning on 'Append on Sync' in EQMOD to add alignment points to the pointing model as you go.

- SlewKeys / SyncKeys / CancelKeys hold the keystrokes to sent to Stellarium when you press the appropriate controller button. These are set to the current CTRL-1, CTRL-3, CTRL-5 defaults. If you change these defaults once key mapping becomes available in Stellarium, you'll need to change these values. Read the AutoHotkey documentation online for details of how to send keystrokes.

The default script is set up for an XBox wireless controller, and uses the Blue ( X ) key to initiate a slew, the Yellow ( Y ) key to do a sync and the Red ( B ) key for cancel in Stellarium AND ALSO emergency stop in EQMOD. Change these to suit your own needs.


; Stellarium AutoHotkey script for Windows
; V1.0b 2012-03-09 - Ian Lauwerys.
; Joystick detection code taken from the AHK joystick test script.
;
; Go to http://www.autohotkey.com/ to download AutoHotkey.
; Create a text file containing this script (using notepad).
; Save it with the .ahk file extension (not .txt).
; Double click script to launch AutoHotkey and activate script.
;
; You will also need the following software (but I assume you knew that anyway!):
;
; EQMOD - http://eq-mod.sourceforge.net/
; Stellariumscope - http://www.welshdragoncomputing.ca/index.php?option=com_content&view=category&layout=blog&id=31&Itemid=39
; Stellarium - http://www.stellarium.org/
;
; This script assumes you are using the default key mappings in Stellarium/StellariumScope.
; As of V12.0 of Stellarium ; it is possible to remap keys so if you change the Slew,
; Sync or Cancel key mappings you need to update the configuration section below.

; ------------------ CONFIGURATION SECTION -------------------

; ** Configure the title of the Stellarium window. **
; ** Needs the trailing space to avoid matching StellariumScope **
StellariumWindow := "Stellarium "

; ** To autodetect and use the first joystick, set to 0 . **
; ** To use a specific joystick, set to a value between 1 - 16 . **
JoystickNumber := 0

; ** Configure joystick buttons (Joy1 through Joy32) to perform the required actions. **
; ** Download and run http://www.autohotkey.com/docs/scripts/JoystickTest.htm **
; ** to identify the key numbers for your joystick or contoller. **

; Joy3 (XBox Blue/X) for Slew.
; It is recommended that you do not map this button to anything in EQMOD.
SlewButton = Joy3

; Joy4 (XBox Yellow/Y) for Sync.
; It is recommended that you do not map this button to anything in EQMOD.
SyncButton = Joy4

; Joy 2 (XBox Red/B) for Cancel.
; It is recommeded that you map this button to 'Emergency Stop' in EQMOD for safety
; as AutoHotkey will pass controller buttons through.
CancelButton = Joy2

; ** Configure the keystrokes to send to Stellarium. **
; ** Change these if you remap keys in Stellarium V12.0 or later. **

; Send ctrl-1 to Stellarium (Slew).
SlewKeys = ^1

; Send ctrl-3 to Stellarium (Sync).
SyncKeys = ^3

; Send ctrl-5 to Stellarium (Cancel).
CancelKeys = ^5

; -------------- END OF CONFIGURATION SECTION ----------------

; ------------------ INITIALISATION SECTION ------------------

; Set hotkey variables.
If JoystickNumber = 0
{
JoystickNumber := DetectJoystick()
}

SlewHK = %JoystickNumber%%SlewButton%
SyncHK = %JoystickNumber%%SyncButton%
CancelHK = %JoystickNumber%%CancelButton%

; Set to match WinTitle "starting with string".
SetTitleMatchMode, 1

; Define hotkeys based on variables, will goto specified labels when pressed.
Hotkey, %SlewHK%, Slew
Hotkey, %SyncHK%, Sync
Hotkey, %CancelHK%, Cancel
return

; -------------- END OF INITIALISATION SECTION ----------------

; ------------------------- FUNCTIONS -------------------------

; Auto-detect the joystick number.
DetectJoystick()
{
Loop 16 ; Query each joystick number to find out which ones exist.
{
GetKeyState, JoyName, %A_Index%JoyName
if JoyName <>
{
TempJoystickNumber = %A_Index%
break
}
}
if TempJoystickNumber <= 0
{
MsgBox The system does not appear to have any joysticks.
ExitApp
}
return TempJoystickNumber
}

; --------------------- END OF FUNCTIONS ----------------------

; ---------------------- HOTKEY ACTIONS -----------------------

; Make Stellarium issue a Slew to selected target command to EQMOD.
Slew:
IfWinExist, %StellariumWindow%
{
WinActivate
SendInput %SlewKeys%
}
return

; Make Stellarium issue a Sync to EQMOD.
Sync:
IfWinExist, %StellariumWindow%
{
WinActivate
SendInput %SyncKeys%
}
return

; Make Stellarium issue a Cancel to EQMOD (stop current slew).
Cancel:
IfWinExist, %StellariumWindow%
{
WinActivate
SendInput %CancelKeys%
}
return

; ----------------- END OF HOTKEY ACTIONS ---------------------
Edited by IanL

Share this post


Link to post
Share on other sites

You don't really need the script to handle stop and sync as you can already assign gamepad buttons within EQMOD to those functions (the sync requires a double tap to prevent accidental syncs). Neat way to trigger the slew though!

Chris.

Share this post


Link to post
Share on other sites

You don't really need the script to handle stop and sync as you can already assign gamepad buttons within EQMOD to those functions (the sync requires a double tap to prevent accidental syncs). Neat way to trigger the slew though!

Chris,

I've not dived in to the innards of ASCOM other than a few of the pulse guide commands when I made my hombrew autoguider for the LX10 mount a while ago:

- If emergency stop is hit in EQMOD, I assume from what you say that Stellarium will know the mount has stopped and not end up confused. It just seemed neater to my mind to have the software that originated the slew command also initiate the cancel, but looks unnecessary if using a controller to do the job.

- Ditto with the sync; again if sync is triggered in EQMOD is that the same as doing it in Stellarium? What does the Sync process do anyway? I guessed that the mount driver would calculate the current RA and Dec based on the encoder values, (or maye hold Alt/Az which it could transform to/from RA/Dec based on time/site info). When an application does a sync it tells the mount driver that it is actually pointing at some different RA and Dec, causing the mount driver to adjust the encoder to pointing position transformation (and in EQMOD also the pointing model if append on sync is selected). So that led me to assume that the application has to initiate the sync, not the mount driver. I mean what happens if you have two applications connected to the mount driver (say Stellarium and AstroTortilla)? They may have different ideas about where the scope is really pointing, which is fine if the application is sending the sync data since you the user has to decide which application is right. If the mount driver initiates the sync process, how does it decide which application should respond, or if they all respond, how does it mediate between different values being sent by different applications? Lot's of assumptions based on no information, kind of my job description in real life to be honest!

Anyway I digress. You can amend the script easily enough to remove the mapping of unwanted commands. Also, in response to your original plea about ctrl-1, etc. you could just use AutoHotkey to replace these with more useful key cominations. Again this may not be needed in the V0.12.x of Stelarium if native keymapping works and we move beyond beta support in StellariumScope, but in the meantime here is an (UNTESTED) example using the F1, F2, F3 keys (slightly more verbose than it needs to be, but I am keeping the separation between configuration and code for ease of comparison):


; Stellarium AutoHotkey script for Windows
; V1.1b 2012-03-11 - Ian Lauwerys.
;
; Go to http://www.autohotkey.com/ to download AutoHotkey.
; Create a text file containing this script (using notepad).
; Save it with the .ahk file extension (not .txt).
; Double click script to launch AutoHotkey and activate script.
;
; You will also need the following software (but I assume you knew that anyway!):
;
; EQMOD - http://eq-mod.sourceforge.net/
; Stellariumscope - http://www.welshdragoncomputing.ca/index.php?option=com_content&view=category&layout=blog&id=31&Itemid=39
; Stellarium - http://www.stellarium.org/
;
; This script assumes you are using the default key mappings in Stellarium/StellariumScope.
; As of V12.0 of Stellarium ; it is possible to remap keys so if you change the Slew,
; Sync or Cancel key mappings you need to update the configuration section below.

; ------------------ CONFIGURATION SECTION -------------------

; ** Configure the title of the Stellarium window. **
; ** Needs the trailing space to avoid matching StellariumScope **
StellariumWindow := "Stellarium "

; ** Configure keys to perform the required actions. **
; ** Got to http://www.autohotkey.com/docs/KeyList.htm for a list of key codes. **

; F1 for Slew.
SlewButton = F1

; F2 for Sync.
SyncButton = F2

; F3 for Cancel.
CancelButton = F3

; ** Configure the keystrokes to send to Stellarium. **
; ** Change these if you remap keys in Stellarium V12.0 or later. **

; Send ctrl-1 to Stellarium (Slew).
SlewKeys = ^1

; Send ctrl-3 to Stellarium (Sync).
SyncKeys = ^3

; Send ctrl-5 to Stellarium (Cancel).
CancelKeys = ^5

; -------------- END OF CONFIGURATION SECTION ----------------

; ------------------ INITIALISATION SECTION ------------------
SlewHK = %SlewButton%
SyncHK = %SyncButton%
CancelHK = %CancelButton%

; Set to match WinTitle "starting with string".
SetTitleMatchMode, 1

; Define hotkeys based on variables, will goto specified labels when pressed.
Hotkey, %SlewHK%, Slew
Hotkey, %SyncHK%, Sync
Hotkey, %CancelHK%, Cancel
return

; -------------- END OF INITIALISATION SECTION ----------------

; ---------------------- HOTKEY ACTIONS -----------------------

; Make Stellarium issue a Slew to selected target command to EQMOD.
Slew:
IfWinExist, %StellariumWindow%
{
WinActivate
SendInput %SlewKeys%
}
return

; Make Stellarium issue a Sync to EQMOD.
Sync:
IfWinExist, %StellariumWindow%
{
WinActivate
SendInput %SyncKeys%
}
return

; Make Stellarium issue a Cancel to EQMOD (stop current slew).
Cancel:
IfWinExist, %StellariumWindow%
{
WinActivate
SendInput %CancelKeys%
}
return

; ----------------- END OF HOTKEY ACTIONS ---------------------
Edited by IanL

Share this post


Link to post
Share on other sites

- If emergency stop is hit in EQMOD, I assume from what you say that Stellarium will know the mount has stopped and not end up confused. It just seemed neater to my mind to have the software that originated the slew command also initiate the cancel, but looks unnecessary if using a controller to do the job.

Stellarium doesn't really know much of what is going on with the mount - it just polls out for the mounts current RA/DEC coords. So if the mount stops because some one hits the emergecy stop button on EQMOD, or a gamepad or indeed if any other ASCOM client software then the telescope reticule in stellarium will remain at th estopped position.

- Ditto with the sync; again if sync is triggered in EQMOD is that the same as doing it in Stellarium? What does the Sync process do anyway? I guessed that the mount driver would calculate the current RA and Dec based on the encoder values, (or maye hold Alt/Az which it could transform to/from RA/Dec based on time/site info). When an application does a sync it tells the mount driver that it is actually pointing at some different RA and Dec, causing the mount driver to adjust the encoder to pointing position transformation (and in EQMOD also the pointing model if append on sync is selected). So that led me to assume that the application has to initiate the sync, not the mount driver. I mean what happens if you have two applications connected to the mount driver (say Stellarium and AstroTortilla)? They may have different ideas about where the scope is really pointing, which is fine if the application is sending the sync data since you the user has to decide which application is right. If the mount driver initiates the sync process, how does it decide which application should respond, or if they all respond, how does it mediate between different values being sent by different applications? Lot's of assumptions based on no information, kind of my job description in real life to be honest!

Again stellarium is quite dumb when is comes to provding a sync - in fact it has no idea it is even doing it!. The only mount control action stellearium currently ,has is to issue gotos so when the sync ctrl key is pressed stellarium initiates a virtual telescope goto to the objects coordinate. Stellariumscope recieves this goto and issues a sync to EQASCOM using the goto coordinates as the sync point. The cancel/stop is te same, stellarium issues a goto but to another vitual scope that stellariumscope intercepts and issues the ASCOM stop.

A sync simply tells you the coordinates of where you are right now and when you think about it EQASCOM is already aware of that - the coordinates of the last received goto are the sync point!. So whenever you issue a goto EQASCOM makes a mental note of where you aked it to go - you then do what you must to centre the sync point in an eyepeice and should you hit the gamepad sync button (twice in faily rapid sucession) eqascom issues a sync to itself using the last goto coordinates.

When a sync is made, no matter who initiates it, eqascom's pointing model is modified/shifted and as a consequence the currently reported RA/DEC coords will change slightly. All connected applications will pick up this change as soon as they next poll eqascom. There is never any questions of EQASCOM serving up different data to different applications. Also catalogue positions used for sync points / goto targets should be identical across all applications provided they have bben setup to use the same epoch (which you would want to be doing anyhow).

Chris.

  • Like 2

Share this post


Link to post
Share on other sites

This is really interesting! I think I'll stop syncing with Stellarium because it is p***ing me off...

It never syncs back to the star.

But, if you sync EQMOD, who tells Stellarium?

Share this post


Link to post
Share on other sites

But, if you sync EQMOD, who tells Stellarium?

A sync will act to change where EQASCOM reports the mount is. When stellarium polls to read the current mount RA/DEC coords the sync will have caused them to change and stellarium will draw the mount reticule at the mew position. In this respect Stellarium can't distinguish between a sync having occurred or a manual slew by the user - but it doesn't need to. Just keep in mind that stellarium is little more than a glorified catalog with a pretty front end - it really knows nothing of mount control.

Chris.

Share this post


Link to post
Share on other sites

Guys, I did a search for Stellearium telescope control and this was one of the threads that google threw up.  What puzzles me is most of the other software that is free (C2A, CDC etc) support the ASCOM platform and have the same sort of menu options by right clicking on a target to slew and sync.  Whilst I can understand that Stellariums developers may not have the time, internet connection speed or the other reasons for not being able to develop the application to support the ASCOM platform, given it's popularity I would of thought that this would of been added by now.  Reading some of the posts and discussions Chris has already commented how to use sockets to something, and even offered to collaborate or develop a suitable plug-in or telescope interface.  Could I suggest to the developers that they seriously consider adding ASCOM support as a priority, and if time, effort or slow PC's are the issue, then maybe Chris could assist...??

In the meantime I'll continue to use CDC until this issue with Stellarium is resolved.

Share this post


Link to post
Share on other sites

Guys, I did a search for Stellearium telescope control and this was one of the threads that google threw up.  What puzzles me is most of the other software that is free (C2A, CDC etc) support the ASCOM platform and have the same sort of menu options by right clicking on a target to slew and sync.  Whilst I can understand that Stellariums developers may not have the time, internet connection speed or the other reasons for not being able to develop the application to support the ASCOM platform, given it's popularity I would of thought that this would of been added by now.  Reading some of the posts and discussions Chris has already commented how to use sockets to something, and even offered to collaborate or develop a suitable plug-in or telescope interface.  Could I suggest to the developers that they seriously consider adding ASCOM support as a priority, and if time, effort or slow PC's are the issue, then maybe Chris could assist...??

In the meantime I'll continue to use CDC until this issue with Stellarium is resolved.

I think it is worth bearing in mind a few things:

- Stellarium is a planetarium first and foremost.  The fact that it has some very basic telescope support is great, but as far as I can see it was never intended to be a telescope control application and I doubt that the current developers have the time and resource to get involved in the difficulties of trying to support advanced telescope control.  The current way it is done is very simplistic (go to coordinate command for each telescope, hence the need for StellariumScope to pretend to be three different scopes so it can do slew, sync, stop).

- It is a cross-platform development with support for Windows, Mac and Linux.  ASCOM is a Windows-only offering (necessarily so).  I would guess it would be difficult/impossible for them to build ASCOM support directly in to the product without forking it in to several versions for different platforms.  I haven't looked at the way plugins are developed and I don't know if ASCOM could be built in to a plugin or not.  I suspect not since StellariumScope is a separate application and if it was easy to build an ASCOM plugin I guess that is what would have been done instead.

- That said the combination of Stellarium and StellariumScope works flawlessly, and the only bugbear is the inability to change key mappings for scope control in Stellarium itself.  This was rumoured to be a new feature in an upcoming version, but I haven't checked to see if it is possible yet.  Using AutoHotKey is a bit of a cheat to allow this in lieu of such a feature.  Even if they do add key mapping, I doubt they will add support for GamePads, etc. as that is (again) a Windows Platform specific issue.  (By way of analogy Stellarium uses cross-plaform OpenGL for graphics rather than DirectX which is Windows-only so not going to be built in for the same reasons as above, and control of gamepads faces a similar issue in Windows).

- I think the killer point that one of the developers made when someone else was saying 'why don't you do xyx..???' was that this is an open source project.  If you have the development skills and want to contribute, jump in and help out, but they are reliant on a handful of people with limited time to contribute and all the theorising in the world about how great it would be to do x or how obviously dumb it is not to support y doesn't really help them move it on.

Personally I am grateful for such a great free piece of software, I have neither the time nor the specific skills to help (I can hack my way around in HTML and JavaScript quite well for someone from the pre-windows/pre-web era of software development, but heavyweight graphics applications are not something I could tackle).  Thus I am willing to accept what I am given; unless you've ever done serious software development it is hard to appreciate just how much time and effort it takes to build and test even simple features in a large application like this whilst ensuring a decent level of quality.  I manage two teams of developers who write far less complex software for a living and it is extremely hard to get acceptable good stuff out of the door in a timely manner, never mind a bunch of people doing it in their spare time for goodwill only and scattered across several continents.

Edited by IanL

Share this post


Link to post
Share on other sites

Don't get me wrong, I think the developers are doing a grand job, and whilst the application may well of been a planetarium program in concept, which it does very well, it does seem left behind given that goto telescopes have been around for many years now and other free apps of this type integrate with a recognised control platform to provide telescope control.  I appreciate that it may be a difficult task, and if I had the knowledge to program in windows I would be first to be offering my assistance, but sadly my programming skills are somewhat limited and not in this field.

As for cross platform, well I guess that if the developers did offer an Ascom interface there would be those on Linux who would want the same under INDI, and probably Mac uses after whatever "standard" runs native on the mac OS.... maybe this is why no direct support for telescope control from within the application has been undertaken.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By alexwolf
      The second bugfix release for series 0.19.
      Thank you very much to community for bug reports, feature requests and contributions!
      Full list of changes between versions 0.19.1 and 0.19.2:
      - Added support DMS and DD formats for parallactic angle feature
      - Added altitude limitation filter for AstroCalc/Graphs[AltVsTime/ME] tools
      - Added visual improvements for AstroCalc/Graphs tool
      - Added new time intervals for AstroCalc/Ephemeris tool
      - Added computation of ephemeris for all naked-eye visible planets into AstroCalc/Ephemeris tool
      - Added GUI for select the color of ephemeris markers into AstroCalc/Ephemeris tool
      - Added 2 new scripts (Saturnian and uranian analemmas)
      - Added 'k Pup' designation to star HIP 37229 (GH: #706)
      - Added information about progress of loading on splash screen (GH: #719)
      - Added a new skylore for Stellarium: Anutan
      - Added support catalog "Southern Stars embedded in nebulosity" (Van den Bergh and Herbst, 1975 - VdBH)
      - Added support "Catalogue and distances of optically visible H II regions" (Dickel+, 1969 - DWB)
      - Added distances for few LDN objects
      - Added support removing shortcuts through config.ini file (GH: #724)
      - Added extraInfoString to StelObject: Allows extra info injected by plugins or scripts.
      - Added display of Apex/Antapex points (GH: #737)
      - Added "observers" for all planets with moons (GH: #736)
      - Added IAU constellation abbreviation to object info
      - Added 3 new actions
      - Added settings for Script Console (GH: #741)
      - Added Vanuatu (Netwar) skyculture (GH: #762)
      - Added few asterisms (GH: #753, #768)
      - Added new one time step into AstroCalc/Ephemeris tool (GH: #758)
      - Added few new DSO textures (GH: #756, #780)
      - Added support Vec3d into scripting engine
      - Added a Messier Marathon script (GH: #771)
      - Added support for short weekday display modes in bottom toolbar
      - Added GUI option to toggle permanent orbit drawing
      - Added hyperbolic comet C/2019 Q4 (Borisov) [2I/Borisov] into default ssystem_minor.ini file
      - Added a scripting function for refraction (GH: #778)
      - Fixed coloring text issue when formatting output is on
      - Fixed saving properties for external software/remote computer in Telescope Control plugin (GH: #702)
      - Fixed behaviour of selected ephemeris marker when sorting not for date (AstroCalc/Ephemeris tool)
      - Fixed sorting date and time columns for AstroCalc/Ephemeris and AstroCalc/Phenomena tools
      - Fixed crash on destruction of static QWidget (GH: #720)
      - Fixed small difference of values issue for different time zones for Date and Time column in AstroCalc/Ephemeris tool (GH: #717)
      - Fixed stupid conversion bug in hmsToRad function (GH: #716)
      - Fixed an asymmetry w.r.t. to the ecliptic latitudes (Moon age)
      - Fixed Search Tool/Lists behaviour for VdBH catalog
      - Fixed distances for few DSO (GH: #708)
      - Fixed Gregorian date issue for AstroCalc (GH: #711)
      - Fixed support GPS on macOS (GH: #712)
      - Fixed coefficient for the duration of mean tropical year
      - Fixed issue for images in description for landscapes: set search directory (GH: #735)
      - Fixed tooltip behaviour for Date and Time dialog
      - Fixed star name to its source spelling (GH: #729)
      - Fixed compiling with GPSD 3.19 [API 8.0] (GH: #733)
      - Fixed encoding script files in Script Console (GH: #742)
      - Fixed drawing names of asterisms
      - Fixed aFOV display in Oculars plugin
      - Fixed visual issue in Script Console (white background) with Qt 5.13
      - Fixed links for scripting docs (SUG)
      - Fixed screen flashing during solar eclipse (GH: #747)
      - Fixed core.resetOutput(); method behaviour (GH: #750)
      - Fixed AltGr behaviour for some languages on Windows
      - Fixed clipping issue for LabelMgr.labelObject (GH: #776)
      - Fixed weekday computation
      - Fixed rendering planets orbits (GH: #773)
      - Fixed error in shape of asterism Red-Necked Emu (GH: #769)
      - Fixed proper removing of default secondary shortcut (GH: #764)
      - Fixed cross-id error in DSO catalog
      - Updated appdata.xml file
      - Updated outdated code for names of days and months
      - Updated Observability plugin
      - Updated list of proper names of stars (IAU approved list)
      - Updated Moon age calculation: let's use geocentric coordinates only for compute of the Moon age
      - Updated AstroCalc/PC tool: simplification and colorification for graphs
      - Updated AstroCalc/Phenomena tool: small speed-up
      - Updated the default color space: StelToneReproducer now use sRGB as target RGB color space (GH: #718)
      - Updated GUI for Satellites plugin
      - Updated common names for DSO
      - Updated common names for stars
      - Updated packaging for macOS: Let's use macdeployqt for creating a MacOS bundles
      - Updated nomenclature support: Let's use compressed nomenclature data to reduce an installation package
      - Updated translations
      - Updated planetary nomenclature
      - Updated Sardinian skyculture
      - Updated file handling in Script Console
      - Updated HDPI features: enabled scaling fonts on High DPI monitors (GH: #546)
      - Updated default shortcuts: changed default shortcut for copying selected object information (Ctrl+C -> Ctrl+Shift+C) to allow use Ctrl+C shortcut for text edit fields for whole planetarium (GH: #748)
      - Updated getInfoMap method [scripting engine]: enhanced the getInfoMap method for the Sun (get eclipse data; GH: #747)
      - Updated Chinese (Simplified) and Russian translations for Windows installer (GH: #755, #779)
      - Updated Bookmarks tool
      - Updated default exoplanets and pulsars catalogs
      - Updated behaviour on Windows: disable HiDPI scaling in manifest (GH: #763)
      - Updated Oculars plugin: improve RA/Dec output for CCD frame
      - Code refactoring: type checking/casting clarifications
      - Removed FOV plugin (the feature was moved into core of planetarium)
      Homepage + links to downloading binary packages: https://stellarium.org
    • By dragorom7
      Hello, i am new to this forum, i made my account here because i need help.
      So few weeks ago i ordered a USB to Serial cable to be able to Control my Telescope with my computer using stellarium.
      It arrived today.
      So i made my Star Alignment, then i plugged the cable to my Telescope and Computer, i installed the Cable driver and ASCOM Platform + ASCOM Celestron Driver.
      I started DriverConnect.exe and put the Celestron Driver i downloaded, and did the properties informations ( had to tick on "Advanced Setup" and "Show All COM Ports" ) and i put "COM8" on "COM Port", then i pressed "OK" and then "Connect"
      Result:
      Create              Creating device
      Connected           Connecting to device
      Error               System.Exception: Connect to COM1 failed, no Celestron scope detected
         to System.Dynamic.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, UInt32 argErr, String message)
         to CallSite.Target(Closure , CallSite , ComObject , Boolean )
         to ASCOM.DriverConnect.ConnectForm.btnConnect_Click(Object sender, EventArgs e) in C:\ASCOM Build\Export\ASCOM.DriverConnect\ConnectForm.cs:line 268
      Dispose             Disposing of device
      ReleaseComObject    Releasing COM instance
      ReleaseComObject    Completed release. Count: 0
      GC Collect          Starting garbage collection
      GC Collect          Completed garbage collection
       
      "Connect to COM1 failed, no Celestron scope detected"

      In Stellarium i set-up everything, the plug-in and restarted the app, then added my telescope  and i says it's "connected" but i can't find my telescope.
       
      Telescope:
      Celestron NexStar 127SLT
      The Cable i bought:
      https://www.amazon.com/Telescope-CP2102-Adapter-Control-Console/dp/B077G37VL1/
      PC Specs:
      Windows 10 Pro, GTX 970, 8GB Ram(DDR4), i7 6700 3.4Ghz
       
      Looking forward for your help, thanks in advance,
      dragorom7.
    • By PlanetGazer
      So I'm referring to the main astro-softwares that you use during your sessions on your phone or tablet, and found that most of people use mainly those two softwares on their phones. Laptop versions of the software are different products and are not the focus of this topic.
      So which do you use and why?
       
      My experience:
      I personally have Stellarium plus, and the free version of SkySafarai, so I have an understanding of how the user-interface of both works, I have been researching the extra features in the SkySafari Pro, and have figured the following so far (please correct me if I'm wrong):
      * I'm aware that both let you control your GoTo telescopes
      * I personally find current version of Stellarium to be more user friendly and easier to navigate the sky manually , could be the configured settings though
      * SkySafari has more options to the search bar, e.g. "Tonight's Best" based on your location, also a menu of Messier catalog with a highlight of those currently visible at your time and location, others like best deep sky objects
      * SkySafari has this wonderful feature of creating an observing list, very helpful to plan your session and share and download with/from others
      * Stellarium Plus has a database of around 1.69 billion stars,while SkySafari 6 Pro has around 100 milion starts (don't think it's important as most of them aren't visible in amateur telescopes, I think I read somewhere that only 25 million stars are possible to observe with our telescopes, up to 15th mag, wonder if any of you have tried to push this limit)
    • By alexwolf
      The first correcting release for series 0.19 has been released today.
      Thank you very much to community for bug reports, feature requests and contributions!
      Full list of changes between versions 0.19.0 and 0.19.1:
      - Added allow to search an inactive meteor showers in Search Tool/Lists tool
      - Added 'Azimuth vs. Time' graph into AstroCalc/Graphs tool
      - Added feature to show tracks for latest several selected planets (GH: #539)
      - Added calculation and showing the orbital period for artificial satellites
      - Added revolutions per day info for artificial satellites
      - Added tools for jumping to the next or previous time of rising, transit or setting for selected object (GH: #484)
      - Added new behavoir for AstroCalc/Graphs when clicking within graph area now sets current time.
      - Added simplification in topocentric correction (GH: #391)
      - Added parallactic angle function (added it to infostring and infomap also)
      - Added hour angle and sidereal time to infomap
      - Added apply rotation when drawing Solar Corona (GH: #699)
      - Fixed draw corona when atmosphere is switched off
      - Fixed airmass in infomap
      - Fixed issue in script 'Mercury Triple Sunrise and Sunset'
      - Fixed crash of Stellarium for eyepieces with permanent crosshair
      - Fixed Stellarium crash when Remote Control plugin is working
      - Fixed computation of assume radius for minor planets.
      - Fixed the issue of the scrolling not working properly on Mac (GH: #393)
      - Fixed crash in Scripting Engine (Hide artificial satellites through StelProperties in core.clear() method to avoid crash if plugin was didn't loaded)
      - Fixed planetarium crash in HiPS (network manager delete problem)
      - Fixed position problems on the Poles (GH: #391)
      - Fixed scaling Telrad sign on HighDPI monitors
      - Fixed surface occlusion bug even with landscape turned off in scripting engine (GH: #680)
      - Fixed building with cmake -DBUILD_SHARED_LIBS=ON (GH: #683)
      - Fixed error in constellation file format (Babylonian)
      - Fixed Europe/Volgograd time zone settings (GH: #686)
      - Fixed HiPS handling of allsky download (GH: #671)
      - Fixed progress bar rendering (GH: #671)
      - Fixed positive declinations issue in AstroCalc tool when option 'Use decimal degrees' is enabled (GH: #690)
      - Fixed file names inconsistency
      - Fixed constellation line in "Japanese Moon Stations" skyculture
      - Fixed file name for constellation boundaries in Stellarium User Guide
      - Fixed the user interface problems in Oculars plug-in (GH: #580)
      - Fixed getting the wrong values in objects/info method for selected object for different formats (Remote Control plugin)
      - Fixed refresh plots when AstroCalc dialog becomes visible again (AstroCalc/Graphs tool)
      - Fixed jquery vulnerability (GH: #694)
      - Fixed date and time dialog behaviour: Hour/Minute/Second spinners now correctly trigger signals dateChanged(), dateChangedByYear and dateChangedForMonth() when days, months or years are affected by it.
      - Fixed update graphs in AstroCalc/Graphs tool when days change
      - Updated planetary nomenclature
      - Updated common names of stars and DSO's
      - Updated cmake rules for Windows deployment
      - Updated DSO textures
      - Updated behaviour of HiPS survey if Stellarium started without network (GH: #681)
      - Updated GUI for ArchaeoLines plugin (GH: #689, #682)
      - Updated default pulsars catalog (v1.60)
      - Updated list of asterisms
      - Updated AstroCalc tools: many optimizations
      - Excluded Armintxe skyculture and landscape from default package
      Homepage + links to downloading binary packages: https://stellarium.org
    • By alexwolf
      Hello!
      Today we published first release candidate to version 0.19.1 - please help us testing Stellarium!
      List of changes between version 0.19.0 and master (0.19.0.16926/0.19.1RC1):
      - Added allow to search an inactive meteor showers in Search Tool/Lists tool
      - Added 'Azimuth vs. Time' graph into AstroCalc/Graphs tool
      - Added feature to show tracks for latest several selected planets (GH: #539)
      - Added calculation and showing the orbital period for artificial satellites
      - Added revolutions per day info for artificial satellites
      - Added tools for jumping to the next or previous time of rising, transit or setting for selected object (GH: #484)
      - Added new behavoir for AstroCalc/Graphs when clicking within graph area now sets current time.
      - Fixed issue in script 'Mercury Triple Sunrise and Sunset'
      - Fixed crash of Stellarium for eyepieces with permanent crosshair
      - Fixed Stellarium crash when Remote Control plugin is working
      - Fixed computation of assume radius for minor planets.
      - Fixed the issue of the scrolling not working properly on Mac (GH: #393)
      - Fixed crash in Scripting Engine (Hide artificial satellites through StelProperties in core.clear() method to avoid crash if plugin was didn't loaded)
      - Fixed planetarium crash in HiPS (network manager delete problem)
      - Fixed position problems on the Poles (GH: #391)
      - Fixed scaling Telrad sign on HighDPI monitors
      - Fixed surface occlusion bug even with landscape turned off in scripting engine (GH: #680)
      - Fixed building with cmake -DBUILD_SHARED_LIBS=ON (GH: #683)
      - Fixed error in constellation file format (Babylonian)
      - Fixed Europe/Volgograd time zone settings (GH: #686)
      - Fixed HiPS handling of allsky download (GH: #671)
      - Fixed progress bar rendering (GH: #671)
      - Fixed positive declinations issue in AstroCalc tool when option 'Use decimal degrees' is enabled (GH: #690)
      - Fixed file names inconsistency
      - Fixed constellation line in "Japanese Moon Stations" skyculture
      - Fixed file name for constellation boundaries in Stellarium User Guide
      - Fixed the user interface problems in Oculars plug-in (GH: #580)
      - Fixed getting the wrong values in objects/info method for selected object for different formats (Remote Control plugin)
      - Fixed refresh plots when AstroCalc dialog becomes visible again (AstroCalc/Graphs tool)
      - Fixed jquery vulnerability (GH: #694)
      - Fixed date and time dialog behaviour: Hour/Minute/Second spinners now correctly trigger signals dateChanged(), dateChangedByYear and dateChangedForMonth() when days, months or years are affected by it.
      - Fixed update graphs in AstroCalc/Graphs tool when days change
      - Updated planetary nomenclature
      - Updated common names of stars and DSO's
      - Updated cmake rules for Windows deployment
      - Updated DSO textures
      - Updated behaviour of HiPS survey if Stellarium started without network (GH: #681)
      - Updated GUI for ArchaeoLines plugin (GH: #689, #682)
      - Updated default pulsars catalog (v1.60)
      - Updated list of asterisms
      - Excluded Armintxe skyculture and landscape from default package
      Download link: https://github.com/Stellarium/stellarium-data/releases/tag/beta
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.