Unexpected meridian flip

@Sergio wrote:

Hi,
my name is Sergio (from Italy) and got the SG pro one month ago and I’m quite happy with it, but I have one problem that not allow me to perform the exposure in autonomous mode for the whole night. In the last two sessions, the the SG performed the meridian flip in right way, but about two hours later, it aborted the session. I noted that it attempted to perform again the meridian flip but of course with no successful (it was already performed two hours before).
I analysed the log file and discovered the following:
a_ also after the meridian flip, the SG checked if a meridian flip is required (the target is already the same i.e. the coordinate were not changed)
b_ the log file reported correctly the side of peer: west before the meridian flip and east after the meridian flip
c_ about two hours later the log file reported wrong side of peer: west instead east. At this point SG started the flip procedure, but the telescope reported that the peer of side was east. At this point SG aborted the sequences.
See the attached log file, in foreground green colour the part with the first needed meridian flip, in yellow the part with unexpected meridian flip and in red the error log.
I do not understand where is the problem, SG or ASCOM telescope driver, and ask to the developers what I have to do in order to avoid this issue.

Thanks a lot in advance for your support and best regards,
Sergio

My configuration is the following:
SG pro rV 3.0.2.94
O.S. Windows 7 updated
Mount Gemini G53F with Pulsar 2 controller FW 5.70 and ASCOM driver released on the 2016. The SG is connected througt ASCOM POTH Hub
ASCOM platform 6.
sg_logfile_20180908222239.zip (93.8 KB)

Posts: 2

Participants: 2

Read full topic