@ Blueshawk
Nothing except patches because of variable overflow was done since March ... I was really lazy last few months
@ Khalid
yes you are right, OnStep uses ":GU" return codes to update tescope status so it reflects exactly the Firmware Status.
The Status is refreshed in the tab each time there is a change in the return code.
In the doubt, I checked some very little slews (1', 2', 10') both RA and DEC via terminal and status behaves normal
Did the same via Indi Control panel and same results.
2018-09-06T11:22:31: [INFO] Slewing to RA: 10:10:09 - DEC: -0:29:09
2018-09-06T11:22:26: [INFO] Slewing to RA: 10:10:09 - DEC: -0:29:10
2018-09-06T11:22:17: [INFO] Slewing to RA: 10:10:10 - DEC: -0:29:10
2018-09-06T11:22:13: [INFO] Slewing to RA: 10:10:10 - DEC: -0:29:03
2018-09-06T11:22:08: [INFO] Slewing to RA: 10:10:03 - DEC: -0:29:03
2018-09-06T11:22:02: [INFO] Slewing to RA: 10:10:03 - DEC: -0:29:02
2018-09-06T11:21:49: [INFO] Slewing to RA: 10:10:02 - DEC: -0:29:02
2018-09-06T11:21:37: [INFO] Slewing to RA: 10:10:00 - DEC: -0:29:00
@ avarakin
First of all, thanks for your time passed on testing and reporting.
Are you using version 1.3 or 1.4?
Do I understand well: You try to slew some second and the sleew starts but never ends!
Does the ":GU#" return change in the "ONStep Status" tab?
Do you have logs for this situation.
I did a test on bench (cannot do it in real situation, my hardware is not mounted)
I was not able to reproduce this problem when asking slews for 1' or 2' and I saw the status changing from Tracking to Slewing and Tracking again,
This status change cannot be seen in the control panel because sometimes it is too quick, but it really happens
Since in the driver code Scope status if set only once based on Status query it is unlikely that Scope Status is set to Slewing and vever reste to Tracking due to polling issues and missed state changes.
I also check is it is not Ekos setting TrackState=SCOPE_SLEWING, it is not the case.
I am sorry not to be in position to help here.
I will check further but if in the meantime you could take logs of the situation would help.