Folks, I found an error last night in the ken-self-sync branch that the mount does not correctly report when it is slewing and when slewing is finished. This leads to problems in EKOS where a plate solving for example is started too early while the mount is still slewing to the expected target.

Please use stargo_work , which does not show this behavior.
-Wolfgang

Can you send me the debug log which has this behaviour?

Hi Ken,
here comes the log file. Please take a look at the entries after 2018-10-03T20:36:10.872, where I started the EKOS polar alignment routine. After the first solved frame, the scope is sent to RA: 07h 59m 17s, DE: 88° 19' 45. At 2018-10-03T20:37:16.470 CEST, the telescope reports that the slewing has completed and a new frame is taken.

What we cannot see in the log file is, that in fact the slew wasn't complete. We can see it only indirectly in a failed solving attempt, which comes from star trails in the taken image.

Currently, my M-zero is in action. I will investigate this tomorrow.

Cheers
Wolfgang

Its odd that there are so few debug messages being logged. There should be a huge number of debug messages as each time the mount is polled (usually once per second) you should get at least 3 or 4 debug messages. These are the ones that indicate the motion state of the mount.

here's my log from last night. You can see the solve at 21:42:28 then the mount slews. The motion state polled is m55 and when it returns to state m10 the next exposure is taken
One thing puzzles me. In your log at 20:50:19 there is a message: Avalon StarGo : "[INFO] Slew is complete. Tracking... "
My version of the code does not issue any such message
In the equivalent position in my log at 21:42:32.530 you see that message is not issued.
That message is in the version of ReadScopeStatus in stargo_work branch.

That's right, this message was missing in your branch. I did some changes on top of yours. It found that parking/unparking wasn't behaving correctly and that I could slew a parked scope. This should be fixed now. And I re-introduced the messages about a slew complete which I find an important message.

So it might be that the mistake was introduced by my latest changes, right.

In ReadScopeStatus line 509:
else if(x>1 && y>1)
newTrackState = SCOPE_SLEWING;
should be
else if(x>1 || y>1)
newTrackState = SCOPE_SLEWING;

Ouch, you are absolutely right. I will fix it today.

OK, the fix is published, please pull the latest version of the ken-self branch .

@kengs: I had forgotten to commit the changes for the info messages. Now everything should be in place.

Detecting slewing and tracking state was still not right. The problem was, that guiding signals - which typically show up as motor status 4 - resulted in a state SCOPE_SLEWING, which was definitely wrong. As a result, PHD was interrupted frequently.

I changed it now that way that ReadScopeStatus() never sets the state SCOPE_SLEWING on its own but it detects, when a slewing state has finished and results into tracking, a parked scope etc.

Please pull the latest version of the ken-self-sync branch.

I did some code cleanup. It would be great if you test the current version.