Dither Error Code 1 Error?
Jim Waters
bw_msgboard
No idea, this doesn’t come from PHD2. Suggest you ask the NINA people…
Bruce
--
You received this message because you are subscribed to the Google Groups
"Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/e6ce0772-b9c1-4c08-ab3c-2dc5d0eaa497n%40googlegroups.com.
Jim Waters
Brian Valente
19:48:59.403 00.003 4244 PhdController::Dither begins
19:48:59.408 00.005 4244 Error thrown from C:\cygwin\home\agalasso\projects\phd2\myframe.cpp:2010->cannot dither if not guiding
19:48:59.412 00.004 4244 PhdController::Dither pFrame->Dither failed
19:48:59.416 00.004 4244 evsrv: cli 06F18400 response: {"jsonrpc":"2.0","error":{"code":1,"message":"Dither error"},"id":"5"}
19:48:59.425 00.009 4244 evsrv: cli 06F18400 disconnect
19:52:35.371 215.946 4244 evsrv: cli 06F18B80 connect
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/0d05b5fb-0a7a-4cae-9dc9-7bc6759fdcdbn%40googlegroups.com.
Jim Waters
You received this message because you are subscribed to a topic in the Google Groups "Open PHD Guiding" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-phd-guiding/gm-S8DTbGIo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i4%2BYFRUJVoZQjkui0MLW7KuGLmXSdBYug2JZKdA2wq4eQ%40mail.gmail.com.
Brian Valente
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAB5JAT3cVvCZz9q4hnGP3J_9cVv5ZX5geHuON1Z%3D3AFfLbGtuw%40mail.gmail.com.
Jim Waters
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i7770-ttu0_9uyih%3D0U%3Dby-AottbYfW4uj8Mb%2BhaiFcjw%40mail.gmail.com.
bw_msgboard
This isn’t really rocket science, you or the NINA people should be able to figure it out by just looking at the log entries. Let’s just take this one example, the one where a dither was attempted while guiding was inactive. Log entries and comments below:
19:44:15.773 01.064 4244 evsrv: cli 06F18540 connect
19:44:15.833 00.053 4244 evsrv: cli 06F18400 connect
19:44:15.845 00.004 4244 evsrv: cli 06F18400 request: {"id":"96","method":"get_pixel_scale"}
19:44:15.849 00.004 4244 evsrv: cli 06F18400 response: {"jsonrpc":"2.0","result":3.86747,"id":"96"}
19:44:15.860 00.011 4244 evsrv: cli 06F18400 disconnect
19:45:23.699 00.811 4244 evsrv: cli 06F18D60 connect
19:45:23.713 00.005 4244 evsrv: cli 06F18D60 request: {"id":"99","method":"get_app_state"}
19:45:23.722 00.005 4244 evsrv: cli 06F18D60 response: {"jsonrpc":"2.0","result":"Guiding","id":"99"}
19:45:23.726 00.004 4244 evsrv: cli 06F18D60 disconnect
19:45:23.731 00.005 4244 evsrv: cli 06F18B80 connect
>>> Your app issues a ‘stop capture’ command – this is just like clicking on the big red ‘Stop’ button in PHD2, Looping and guiding STOP after the camera exposure is aborted.
19:45:23.742 00.004 4244 evsrv: cli 06F18B80 request: {"id":"6","method":"stop_capture"}
19:45:23.755 00.007 4244 evsrv: cli 06F18B80 response: {"jsonrpc":"2.0","result":0,"id":"6"}
19:45:23.759 00.004 4244 evsrv: cli 06F18B80 disconnect
19:45:23.766 00.007 4244 evsrv: cli 06F18400 connect
19:45:23.778 00.003 4244 evsrv: cli 06F18400 request: {"id":"99","method":"get_app_state"}
19:45:23.784 00.003 4244 evsrv: cli 06F18400 response: {"jsonrpc":"2.0","result":"Guiding","id":"99"}
19:45:23.788 00.004 4244 evsrv: cli 06F18400 disconnect
19:45:24.869 00.010 4244 evsrv: cli 06F18CC0 connect
>> You app continues to poll the state of PHD2 – here it’s told that it is STOPPED based on the command it sent one second earlier.
19:45:24.873 00.004 4244 evsrv: cli 06F18CC0 request: {"id":"99","method":"get_app_state"}
19:45:24.876 00.003 4244 evsrv: cli 06F18CC0 response: {"jsonrpc":"2.0","result":"Stopped","id":"99"}
19:45:24.880 00.004 4244 evsrv: cli 06F18CC0 disconnect
19:48:59.394 214.514 4244 evsrv: cli 06F18400 connect
>> Despite all this, your app now wants to start a dither operation and is told the operation can’t be done
19:48:59.400 00.006 4244 evsrv: cli 06F18400 request: {"id":"5","method":"dither","params":{"amount":3,"raOnly":false,"settle":{"pixels":1.5,"time":16,"timeout":40}}}
19:48:59.416 00.004 4244 evsrv: cli 06F18400 response: {"jsonrpc":"2.0","error":{"code":1,"message":"Dither error"},"id":"5"}
So this is NOT a PHD2 bug, it’s a fouled up automation sequence. Analyzing this sort of thing requires nothing more than a text-search for ‘evsrv’ in the debug log file, looking at the request/response pairs, and thinking about what’s going on.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAB5JAT0yz%2BpDNQYZY5TfD83Ye%2BSONTUgzAqxXy0FSBxdmj%2BXFg%40mail.gmail.com.
Jim Waters
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/16E485F8AF90488BB7C950CE0A5CD395%40HomeDesktop.
Brian Valente
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAB5JAT0LL1fO9k0GbwzPj%3D%3DLaxAZrnis%2B5P1z_NrfNThKtx%2BaA%40mail.gmail.com.