Recently Browsing 0 members
No registered users viewing this page.
Has anyone had Stellarium move the mount reticle between the point the mount is actually pointing at to 0h00m00s - 0deg 0' 0" then after a random period of time move it back and forth and back and forth...?
I'm using a Sky-Watcher EQ6-R PRO directly connected to Windows 10 using a standard USB B cable. Then I have SynScan App Pro running connected to the mount on COM8. This works great and I can control all aspects of the mount without need for the handset. Then I've also got the ASCOM Telescope driver for SynScan App v18.104.22.168 installed. I can use the ASCOM Device Hub to connect to the ASCOM.SynScanMobile.Telescope driver and also control the mount from that.
When I then move over to Stellarium, it connects to the same ASCOM driver but then exhibits this strange movement behaviour and it does it whether the mount is tracking or not.
I'm using the latest Stellarium v0.21.1, ASCOM Platform 6.5 SP1 and the driver as specified above. Windows 10 is 100% up to date.
I've attached a short video clip of Stellarium. Initially I'm pointing at Polaris and it moves the reticule to 0/0 then back again. Then I slew and the reticule catches up to where I've moved the mount to but then again flicks back to 0/0.
I'm am new to this mount and setup so it's possible I've not set the mount up correctly. Note that I've only had it a couple of days and it's not yet made it outside so the "pointing at" part is "virtual" having set the mount to the home position only. It seems to be saying the correct RA/DEC in the SynScan App though from what I can tell.
Any ideas would be most welcomed.
Stellarium 0.21.1 2021-07-31 15-14-39_Trim.mp4
The Stellarium team are delighted to announce the release of Stellarium 0.21.1.
The major changes of this version:
- Updated designations of stars and handling of list of designations and common names those stars
- Updated Almagest and al-Sufi skycultures
- Many changes in plugins
- Many fixes in core and plugins for support HiDPI devices
- Enhancements in visualization of markings and in scripting engine
There have also been a large number of bug fixes and closes feature requests and enhancements (see full list of changes).
A huge thanks to the people who helped us a lot by reporting bugs!
Hello fellow astronomers, I have come to the forums as I have depleted all other options.
I own an NEQ5 GoTo with a Skywatcher 72ED. I have connected the mount to my computer using an EQDIRECT cable.
I am trying to use stellarium with ascom and eqmod to slew the mount to a desired object. I have configured my scope using the “telescope control” plugin in stellarium. In the past I had successfully achieved slewing through stellarium.
The problem is that now, one month later, when opening stellarium and trying to slew the telescope to a selected object (using either the “slew telescope to” panel or the shortcut (control + 1)) the mount moves for a fraction of a second and then stops, stellarium freezes and then the scope indicator in stellarium slides quickly to the horizon, and EQMOD control panel displays “horizon limit horizon limit” error. (Let’s call this the “main failure mode”.)
Note that :
I can use EQMOD and slew the scope manually without problem. If using it in tandem with stellarium, when I do so the scope indicator in stellarium moves without issue.
I have used the “resync encoders” button on EQMOD to establish the home position, but this does not affect the behavior.
I can use ascom device hub to slew the scope manually without a problem as well.
The main failure mode described above happens most of the time. However, I sometimes get other erratic behavior in stellarium:
Sometimes, when trying to slew the scope in stellarium, the mount moves for a second then stops (as described above), yet the scope indicator in stellarium moves to the selected object not the horizon, then the mount starts to track (even though it has not yet slewed).
Or, rarely, when trying to slew the scope in stellarium, the mount physically moves (seemingly to the object) and starts tracking, the scope indicator moves to the selected object -- appearing to work normally. But then, when trying to slew the scope a second time to a different object, it fails again as described in the main failure mode above.
I have tried opening stellarium as administrator but I still get one of the three outcomes when trying to slew.
Does anyone have any insight on this ?
Since I live in a flat I do most of my imaging from my balcony... I purposely choose a top floor because of my astrophotography passion in order to have a decent field of view, but my balcony has walls on one side and on top.
So I decided to bring to Stellarium my own landscape and my FOV so I can know exactly which targets are on sight and at what time.
I have done some reading and watch videos but I still have a couple of questions before I begin and hopefully some people from here could help!
a) how should I take my photo... Me standing straight levelled with horizon or placing my camera on a tripod and place it like a telescope looking up in the sky towards North?
b) the famous cardinal points and the line angle_rotatez= in the ini file... Is there a secret of finding this number easy in order to match cardinal points to my photo or the only way is by trial and error....?
Thanks for reading
I have a few questions regarding mount control using stellarium that I can't seem to find elsewhere.
I have an EQ3 pro with with Syscan (handcontrol) and a laptop with stellarium.
The articles I've read refer either to EQMOD or ASCOM as a download requirement for Stellarium, is there any preference here for the EQ3?
I'm also struggling to find details of the correct cable to connect the mount straight into the computer via USB (and which port recieves this in the mount).
Thinking ahead, considering the requirement for the Guidscope and DSLR to be pugged into the computer, I will need to ensure this cable would be compatible with a "USB hub" (an area I havent done any research into yet). My computer has only 2 USB ports!