Hi Hades,

Thanks a lot.

Looking at your "raw" file, every byte values are FF :

The good news : it's not an "indi driver" issue
The bad news : it's an SDK issue...

Sorry, I did a mistake with my first "test", it uses the installed system library, not the new one.
Could you please try again with this new one ?

 

Thanks !

Best regards.

Thx8411

Hi Collin, I have run the new test and it looks better. Here is the text output and RAW file:

Scan camera number: 1
Friendly name: SVBONY SV305M PRO
Port type: USB3.0
SN: 01235878729036F4EE2108260009
Device ID: 0x1301
Camera ID: 1
sn: 01235878729036F4EE2108260009
camera maximum width 1920
camera maximum height 1080
camera color space: mono
camera bayer pattern: 2
support bin: 1
support bin: 2
support bin: 0
support img type: 5
support img type: 9
support img type: -1
Max depth: 16
Is trigger camera: YES
=================================
control type: 1
control name: Exposure
control Description: Exposure
Maximum value: 1999999999
minimum value: 7
default value: 30000
is auto supported: YES
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 1 value 996
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 0
control name: Gain
control Description: Gain
Maximum value: 720
minimum value: 0
default value: 10
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 0 value 0
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 9
control name: Contrast
control Description: Contrast
Maximum value: 100
minimum value: 0
default value: 50
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 9 value 50
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 10
control name: Sharpness
control Description: Sharpness
Maximum value: 100
minimum value: 0
default value: 0
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 10 value 0
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 2
control name: Gamma
control Description: Gamma
Maximum value: 1000
minimum value: 0
default value: 100
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 2 value 100
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 8
control name: Frame speed
control Description: Frame speed
Maximum value: 2
minimum value: 0
default value: 1
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 8 value 2
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 13
control name: Offset
control Description: Offset
Maximum value: 255
minimum value: 0
default value: 0
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 13 value 0
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 12
control name: Auto exposure target
control Description: Auto exposure target
Maximum value: 160
minimum value: 60
default value: 100
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 12 value 100
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
=================================
control type: 7
control name: Flip
control Description: Flip
Maximum value: 3
minimum value: 0
default value: 0
is auto supported: NO
is writable: YES
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
control type 7 value 0
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
camera ROI, startX 0, startY 0, width 1920, height 1080, bin 1
camera ROI, startX 0, startY 0, width 800, height 600, bin 1
cameraMode: 0
pixel size 2.900000
write image file SVB_image_0.raw
drop frames: 0
stop camera capture
close camera

 

Thanks!

Thanks,

Right, it looks much better.

I will push this new firmware on my github repo.

Could you please just do on more test, with the cap on the camera ?

Thanks.

Best regards,

Thx8411

Sure, here it is:
 

Edit: I have recently tried AstroDMx and it works with this camera. I have tried it on a clean install of Raspberry Pi OS

Hi Hades,

Good news, thanks to your help, I thing I found the "black frames" issue.

The SV305 and the SV305 PRO both support RAW8 and RAW16 frame format. My driver uses these two formats.
But the SV305M PRO only supports Y8 and Y16 (luminance).
It's the same on a mono camera, but when my driver tries to set the format, it fails, and we get blank frames.

I will work on a fix this week-end.

Best regards,

Thx8411
 

Hello Hades !

I pushed a patch to my repo : github.com/thx8411/indi-3rdparty.git, including
- the last SVBony SDK, fixing the PixelSize issue
- corrections on the SV305M Pro frame format

I hope it will fix the issues.

You will have to

- update your local repo (the "clone" you did some weeks ago)
- build and install libsv305 (again)
- build indi-sv305 and start it (again)

If you have some libraries conflicts, you may check the library used by your indi_sv305_ccd binary with ldd :

> ldd indi_sv305_ccd

Best regards !

Thx8411

Hi Collin, I have compiled the driver and started the indi server. Camera was connected in the Ekos successfully, but the picture was blank. I have tried both single exposure and streaming.
What should be next steps?
hades

Hello Hades,

Sad...

It could be related to the framing mode.
My INDI driver uses the "Soft Trigger mode" instead of the "Normal mode"

Normal : the camera grabs frames endlessly, and we just catch the frames grabbed
Soft Trigger : like a DSLR, if we need a frame, we trigger it, and then read it

Could you please try these new tests (joined to the post), and send me the resulting "pgm" files ?



test2 : normal mode
test3 : trigger mode

The tests now output "pgm" images, you can open it like simple images.

Best regards,

Thx8411

 

Hi Collin, here it is. I have made two sets, one with cap on the camera, second with cap off.
Thank you for your support

Hello Hades,

Thanks a lot.

Damned, both work...

the problem is somewhere else...

I hope I will receive my camera soon, to go faster and further.

Thx8411

Well it is possible that I have done something wrong. How can I check that the current driver is used?
I have this message in terminal: 
Driver ./indi_sv305_ccd: No ISwitch 'FORMAT_RAW12' in SVBONY SV305M PRO 0.FRAME_FORMAT

Hello,

In the previous driver, RAW12 was the recorderddefault value. It doesn't exist any more in the new driver for the SV305M Pro. Did you try to toggle between Y8 and Y16
frame format in the driver settings ?

Thx8411