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

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

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

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

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.

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.

Hello Christian,

Sad...

What's your architecture ? x64 or x32 ?

In my mind, you wont see this driver in the Ekos list. Ekos doesn't know it yet. You indeed have to start it manualy.
Ensure you use the last commited version.

Could you start the driver with the "-l" (log) option, and send me the resulting file ?
Do you get an "assertion failed" error from the SDK ?

It would be nice to create an Ekos profile with just the sv305 ccd. I didn't try device snooping yet.

Thanks a lot.

Blaise

Hello JonCarleton,

Thanks for your enthusiasm and these informations.

your help will be appreciated !

Best regards,

Blaise

Blaise,

You are welcome. I can test on arm 32 and 64 and x86_64 hardware and have both the 105 and 305 cameras.

I notice you referred to the 305 as a CCD. It is actually a CMOS chip. I made that mistake once on another forum and was rather slammed (repeatedly) for it. Perhaps I can save you from the same fate.

I wish I could assist code-wise, but am a Java/Perl/SQL programmer and truly awful at C, C# and C++. I can compile, install and perhaps fix a few config errors and run, but that's about it.

My usual OS platform is Ubuntu, though I know my way around most Unix/Linux variants running on Intel, AMD, Arm or Sparc.

Hello Jon,

Thanks for your help.

I didn't try the driver on x86 (32bits) yet.
For arm targets, I'm waiting for the SVbony SDK.

Christian seems to have issues I can't reproduce.
It would be nice if you had the time to test my last commit in the thx8411_sv305 branch, from my repo (thx8411 fork).

Just added gain control today.

Thanks for the advice, but I know the difference between CCD and CMOS . I'm referring to CCD because all INDI capture devices inherits from the CCD base class.

Best regards and have a clear sky !

Blaise

Blaise,

Indeed, it was that same issue that led me astray initially as per ccd/cmos.

I will get on the last commit in the thx6411_sv305 branch this evening (US Eastern Daylight Time).

Hi Jon,

Great ! Thanks a lot !

I just added and pushed the subframing capability.

Best regards !

Blaise