Re: Meridian Flip - Stopped Working
|
From the log zip file provided, Pointing.DAT appears to show no Initial Alignment since startup -?
If there is no initial?alignment, Gemini will not flip. (I have a sample python script which I wrote to test flips, and I can comment out the initial?sync to prove this.). If you think you are doing a sync, or a platesolve with sync, this might suggest it's not doing what you think it is? You have successful platesolve/syncs in late Sept and early Oct, but none since. The last entry in the file is: ! *** Losmandy Gemini2 Version 5.21 Build Mar 12 2017 08:22:00 started up ***
:NODA
:EQUAT
+40 36 07 2023 02 22 10.0 1000.0 0.0
<EOF>
The last alignment looks like it was nearly a week ago and I presume you have done a cold start since (this is a manual alignment on a catalogue object (Alpheratz) since it will say "PC Object" if doing a platesolve+sync via software. Initial Alignments to PC Objects are perfectly valid, and the normal way of doing it as an imager - you even have these in the file):?
! *** Losmandy Gemini2 Version 5.21 Build Mar 12 2017 08:22:00 started up *** :NODA
:EQUAT
+40 36 07 2023 02 16 10.0 1000.0 0.0
! UTC Date: 16/02/2023 UTC Time: 22:10:44 Initial Alignment, Object: Alpheratz α AND, West Side
00 09 35.11 +29 13 08.47 00 09 35.09 +29 13 08.62 02 28.68
! ? 0.00 ? 0.00 ? 0.00
Graeme
On Wed, 22 Feb 2023 at 13:06, Paul Kanevsky < yh@...> wrote: On Tue, Feb 21, 2023 at 08:51 PM, Frank Wielgus wrote:
Interesting results.
Once the troubleshooter started recording, I went to a bright star via the HC and synched.? During this time, error messages were flashing rather quickly with time out, com errors etc. After syncing I slewed just passed the meridian and tried to flip - which it did not.? The error messages never stopped. I then stopped everything. I did not get these messages before.? File is attached.
Thanks, Frank.? The logs show all the settings and configuration, and I'm still unable to see anything that would cause the no flip behavior. Maybe Ren¨¦?can take a look.
The comm errors you saw were related to the troubleshooter and Gemini.NET driver trying to poll the mount simultaneously while running in the 'record activity' mode. I've made a fix for this for a future version of the driver, but it shouldn't affect anything other than the occasional popup messages.
I do see your tests to flip the mount, and as before, Gemini reports success but doesn't flip, HA=0.1826:
Tracking=True
Nudge from Safety=True
Eastern Safety Limit=094d00
Western Safety Limit=094d00
Goto Limit=002d30
AtHome=False
AtPark=False
Status Byte=5
At Safety Limit=False
Side of Pier=W
####### HA=0.189758 before flip request, mount is tracking #########08:40:17.184: ENQ 0 Macro=557783;389867;6.265307;+31.833485;+0.189758;195.535668;+80.937333;T;T;N;W;6.455065;0;0;276.106358;5;00090B10;-1;0;5;0;
####### Sent flip request, received 0 => OK #########
08:40:17.184: TRANSMITED=:Mf#
08:40:17.184: RECEIVED=:Mf#=0
####### Mount continues to track towards the safety limit, no flip has occurred #########
08:40:17.685: ENQ 0 Macro=557769;389867;6.265302;+31.833485;+0.189902;195.547123;+80.936885;T;T;N;W;6.455205;0;0;275.582792;5;00090B10;-1;0;6;0;
08:40:18.187: ENQ 0 Macro=557756;389867;6.265306;+31.833485;+0.190038;195.557759;+80.936475;T;T;N;W;6.455344;0;0;275.096623;5;00090B10;-1;0;5;0;
08:40:18.688: ENQ 0 Macro=557742;389867;6.265300;+31.833485;+0.190185;195.569213;+80.936029;T;T;N;W;6.455485;0;0;274.573057;5;00090B10;-1;0;13;0;
|
