×

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: 150
  • Thank you received: 15
that's a very good new. I just received my sv305 and I had requested to SVBONY the lib and api for develop the indi driver.
The only problem for me is that the lib is for X86 achitecture and i drive my telescope from a raspberry. I hope that SVBONY will quickly provide a arm drivers.

I will do a quickly install your driver.
3 years 9 months ago #55786
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi,

Thanks.

I'm used to work with cameras, but INDI development is new to me.
I worked on qastrocam-g2 (sourceforge.net/projects/qastrocam-g2/) some years ago.

At this time, I succeed in grabbing a color frame.
2 bugs to fix :

- Abort Exposure kills the driver at next frame exposure
- I get sometimes twice de same frame.

Is the TimeHit method threaded ? I suppose. So I have to protect resources by mutex ?

I also asked SVBony for the SDK and the USB EndPoints descriptions. I was ok for an NDA, but they just gave me the SDK.
The SDK (and probably the cameras) comes from "CK". Sadly, I don't think they will provide an arm version. The SDK is already 3 years old.
You could perhaps use something like an USB forwarder ?

I use a mini X86 box instead of a raspberry. It's more expensive, but more versatile, with a better power supply.

I'm an IT Manager in real life, with two kids. No much time left for Astronomy and programming ;-)
Stay tuned.

Best regards.

PS : Sorry for my bad English, I'm a French native ;-)
The following user(s) said Thank You: Jasem Mutlaq
Last edit: 3 years 9 months ago by Collin.
3 years 9 months ago #55800
The topic has been locked.
Thank you for the update. So what did they exactly say when you asked for ARM? If they don't have it precompiled, can you ask for sources to compile them yourself under NDA?
3 years 9 months ago #55807
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi,

I didn't ask for the ARM processors.

I just sent a mail to SVBony, asking for the ARM binaries, or the SDK sources (under NDA if needed) if not available.

Wait and see...

You can see my last test here :

drive.google.com/file/d/1dOA9ICZZD3vzm_x...mKW/view?usp=sharing

I wish you a clear sky,

Blaise
3 years 9 months ago #55824
The topic has been locked.
  • Posts: 150
  • Thank you received: 15
Hi Blaise,

i have a sdk version from december 2019 (i deeped a little into the .h and i no version or timestamp are declared into the file).

It is will be cool if svbony share the source of the api with the community.

I tried to get the source (with a git clone github.com/thx8411/indi-3rdparty.git) but i cannot see the indi-sv305...

Ad also, i'm French and it manager.... So funy !
3 years 9 months ago #55827
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi Christian,

Right, it's amazing ;-)

What branch do you use ? All my commits are in the thx8411_sv305 branch, not in master.

Best regards !
3 years 9 months ago #55832
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hello !

I have got a reply form SVBony. I have good news and bad news.

The bad one :

<<
the SDK doesn't support ARM.
>>

And the good one :

<<
The ARM version SDK is in the processing. will be finished soon.
I will let you know it. maybe next week.
>>

Have a nice day !

Blaise
3 years 9 months ago #55854
The topic has been locked.
  • Posts: 150
  • Thank you received: 15
Hello Blaise,

i find that is the good new anymay ! Just the time for finish the development ;-)

i has get the source code. But, where do you install the libs ? that will be cool if the libs been in a directory and linked during build. Il will try to do that and will begin play with driver.

Thank you.

Christian
3 years 9 months ago #55863
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi Christian,

I don't want to touch the main folder at this time, so no integration to the indi third party build process.
To build and install, you must :

1 - For the library :

mkdir <somewhere>/libsv305-build
cd <somewhere>/livsv305-build
cmake <indi third party sources folder>/libsv305
make
sudo make install

2 - Then, to build the driver

mkdir <somewhere>/indi-sv305-build
cd <somewhere>/indi-sv305-build
cmake <indi third party source folders>/indi-sv305
make

3 - To start the server, in the build folder :

indiserver <options> ./indi_sv305_ccd


Best regards,

Blaise
3 years 9 months ago #55876
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi,

I think I managed to get something usable :

- we can capture and loop
- bayer colors are ok
- we can abort
- using trigger mode instead of continuous mode to avoid heat excess

Implementing the CCD_CAN_ABORT was a bit tricky :

- using SDK Pause/Play method crashs (assertion failed in SDK)
- using SDK Uninit/Init method crashs also (assertion failed in SDK)

Switching from trigger mode to continuous mode and back to trigger mode does the trick (it aborts exposure), but we get a junk frame.
I had to grab and drop it.
In my mind, this feature was essential, with a camera able to expose up to 30mn (ok, in real life, without cooling, much much less ;-)).

TODO :

- analog gain control
- ROI
- Binning
- streaming
- code cleaning/comments/logs levels
- extensive testing

Some features are hard coded, but in my mind, it doesn't matter at this time :

- capture always at 1920x1080 -> we will use ROI
- capture always at 16 bits depth (12 bits real) -> better for Astronomy, isn't it ?
- all post processing and automation disabled (WB, anti flicker, auto gain/exposure, digital gain, fast frame, etc).
- camera's "get capability" doesn't report minimal exposure time. Arbitrarily set to 1/10th seconds.

Next step : analog gain control

Best regards,

Blaise
Last edit: 3 years 9 months ago by Collin.
3 years 9 months ago #55938
The topic has been locked.
  • Posts: 150
  • Thank you received: 15
Hello Blaise,

i quick feedback :
- compilation : ok
- launching : ok

2020-06-22T18:28:34: startup: indiserver -v ./indi_sv305_ccd indi_simulator_telescope
2020-06-22T18:28:34: Driver ./indi_sv305_ccd: pid=4571 rfd=3 wfd=6 efd=7
2020-06-22T18:28:34: Driver indi_simulator_telescope: pid=4572 rfd=4 wfd=9 efd=10
2020-06-22T18:28:34: listening to port 7624 on fd 5
2020-06-22T18:28:34: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: Camera(s) found
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on CCD Simulator.FILTER_SLOT
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on CCD Simulator.FILTER_NAME
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on SQM.SKY_QUALITY
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Focuser Simulator.FOCUS_ABSOLUTE_POSITION


but, i cannot see the sv305 driver into kstars if i start indi in local mode. But, i see it if i launch in remote on localhost. but when i try to shoot a picture, the counter decrease to 0 abs kstars crash. I tested with phd2 and i have the same behavior.

Do you have a idea ?

Thank
C.
3 years 9 months ago #55953
The topic has been locked.
  • Posts: 215
  • Thank you received: 16
Fantastic! I have been using AstroDMx_Capture on my x86_64, as it works well with the SVBONY 305, but in my direct communications with SVBONY, they have indicated a programmer was hired to produce the 64 bit SDK for multiple OS platforms (including arm), but that was before CV19 was in full swing. Latest I heard was they expected the SDK to release when they release the 305 Pro, which has a guide port added. The only word I have on that is "soon."

If you require any beta testers, kindly contact me. I'd be pleased to jump right on it.
3 years 9 months ago #55960
The topic has been locked.
Time to create page: 0.501 seconds