×

INDI Library v1.9.9 Released (30 Nov 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

INDI Driver for SVBONY cameras

  • Posts: 67
  • Thank you received: 0
Interesting.

I'm using a Raspberry Pi 4B with the latest release of Astroberry.

All other settings have no errors.

Yes. multiple power resets of both camera and Pi.

Probably best to wait until SVBONY replies to thx_8411.
Last edit: 2 years 3 months ago by Doug MacGregor.
2 years 3 months ago #59444
The topic has been locked.
  • Posts: 47
  • Thank you received: 0

Okay i was able to reproduce your error:

there is what needs to work around the device done to get to the error (or in my case why i did not see the error)
1. connect to device.
2. capture a 1 second shot
3. change gain - now it will work.

see screenshot for confirmation. I took a picture between 16:01:15 and 16:01:25 - I suppress those logs in the source.

From briefly looking at it, the issue it seems is with the SDK.
NOTE: The value printed on the error message is zero, which the value should have been 170. thats because i interpreted the variable as an integer wrongly.

here is the snipit of the code producing the log entry:
@@ -1041,22 +1042,25 @@ void Sv305CCD::TimerHit()
 // helper : update camera control depending on control type
 bool Sv305CCD::updateControl(int ControlType, SVB_CONTROL_TYPE SVB_Control, double values[], char *names[], int n)
 {
-    IUUpdateNumber(&ControlsNP[ControlType], values, names, n);
 
+    IUUpdateNumber(&ControlsNP[ControlType], values, names, n);
+    LOGF_INFO("Camera control %d to %.f\n", ControlType, ControlsN[ControlType].value);
+    ControlsNP[ControlType].s = IPS_OK;
+    IDSetNumber(&ControlsNP[ControlType], nullptr);
     pthread_mutex_unlock(&cameraID_mutex);
 
     // set control
     status = SVBSetControlValue(cameraID, SVB_Control , ControlsN[ControlType].value, SVB_FALSE);
     if(status != SVB_SUCCESS)
     {
-        LOGF_ERROR("Error, camera set control %d failed\n", ControlType);
+        LOGF_ERROR("Error, camera set control %d failed: sdk-id=%d, value=%d\n", ControlType, SVB_Control, ControlsN[ControlType].value);
+        ControlsNP[ControlType].s = IPS_ALERT;
+        IDSetNumber(&ControlsNP[ControlType], nullptr);
+        return false;
     }
-    LOGF_INFO("Camera control %d to %.f\n", ControlType, ControlsN[ControlType].value);
:
Last edit: 2 years 3 months ago by Rashed.
2 years 3 months ago #59448
Attachments:
The topic has been locked.
  • Posts: 47
  • Thank you received: 0
@thx,

Whilst the OEM is working on their SDK, this workaround may be useful to mitigate the issue:

github.com/rsarwar87/indi-3rdparty/commi...1f23ab3f43b6fe2563f3
2 years 3 months ago #59449
The topic has been locked.
  • Posts: 67
  • Thank you received: 0
You are right.
As soon as I do any kind of capture with the camera, the error messages no longer appear when I "set" the Gain.
Nice catch.

Did you try that patch yoursefl?

How would I apply it?

Thanks.
2 years 3 months ago #59458
The topic has been locked.
  • Posts: 47
  • Thank you received: 0
yes, i have it running.

you would need to recompile the code. if you are unsure how to do it, i recommend doing it manually for the time being - till they update the indi repository.
2 years 3 months ago #59460
The topic has been locked.
  • Posts: 67
  • Thank you received: 0
I agree.
I don't need to introduce problems while I have it running.
2 years 3 months ago #59466
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello,

Thanks for your help Sarwar. I didn't notice this behavior.

It's great !

I will look deeply at your patch and do some testing this week-end.
Does it work for all targets (amd64, arm, etc.) ?

Best regards,

Blaise
2 years 3 months ago #59549
The topic has been locked.
  • Posts: 47
  • Thank you received: 0

Hi

No worries. I only tested it on arm7 and amd64. but the patch should not break the code for already supported targets.

It is on my list of things to do, but one thing that needs checking is if the patch introduces old frames (i.e. frame from n-1 shot, where n is the current shot number) being served. If that is the case, we need to also retrieve the frame when calling SVB_EXPOSURE.

Thanks
2 years 3 months ago #59550
The topic has been locked.
  • Posts: 67
  • Thank you received: 0
Do you know if KStars/Ekos supports showing live video from the SV305?
I tried both the remote version running on my RPi and the Windows version connected to the INDI Web Manager also running on the RPi.
All I got was a black screen.

I confirmed the camera is still working with SharpCap on Windows.
2 years 2 months ago #59782
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello,

Liveview should work.

I get some "chess board effects" in B&W, due to the bayer matrix, but if you toggle the "bayer" button, it works well.
(no resize, ROI or binning, just basic streaming)
Do you get a black screen ?
The default exposure time in liveview is very short. Streamed frames are very dark.

Best regards.

Blaise
2 years 2 months ago #59879
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi Sarwar,

I did some test this week-end.

Murphy's law...
I wasn't able to reproduce de gain issue with my non patched version...

I re-forked a clean version of the official indi 3rd party repo.
I commited your corrections.

I will test a bit more before sending a PR, but you're right, your patch shouldn't break anything.

Best regards.

Blaise
2 years 2 months ago #59881
The topic has been locked.
  • Posts: 67
  • Thank you received: 0
Thanks Blaise.

I just tried another test and I'm getting some light now. I don't know why I was getting black the other day. This test was outside light hitting the CCD (or CMOS) directly, with my hand partially blocking the chip.
Exposure time is the default, whatever that is.
Uncovered is light grey (2nd attachment) which I guess is normal.


I'm using AstroDMx for the time-being until I've got this figured out.

Thanks.

Doug
Last edit: 2 years 2 months ago by Doug MacGregor.
2 years 2 months ago #59884
Attachments:
The topic has been locked.
Time to create page: 0.625 seconds