×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

INDI Driver for SVBONY cameras

  • Posts: 149
  • Thank you received: 31
Hi Hades,

Settings usually sits in the ".indi" folder, in your "home".
But you mostly get this kind of error when your "indi_sv3055_ccd" binary doesn't match the loaded library (ie the SDK version).

Did you start the driver from "command line", or from the Ekos GUI ?

Thx8411
2 years 5 months ago #76913
The topic has been locked.
  • Posts: 152
  • Thank you received: 20
It was started from the command line. I have renamed the driver configs and now it connects correctly.
hades
2 years 5 months ago #76915
The topic has been locked.
  • Posts: 255
  • Thank you received: 65
Hello, I have been using the sv305 for over 6 months now in an All Sky camera (permanent enclosure).  The camera has been very stable over that time, but I have had quite an irritating issue that I have not been able to resolve.

Hardware:  Raspberry Pi 3
OS:  Raspbian 10
INDI:  1.8.9, 1.9.1, 1.9.2 (via pyindi-client)
Camera:  SV305

On average, at least 40% of the exposures take double the time of the exposure to complete.  In some cases, it can be 90% of the exposures.  It seems to happen at random.  For the most part, I run at a pretty high gain at night, usually 250 and short exposures of 15s.  The exposures are still the correct exposure time, but the exposure is not received for double the time.

Below is an example that shows images from last night, the requested exposure, and how much time elapsed from the previous exposure.
Time | Exposure | Delta
2021-10-29 22:09:36|15.0|31
2021-10-29 22:09:05|15.0|30
2021-10-29 22:08:35|15.0|16
2021-10-29 22:08:19|15.0|30
2021-10-29 22:07:49|15.0|31
2021-10-29 22:07:18|15.0|15
2021-10-29 22:07:03|15.0|31
2021-10-29 22:06:32|15.0|15
2021-10-29 22:06:17|15.0|31
2021-10-29 22:05:46|15.0|31
2021-10-29 22:05:15|15.0|30
2021-10-29 22:04:45|15.0|31
2021-10-29 22:04:14|15.0|30
2021-10-29 22:03:44|15.0|31
2021-10-29 22:03:13|15.0|30
2021-10-29 22:02:43|15.0|16
2021-10-29 22:02:27|15.0|30
2021-10-29 22:01:57|15.0|31

Any ideas?
2 years 4 months ago #77104
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi Aaron,

What settings do you use on your camera ?

Could you please show us your python script ?

Best regards,

Thx8411
 
2 years 4 months ago #77182
The topic has been locked.
  • Posts: 255
  • Thank you received: 65
The script is not small simple, unfortunately, its part of my allsky software project:  github.com/aaronwmorris/indi-allsky/

Here are some example log messages from a doubled exposure.  The camera appears to take the exposure and then hangs (a 9 second gap between messages).  Below that is what a normal exposure looks like.

Doubled exposure

<code>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</code>


Normal exposure

<code>2021-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</code>

 
Last edit: 2 years 4 months ago by Aaron Morris.
2 years 4 months ago #77348
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi Aaron !

Great project ! It looks awesome !

Sorry, I didn't found the time to dig on this issue yet, but I promise I won't forget you.

Best regards,

Thx8411
The following user(s) said Thank You: Aaron Morris
2 years 4 months ago #77534
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello Hades,

I received my SV305M Pro today, and found a bug : the frame pixel depth (8 or 12) selection wasn't available in the UI any more.
Pushed a fix on my repo. A pull request is on it's way.

I advise you to delete your saved driver config before, like you already did earlier.

Best regards !

Thx8411
2 years 4 months ago #77535
The topic has been locked.
  • Posts: 152
  • Thank you received: 20
Hi Collin, these are great news, I am loking forward for the update.
Hades
2 years 4 months ago #77537
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello Hades,

Another bug : the LiveView recording (.ser file) was broken for the SV305M Pro.
Fixed in my repository. Pull Request on it's way.

I also removed some wrong FITS entries (color controls on a mono camera...)

Best regards !

Thx8411
2 years 4 months ago #77608
The topic has been locked.
  • Posts: 255
  • Thank you received: 65
I might have figured out what is causing the doubled exposure time.  I made a new script that is a "minimum viable product" to take exposures, but performs all of the configuration in the way it is normally done in my program.  Doing this I could quickly change various settings to see how the program would react.  I found that I could not consistently get the doubled exposure until I was taking 9 second exposures.  8 seconds and below, it might happen rarely, but at 9 seconds it happened fairly often.

This is my MVP test script:
github.com/aaronwmorris/indi-allsky/blob...ting/exposureTest.py

My indi code (which is based on Marco Gulino's indi-light-tools) has a synchronous mode for taking exposures.  Basically, it sets the exposure value and then queries the status of the exposure control until it is idle.  The code I was using would query the status of the control every 0.05 seconds, or 20 times a second.  Backing off to 0.15 seconds between status calls seems to do better.  It appears the cause of the doubled exposure is aggressively querying of the status of the exposure control.  I am not sure if it is the total number of status calls or just the calls-per-second causing the behavior.

It does appear to be specific to the sv305.  I have tested several other cameras (ASI, QHY) and they do not exhibit the same behavior.

This is the code where my script queries the status:
github.com/aaronwmorris/indi-allsky/blob...exposureTest.py#L352
The following user(s) said Thank You: Jasem Mutlaq
2 years 4 months ago #77636
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello Hades,

The SV305M PRO should be fully supported now.
The SV305M PRO being a mono camera, it's much more sensitive.
I added ROI support in live view for fast fps planetary imaging.
Binning also works in live view now.

Version 1.2.9 is in my repo.
Submitted a PR.

Best regards !

Thx8411
The following user(s) said Thank You: Joakim
2 years 4 months ago #77813
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello Aaron,

Thanks for your diagnostic.
Could you please enable the debug log level on the indi server side, and send me the resulting logs in "real use".
We could have some useless internal calls in the driver, introducing time delays.

Best regards,

Thx8411
2 years 4 months ago #77814
The topic has been locked.
Time to create page: 0.866 seconds