I’ve been using the older Nexdome driver and when I issued a goto using Maxim DL , it would slew the dome at the same time as the mount, simultaneously . And if I issued the goto to CPWI program (direct control of CGX mount), immediately after moving the mount finished it would move the dome.
My mini Pc bit the dust so I had to replace it and rebuild all the drivers. So I installed the latest package from github. Now if I issue the goto from maxim or from cpwi, it slews the mount and the dome appears to do nothing for a couple minutes it gives. New ‘target azimuth’ but the ‘dome azimuth’ stays the same. It counts down ‘next move in’ 5 4 3 2 1 the does nothing and counts down from 5 repeatedly. After a couple minutes though it moves.
I actually only found out it would eventually move because I was sitting there trying to figure something else out and suddey the dome took off and slaved to the right point. Before that I had been just unclickng ‘slave’ and moving to azimuth manually.
To get it to respond to a manual move I had to hit ‘abort’ then I could manually input an azimuth and hit goto on the dome window.
So not being able to issue a manual command unless I hit abort first is what made me think the driver is hanging up on a typo or maybe too long of a counter in the code or waiting for an input.
Is is there maybe a bug in the ASCOM Driver or the rotator firmware that it will not move simultaneously?
Another possibility , I see in the Nexdome setup window that the dome voltage reports between 12V and 6.5V at times. Is this normal? Maybe this is causing the strange behavior?
Jasem has taken control of the indi driver and rewrote it for me. Logged in and hot swapped it on my machine. He awaits the new firmware for his final rewrite. = )
NexDome Setup_211E <--- what firmware is needed for this driver? I have 1.1 firmware installed due to the fact that I'm using INDI. I can swap back to the PC and SGP - but when I do my dome doesn't work. I'd need to find a driver that "works" with the 1.1 firmware. I'd like to be able to swap machines back and forth without reflashing.
I've never seen my voltage drop below 11 on the shutter. (rotator is a fixed voltage).
Be aware all new firmware and driver are currently in the works. month or two?
I tested with the driver you suggested. The dome was WAY more responsive. It reacted instantly to a goto and pointed correctly on both sides of the meridian. Whatever you did was it. Thanks a ton for the help.
The funny thing is I've been told the shutter controller has shipped. So I'll probably install it in a couple weeks. But at least till then my stuff will work. You can understand the frustration I'm sure when all the other equipment works but the dome doesn't line up. It leaves you pointing at a wall... Thanks for the help!
Can you try the new version uploaded as 'NexDome Setup_211E_NoShutter.exe' in the git repo in
can you check the setting and try disabling the shutter in ASCOM ?
Having to hit abort mean another command is in progress.. and as the shutter (in ASCOM) is enabled by default this might be the issue as something probably query the shutter state and wait for the answer for a long time and finally timeout.
Ok, so changing the PS will not solve the issue (it will at least make sure you have a properly working power supply).
As it slew properly when told to do so, the issue is not in the firmware as it react as soon as it gets a command.
So we need to look at the ASCOM part.
Ron and a few other have been testing it and using it successfully, but they have a shutter kit. Do you have one ?
Can you enable the trace and see if there is something in there that would put us on the right track ?
What is your voltage cut-off value ?
If you're using the power supply supplied by NexDome there is an issue with it as it goes in power saving mode and this will prevent the dome from moving.
Set the voltage cut-off to something like 5v (or less) and see if that solves the issue.
The real solution : https://www.amazon.com/gp/product/B013EU4AHQ/ref=oh_aui_search_asin_title?ie=UTF8&psc=1