BIG BUG with LACERTA NEW post with video and all the files

Sequence Generator Auto Focus
1

Hello

I start a new post with all the files at disposal for analysis with this link and a small video to show the bug.
I shared all the file with this linK :
https://share.orange.fr/#QiBbKZT1zw284dd130f beware this is not the right link , see below the good one
https://share.orange.fr/#5oe64AjWGb284dd7cec

Please HELP me with this bug
Arnaud

You will see in the video that the focuser is not reponsponding to commands but something happens between SGPro and the focuser when you open the “Control Panel” at the “focuser tab”, at the botton , you can see the activuity , and it is constantly switching from idle to focuser. To stop it , I just disconnect the focuser….
after reconnection the focuser becomes crazy … it moves without any command

Please see this video

I am testing the configuration on my desk with my test computer . I always do so before going to my remote place and install everything there. Usually it prevents me from lots of problem directly on field.
So
I redo all the testing with my desktop computer , but this time with all the setup and config files from my remote , I mean with the equipement and localisation files used by SGPro and a .sgf file of SGPro.
I shared all the file with this linK :
https://share.orange.fr/#QiBbKZT1zw284dd130f beware this is not the right link , see below the good one
https://share.orange.fr/#5oe64AjWGb284dd7cec

12:58

  1. I power ON the LACERTA Controller with the Motor attached to it,

  2. I launch SGPro on my computer

  3. I connect the Focuser = >OK connected

  4. Initial Current position : 6251

  5. I push the button “Fine” IN with a steps of 5 => the motor move only 1 step (not the 10 asked)
    Current Position : 6250
    => FIRST BUG

  6. I push the button “Fine” OUT with a steps of 5 => the motor DOES NOTmove at ALL ,
    Current Position : 6250

  7. I push the button “Coarse” OUT with a steps of 200 => the motor DOES NOTmove at ALL ,
    Current Position : 6250

  8. I push the button “Coarse” IN with a steps of 200 => the motor DOES NOTmove at ALL ,
    Current Position : 6250
    If you look at the log , you see nothing about these 3 commands corresponding to 6) 7) and 8)
    13:02

  9. Nothing works , the Focuser is not reponsding so I disconnect it and reconnect it at 13:02

  10. The focuser si redoing ALMOST ALL the commands that were not executed earlier , and at the end the current position is now : 6449

  11. Without BUG , the expected position will be the start/initial position because -5+5-200+200 = 0 zero , but it is not 6251 but 6449

  12. Fine IN , Fin Out , Coarse IN and Coarse OUT = ALL OK and the final position is GOOD with 6449.
    13:08

  13. Disconnect focuser and killing SGPro at 18:55

IN the log :
5) commands of FINE IN of -5 => [08/01/19 12:59:29.913][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL message received…
[08/01/19 12:59:30.016][DEBUG] [Focuser Thread] Focuser moving to 6246
[08/01/19 12:59:30.016][DEBUG] [Focuser Thread] Focuser backlash active, modified move to 6196
[08/01/19 12:59:30.021][DEBUG] [Focuser Thread] Focuser move call complete
[08/01/19 12:59:30.023][DEBUG] [Focuser Backlash Thread] Focuser backlash thread has started…
The focuser current position is only 6250 instead of expected 6246) nothing move after …
The 3 commands FINE OUT , COARSE IN and COARSE OU are not seen in the log , the fouser did not move at all
I disconnect the focuser at 13:02 , It is written below , OK =>
[08/01/19 13:02:37.928][DEBUG] [Main Thread] Disconnecting ASCOM Focuser: ASCOM.MotorFocus.Focuser

All log files of the above script are at your disposal with the link

The video was done just after the script above.
Arnaud

2

I don’t see the video in those files. But what is interesting from your log may be this:

[07/30/19 18:54:29.867][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL message received...
[07/30/19 18:54:29.867][DEBUG] [Focuser Thread] Focuser moving to 10
[07/30/19 18:54:29.867][DEBUG] [Focuser Thread] ASCOM Focuser: MaxStep is 0.  Ignoring this, hopefully bad things don't follow.

Generally we expect a MaxStep size from the driver. This may be something you can set in the driver itself. This limits the number of steps that the calling application should send to your focuser at any given time. Having this at 0 may be causing the actual focuser to have some issues. We’d have to see the actual ASCOM logs from the focuser as well.

Also for these tests it would be beneficial to disable backlash compensation as that tends to just add more traffic to the logs.

If you could also provide a link to the controller you’re using that would be helpful.

Thank you,
Jared

3

Thank a lot for your support
This is the link direct to the video : https://share.orange.fr/#kt2SxEgGdZ284dd7b6d

For the link , It is my mistake please find the REAL link to all alll logs and the video and the ASCOM driver log of the focuser LACRTA

in the directory : https://share.orange.fr/#5oe64AjWGb284dd7cec

Thanks
ARnaud

4

NEW TEST without Backlash in SGPro : Backlash desactivated during the test

TEST without Backlash compensation in SGPro

Script :
WITHOUT SGP Backlash : backlash not checked in SGPro menu
18:18

  1. I power on the focuser
  2. I launch SPRo with the file .sgp : “WITHOUT Backlash – TEST My setup with LACRETA MFOC.sgp”
  3. I pconnect the focuser in SGPro, => OK
  4. 18:19
  5. InitialCurrent position : 3609
  6.  I push the button “Fine” IN with a steps of 10 => NOT OK  the motor move only 1 step (not the 10 asked)

Current Position : 3608
=> FIRST BUG

In the log , you see
[08/01/19 18:19:56.711][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL message received…
[08/01/19 18:19:56.815][DEBUG] [Focuser Thread] Focuser moving to 3599
[08/01/19 18:19:56.820][DEBUG] [Focuser Thread] Focuser move call complete
[08/01/19 18:19:58.242][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL complete…

Comment : But the focuser did not move to 3599, but to 3608 , only -1 instead of -10, WHY ?

In the ASCOm LOG , you see that the received command is to move to 3608 not the expected 3599 => NOT OK, WHY ??

2019-08-01 18:19:57.427 | ASCOM.Position receive wait.
P 3608
execution.

So the ASCOM driver received the order to move to 3608, , WHY ?
and it really moves to 3608

The rest , is OK if I do not push the “STOP button”

  1.  I push the button “Fine” OUT with a steps of 10 =>  OK   3618

  2.  I push the button “Coarse” OUT with a steps of 100 => ok  3718

  3. I push the button “Coarse” IN with a steps of 100 => OK

08/01/19 18:21:24.778][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL message received…
[08/01/19 18:21:24.879][DEBUG] [Focuser Thread] Focuser moving to 3618
[08/01/19 18:21:24.879][DEBUG] [Focuser Thread] Focuser move call complete
[08/01/19 18:21:26.402][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL complete…
[08/01/19 18:22:07.073][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL message received…
[08/01/19 18:22:07.174][DEBUG] [Focuser Thread] Focuser moving to 3718
[08/01/19 18:22:07.175][DEBUG] [Focuser Thread] Focuser move call complete
[08/01/19 18:22:10.567][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL complete…
[08/01/19 18:22:20.577][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL message received…
[08/01/19 18:22:20.678][DEBUG] [Focuser Thread] Focuser moving to 3618
[08/01/19 18:22:20.678][DEBUG] [Focuser Thread] Focuser move call complete
[08/01/19 18:22:23.955][DEBUG] [Focuser Thread] SGM_FOCUSER_MOVE_REL complete…

Eveything works OK , but if I push the button STOP , let ‘s have a look

  1. Push the STOP button 18:23
  2. I push the button “Fine” OUT with a steps of 10 => NOT OK  the motor move only 1 step (not the 10 asked)

Comment : if I push the STOP button , ,the command after is always 1 instead of 10 or 100 Steps, . And the next following command is OK.

  1. Push the STOP button 18:27
  2. I push the button “Fine” OUT  with a steps of 10 => NOT OK  the motor move only 1 step (not the 10 asked) Current Position : 3618
  3. Push the STOP button 18:28
  4. I push the button “Fine” IN  with a steps of 10 => NOT OK  the motor move only 1 step (not the 10 asked) Current Position : 3617

I did that many times STOP + Fine IN , always the same behavior 18:29

  1. Disconnect focuser and killing SGPro at 18:30

Files at the following link : https://share.orange.fr/#fsuW1TAkk5284dde974

Comments : with the BACKLASH deactivated , the behaviour is different , but still faulty …
Anyway , in the field , I will use the SGP backlash because it is really impossible to work without it .So it has to work with backlash …

Please help,
ARnaud