So things were going smoothly the first time I fired up the dome and started to track my scope following my target in the east. I first did a routine alignment and then selected track my scope in ASCOM (Beaver) and sent the scope and dome to the same location. When I finally sent the scope to the home position, the dome followed as expected. About 10 seconds later, the dome went back to the eastern location it first went to. I told the dome to go home, and it did, then repeated its movement to the east, over and over again after sending it home.
I turned the scope off, closed the dome and turned off the shutter motor, at one point I even pulled the plug on the rotator and rebooted my PC. Every time I connect then select track the scope, the dome moves to the east even thought the scope is still at home (aligned with CNP) where the dome home location is located too.
How do I reset the dome, so it doesn't jump to a location it once followed the scope the first time I selected track. If I give the scope a new target, the dome moves but is always offset by the same ~90 degrees. I never set park, and it knows where home is.
BTW, when I first set up the dome and scope and hit track for the first time, the dome did not move until I gave the scope a target.
My equipment is a CGEM DX mount with an 11" Edge scope balanced in all directions. My offsets are all good.
HELP!
Steven
Well, I'm an idiot. It turns out that the diameter of the dome in the Dome setup was set to zero and once connected to the scope it defaults to azimuth 90. All the other offsets were set and once I corrected the diameter and the dome is slaved to the mount, the dome moves to the correct location. Still not clear on why the dome didn't follow the scope, even thought it would be way off, while the mount was slewing to a different position. Will work with NexDome if that starts up again in the future.
As far as the COMMS DOWN! message it appears to be related to the driver for the shutter overheating. In my case, it looks like the heat sink is missing from the Beaver board, which may be associated with the battery BMS shutting down.