×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

ekos dither not received by PHD2

  • Posts: 969
  • Thank you received: 94
Hi everyone
Whilst most ekos dither requests are received by PHD2, some are not.
ekos sends a dither, but PHD2 does not receive it:

[2018-07-25T01:45:52.547 CEST INFO ][ org.kde.kstars.ekos.capture] - "Received image 2 out of 33."
[2018-07-25T01:45:52.548 CEST INFO ][ org.kde.kstars.ekos.capture] - Dithering...
[2018-07-25T01:45:52.693 CEST INFO ][ org.kde.kstars.fits] - Loading FITS file "/tmp/kstars/phd2.fits"
[2018-07-25T01:45:52.694 CEST CRIT ][ org.kde.kstars.fits] - "Could not open file /tmp/kstars/phd2.fits. Error could not open the named file"
[2018-07-25T01:46:37.631 CEST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: There was no dithering response from PHD2, but continue guiding."
[2018-07-25T01:46:37.632 CEST INFO ][ org.kde.kstars.ekos.capture] - "Dither complete."
[2018-07-25T01:46:37.634 CEST INFO ][ org.kde.kstars.ekos.guide] - "Dithering completed successfully."
[2018-07-25T01:46:37.635 CEST INFO ][ org.kde.kstars.ekos.guide] - "Guiding resumed."

Example of PHD2 successful dither from the same session:
23:21:22.249 00.121 139813593985856 evsrv: cli 0x55d758fb2e00 request: {"id":192,"jsonrpc":"2.0","method":"dither","params":[3,false,{"pixels":1,"time":12,"timeout":45}]}
23:21:22.249 00.000 139813593985856 dither: size=3.00, dRA=2.04 dDec=-0.63

Any ideas why doesn't the dither work every time?
TIA and clear skies,
Steve
indi and PHD2 logs: drive.google.com/open?id=1kOWyO2sKVd1cIVTS5FM-HMbvMhDL36aX
5 years 8 months ago #27824

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
My bet is that for some reason PHD2 did not receive the dither request. Sometimes the PHD2 communications are not perfect. The JSON documents can get interrupted or there could be a network issue that prevents them from being received. I programmed KStars to wait for a bit (I think it was 45 seconds) for the dithering to be reported as a success, but then if it doesn't, to just continue the sequence. That way if there is a dither communication failure or an issue with dithering, it doesn't just keep waiting and waiting for the dither to finish. I suppose we could also try to send a request to dither again if it doesn't report back that the dither command was received.
The following user(s) said Thank You: alacant
5 years 8 months ago #27829

Please Log in or Create an account to join the conversation.

Time to create page: 0.158 seconds