Hi,
I'm continuously getting hangs of the indi_eqmod_telescope thread. It would suddenly start consuming 100% CPU and stop responding to any communication.
I enabled debugging, and the common issue seems to be that one of the encoders suddenly reports a completely different (negative) value:
This seems to be some communication problem. If I look at the logs, and compare the good and bad case, I see
COMM 106.305638 sec : dispatch_command: ":j2", 4 bytes written
COMM 106.321439 sec : read_eqmod: "=003091", 8 bytes read
SCOPE 106.321567 sec : GetDEEncoder() = 9515008
--
COMM 107.365940 sec : dispatch_command: ":j2", 4 bytes written
COMM 107.382985 sec : read_eqmod: "=0030", 9 bytes read
SCOPE 107.383103 sec : GetDEEncoder() = -49729536
It reads an additional byte (9 instead of 8 ). I checked all hangs I have logs for, always the same: Good reads receive 8 bytes, the bad one 9. Some suggestions how to further narrow this down would be highly welcome!
The following user(s) said Thank You: Jasem Mutlaq
Good observations. Perhaps you could be put a break point once the value < 0 and then trace that back to read_eqmod and see what's going on with this particular read? You'd need to know how to use gdb (or QtCreator)
Sorry, I had put that back for a while (during new moon...)
Meanwhile I got my direct usb cable for eqmod. Only some quick tests so far, but with that cable there were no hangs/misscommunications. Also, I had been using the normal synscan module extensively via exactly the same cable and did not experience problems there either, so it somehow seems linked to the PC Direct mode.
Full moon is ahead, so I'll probably have some time trying this breakpoint/debug thing. I'm not really a programmer though...
I'll share my findings (should I get some...)