I managed to get to site to look at this further. What was strange is I couldn't slew to anything to the West without getting an interrupt message. I checked the controller, and internals to make sure there was no corrosion. I also checked the battery condition which was 3.07 volts. I then removed the battery for 5minutes to clear the SRAM. After reinstalling the battery and entering all settings again everything was fine thereafter. My safety limits were way off which I manually set with the hand controller. Perhaps it was a corrupted model which was cleared properly, or the warm restarts caused the issue. I'm not sure what the problem was, but everything appears to be working now as it should.
I've been looking through the logs and didn't see anything that shows a goto limit issue, all Serial Received results show "MS, 0" in all logs for the past few days.
That might lead me to the controller causing an issue.
00:44:44.271 Serial received: ? ? ? ? ?TID:11 [0]: <220:, 098d00;096d00
00:44:44.272 Serial Transmit ? ? ? ? ? TID:11 [0]: <237:p#
00:44:44.272 IT:DestinationSideOfPier ?TID:5 [1]: GoTo Limit, West Limit, East Limit Meridian offset (degrees):, 2, 6, -8
00:44:44.272 IT:DestinationSideOfPier ?TID:5 [1]: GoTo Limit, West Limit, East Limit Meridian offset (hours):, 0.133333333333333, 0.4, -0.533333333333333
00:44:44.272 IT:DestinationSideOfPier ?TID:5 [1]: SiderealTime, ScopeHA, DesinationHA (hours):, 7.31694444444444, -6.00361111111111, 1.61516032855189
00:44:44.280 Serial wait for response ?TID:11 [0]: <237:
00:44:44.298 Serial received: ? ? ? ? ?TID:11 [0]: <237:, 4500;4500
00:44:44.298 Serial Transmit ? ? ? ? ? TID:11 [0]: <235:r#
00:44:44.307 Serial wait for response ?TID:11 [0]: <235:
00:44:44.321 Serial received: ? ? ? ? ?TID:11 [0]: <235:, 4501;0
00:44:44.321 Serial Transmit ? ? ? ? ? TID:11 [0]: <237:p#
00:44:44.329 Serial wait for response ?TID:11 [0]: <237:
00:44:44.348 Serial received: ? ? ? ? ?TID:11 [0]: <237:, 4500;4500
00:44:44.348 IT:DestinationSideOfPier ?TID:5 [1]: From Region A to Region C, Retval: , pierEast
00:44:44.403 Serial Transmit ? ? ? ? ? TID:11 [0]: :Sr05:41:00#:ONPC Object#:Sd-02:26:40#:MS#
00:44:44.448 Serial wait for response ?TID:11 [0]: :Sr05:41:00
00:44:44.448 Serial received: ? ? ? ? ?TID:11 [0]: :Sr05:41:00, 1
00:44:44.448 Serial wait for response ?TID:11 [0]: :Sd-02:26:40
00:44:44.594 Serial received: ? ? ? ? ?TID:11 [0]: :Sd-02:26:40, 1
00:44:44.594 Serial wait for response ?TID:11 [0]: :MS
00:44:44.607 Serial received: ? ? ? ? ?TID:11 [0]: :MS, 0
?I had been using Warm Restarts, but since this occurred, I powered off and powered back on with Cold Starts from CWD to remove any prior modelling. I've set the goto limit to Western: 96, Eastern 98; with 2.5 degrees goto limit, which I thought was conservative enough to hit anything at 40-60¡ã but still got the Interrupt message.
I even went back to 1.0.75 drivers to rule out issues.
I thought goto limits was one of the reasons, but given the goto requests were nowhere near the meridian I ruled out that being an issue.
I have someone going onsite and will get them to check the current state settings on the hand controller to rule out any differences between what I'm setting and seeing in Gemini.NET; and remove the hand controller and try rule out where this might be occurring. May even swap the battery over.
Thanks
On Sun, 2 Jan 2022 at 04:14, Brian Valente < bvalente@...> wrote: I would add that if you use warm start (or restart) on a regular basis, it's possible the limits can drift a bit
Brian
On Sat, Jan 1, 2022 at 11:56 AM Paul Kanevsky < yh@...> wrote: Hi Dan,
This is from the Gemini 1 Level 4 manual, discussing the goto limit and safety limits:
The default value of zero means that the GoTo limit is set 2.5 degrees east of the western safety limit. Note: Use caution when setting the GoTo limit to values between 1 and 89 degrees. Such values would indicate points east of the meridian, and would mean that Gemini would try to point to objects between the GoTo limit (now in the eastern hemisphere) and the meridian with the telescope tube on the east side of the mount. It is possible that such objects would be unreachable without violating the eastern safety limit. Attempts to GoTo such objects in this situation would result in the telescope not moving, and?¡°*±õ²Ô³Ù±ð°ù°ù³Ü±è³Ù±ð»å*¡± being displayed on the hand controller.?
I suggest that you check your Goto and safety limit settings, as they are possibly preventing you from doing Goto's due to being too conservatively set.
Regards,
? ? ? -Paul
On Sat, Jan 1, 2022 at 11:22 AM, Daniel Judge wrote:
I've been using my mount in a remote installation lately, and often I will power the mount down and power up and connect to it when it's to be used.
I've just now encountered a constant interrupt message on the HC when I try to slew to stars around the sky with precise pointing and plate solving, sometimes some slews work others don't.
I can't work out why it's doing this, and I've never seen this before.
Everything looks to be Ok. I start Cold start from CWD, sync with GPS, and enter the correct site lat/long, I have the mount limits set to my best limits.
I am in the Southern Hemisphere. From south pole position, it will slew West to some stars, Ankaa, and Achernar.. but if I tell it to slew to rigel or Orion, the software says slewing, but the mount raises an 'Interrupted' message on the HC, and it doest nothing.
I'm using Gemini Level 4 v1.05 and the latest 1.0.84.0 .NET drivers.
Has anyone come across this HC message, or similar issue before?
--
Brian?
Brian Valente portfolio
|
