Catch 22 situation here. I run indiserver on an embedded Pi 3 mdel B. I have two options to run KStars/EKOS.
1. Running KStars/EKOS on the Pi and using Remote Desktop to connect to and control the Pi.
2. Running KStars/EKOS on my desktop and connect it to the indiserver on the Pi.

In situation 1 my ASI120MM is not working and produces distorted images like in this post indilib.org/forum/ccds-dslrs/1730-asi-120mc-bug.html#12902
The QHY5L-II-C guider camera is working OK most of the time, although some errors occasionally occur.
In situation 2 my QHY5l-II-C guider camera is not working. It sometimes gives a good image, but intermittent distorted images as mentioned above and regular "Exposure timeout. Restarting exposure..." errors. All leading to loosing the guide function.

w0anm wrote: " I found that would have to keep the exposure times to less then 2.5 seconds or so. ....[snip].... The blocking read call never finishes. and you get a timeout error. I've attempted to abort, disconnect and reconnect, and usb disconnect. The only solution I've found is to restart the Indi server and reconnecting."

I had already done that, but ended up getting indiserver running multiple instances of the indi_qhy_ccd driver. See the image attached to my original posting. After several restarts, I have now 5 drivers running. One time the indi_simulator_telescope driver and 4 (four) times the indi_qhy_ccd driver. At restart I also get an error now on the indi_simulator_telescope driver (see attachment).

It seems that the indi_qhy_ccd driver is not properly removed from the driverlist in the indiserver when the server is stopped. Considering the warning on the indi_simulator_telescope driver, that may also still be in the driverlist, but at least is not duplicated.

When I set the exposure time on the QHY5l-II-C camera to 5 seconds or more, the camera stops recording images and is no longer controllable via the INDI Control Panel. WHY? To my knowledge the filesize does not change with exposure time.

I have attached a log file in which I have made a few images with times shorter than 5 seconds, than a longer one where upon the camera stops responding.

An other problem with the driver is the fact that you can not disconnect/connect via the INDI Control Panel. It gives this error: "2018-03-01T13:54:23: [ERROR] Connecting to CCD failed (QHY5LII-C-6177e210b82ca44af)" when trying to reconnect.

Jasem Mutlaq, can you please look into these problems? The few clear nights We had overhere are all lost due to failing equipment.

regards berendj

Read More...