×

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
Hello Jasem,

Thanks.
Right, in your ser file, frame size fields are empty (0).
Weird...

I can't reproduce the issue, with both the 1.2.6 (actually available in your launchpad) and the 1.2.9 (my last version) versions.

Do you know what could produce this issue :

<< ROI, Binning and gain don't apply to LiveView, unless you trigger a normal capture before >>

Am I doing something wrong ?

Best regards,

Thx8411
2 years 3 months ago #78266
The topic has been locked.
  • Posts: 7
  • Thank you received: 0
I'm trying to get my SV305M Pro working with an astroberry setup and I'm pulling my hair.
I've tried building and installing the lib and drivers from your repo, running the indiserver seperate and from ekos with no success, the output I get is always2021-12-28T21:53:33: [ERROR] Error, get camera pixel size failed2021-12-28T21:53:27: [INFO] Attempting to find the SVBONY SV305 CCD...

And then nothing more, any pointers on what to try next?

Many thanks!
2 years 2 months ago #78895
The topic has been locked.
  • Posts: 152
  • Thank you received: 20
Hi Joakim, have you tried the latest release version of INDI? I have the same camera and with INDI v1.9.3 it is working properly
2 years 2 months ago #78903
The topic has been locked.
  • Posts: 7
  • Thank you received: 0
I built the latest from source in effort to get it working, but maybe a fresh install would do it, I'll give that a go after new years. 

The camera works with the raspberry using AstroDMx (and Sharpcap on windows) so the camera seems fine. 
Are you using 32 or 64 bit OS? 
Also I'm using the raspberry pi 4 8GB, what have you tried it on? 
Cheers
2 years 2 months ago #78944
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi Joakim,

Your error is a bug from the previous SDK. It as been  fixed since.

It looks like a library/package conflict issue.
I think you have the old broken version (standard package installation ?) and the one working installed side by side.
But sadly, your setup uses the wrong one.

Try to identify the old packages, and to remove it.

Best regards,

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

"Don't let nerds have some spare time..."

Let me show you my SV305 Pro F (F stands for "Frankenstein"), my cooled SV305 Pro.

 

 

 

It didn't saw the stars yet, still a prototype.

Happy new year !

Thx8411

 
Last edit: 2 years 2 months ago by Collin.
2 years 2 months ago #78946
Attachments:
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Max delta is 25°C below ambiant temperature.
Stable delta is about 20°C.

"Hot" dark is at 22°C
"Cold" dark is at -1°C

Gain at 360 (half max), 180s.
Amp glow at bottom right.

Best regards,

Thx8411
Last edit: 2 years 2 months ago by Collin.
2 years 2 months ago #78947
Attachments:
The topic has been locked.
  • Posts: 7
  • Thank you received: 0
Pretty sure I tried it before, but now it worked:
sudo apt update
sudo apt upgrade

On the plus side I got the complete dev environment installed in the process 
Many thanks!
2 years 2 months ago #79027
The topic has been locked.
  • Posts: 7
  • Thank you received: 0
Well, that happiness was unfortunately short-lived :/
Pulled an update today (sudo apt-get update && sudo apt-get -y dist-upgrade) and now the sv305 driver crashes when I try to connect. Pretty sure the sv305 driver didn't change, but it upgraded some indi packages (my Canon DSLR started working)
I've attached the logs, and this line seems worrying 
<code>INDI Server:  "2022-01-05T00:17:03: Driver indi_sv305_ccd: Impossible IPState 1598309187"</code>
Any idea on what to do?
Cheers!

Edit:
I was after these upgrades the sv305 stopped working (I looked in the apt-get history):
Upgrade: indi-bin:armhf (1.9.2-1, 1.9.3), libindi-data:armhf (1.9.2-1, 1.9.3), libindi-dev:armhf (1.9.2-1, 1.9.3), libindi1:armhf (1.9.2-1, 1.9.3), indi-weather-mqtt:armhf (1.1-1, 1.1-2)
Last edit: 2 years 2 months ago by Joakim. Reason: More info
2 years 2 months ago #79076
Attachments:
The topic has been locked.
  • Posts: 7
  • Thank you received: 0
Update from today's effort

I tried with purging all indi and astroberry packages and then reinstalled them (apt-get, purge, autoremove and install) with the same result as previous, the sv305 driver crashed on connection.

What I tried after that was to purge everything again and compile indi (core and drivers) from source (master branches). After that I can connect to the camera, live stream works but it always crashes when I try a capture. Log attached 

File Attachment:

File Name: sv305-2022-01-05.txt
File Size:186 KB
.

So close..., anyone with any ideas on what to try next?
2 years 2 months ago #79092
Attachments:
The topic has been locked.
Can you use Ekos Debugger to debug the driver? this would give a more valuable trace back.
2 years 2 months ago #79106
The topic has been locked.
  • Posts: 7
  • Thank you received: 0
Hi Jasem!

I'm new to this so I don't know all the tools yet.
I built the ekos debugger according to the instructions in this post: indilib.org/forum/ekos/7245-new-tool-eko....html?start=12#75533
and I got the attached logs by running the indiserver from the tool.

I haven't done c/c++ since my school days and I don't know the the project that well yet, so I don't know what to make of the segfault, any ideas?

Thanks!
2 years 2 months ago #79112
Attachments:
The topic has been locked.
Time to create page: 0.421 seconds