I am still experiencing this issue in INDI 1.9.1 and 1.9.2 with the sv305 driver. I do not experience this with my ZWO or QHY cameras.

Read More...

I fixed this by checking out the pyindi-client commit just before the high level property includes were added.

git checkout 9a255471f5e91e04404c9d481b16dfc6ce45a582

Read More...

Here is an example of a normal exposure:

021-04-10 00:00:31,245 [INFO] MainProcess takeExposure() #108: Taking 9.239792 s exposure
2021-04-10 00:00:31,286 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:31,717 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:32,718 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:33,719 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:34,721 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:35,722 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:36,723 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:37,724 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:38,725 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:40,648 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:40,772 [INFO] MainProcess newBLOB() #66: new BLOB CCD1
2021-04-10 00:00:40,777 [INFO] MainProcess newBLOB() #73: Blob downloaded in 0.0041 s
2021-04-10 00:00:40,778 [INFO] MainProcess run() #784: Exposure received in 9.5331 s

Here is an abnormal exposure received in double the time.
2021-04-10 00:00:46,262 [INFO] MainProcess takeExposure() #108: Taking 9.239792 s exposure
2021-04-10 00:00:46,306 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:46,655 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:47,656 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:48,657 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:49,658 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:50,660 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:51,662 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:52,664 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:00:53,665 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:01:04,980 [INFO] MainProcess newNumber() #87: new Number CCD_EXPOSURE for device SVBONY SV305 0
2021-04-10 00:01:05,103 [INFO] MainProcess newBLOB() #66: new BLOB CCD1
2021-04-10 00:01:05,108 [INFO] MainProcess newBLOB() #73: Blob downloaded in 0.0041 s
2021-04-10 00:01:05,109 [INFO] MainProcess run() #784: Exposure received in 18.8462 s


Read More...

I am writing a project to generate timelapses for All Sky cameras using INDI as an interface for the camera.  It is heavily inspired by github.com/thomasjacquin/allsky

I am currently using INDI v1.8.9 with pyindi.  Once I started reviewing my timelapses, I realized I was missing some expected frames.  As an example, at night, I configure a max exposure time of 15s, but I was missing approximately two 15s frames for every 75s period (2 out of 5 expected frames).

After reviewing my logs, I can see that ~2 out of every 5 frames, I receive the exposure 30s after requesting a 15s exposure.  The frame exposure still seems to be 15s, but something is causing the blob to not be received until double the time has elapsed.

Read More...