×

INDI Library v1.9.8 Released (29 Sep 2022)

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

INDI Driver for SVBONY cameras

  • Posts: 67
  • Thank you received: 0
I agree.
I don't need to introduce problems while I have it running.
2 years 4 weeks ago #59466

Please Log in or Create an account to join the conversation.

  • 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 weeks ago #59549

Please Log in or Create an account to join the conversation.

  • 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 weeks ago #59550

Please Log in or Create an account to join the conversation.

  • 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 3 weeks ago #59782

Please Log in or Create an account to join the conversation.

  • 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 3 weeks ago #59879

Please Log in or Create an account to join the conversation.

  • 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 3 weeks ago #59881

Please Log in or Create an account to join the conversation.

  • 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 3 weeks ago by Doug MacGregor.
2 years 3 weeks ago #59884
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 10
  • Thank you received: 0
Key knro,
updated via your comment but was still unable to get driver(s) working.
Then I tried another poster's suggestion of changing names of drivers in various locations and then performing same update you posted, still not working (and now the manually built/installed driver versions are unavailable as a choice in indi).

The error I get when trying to start the "SVBONY" driver (only one avail for profile) is: 2020-09-21T22:21:45: [ERROR] Error: unable to open device. Cannot identify /dev/video0: 2, No such file or directory

Should I consider just a fresh Astroberry install and then start over with adding the indi library and functionality? If so, is there a comprehensive guide for that (current build is base AB then added indi lib then built drivers for svbony sv305)? Thanks
2 years 1 week ago #60397

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0
If you are using KStars then do the following...

sudo apt-get -y install indi-sv305

Otherwise download and install the latest version of AstroDMx (0.78.3). It has the driver built-in.
2 years 1 week ago #60398

Please Log in or Create an account to join the conversation.

  • Posts: 10
  • Thank you received: 0
Hey dlwmacgregor,
I've already tried the sudo install (i mention this in the post you replied to) , this resulted in the error mentioned in same post.
I also have ADMx installed, still getting the error above. Before that, I'd built the drivers using instructions here, and those were giving errors as well.
2 years 1 week ago #60399

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0
In that case I would start from scratch with a fresh install of Astroberry and KStars/AstroDMx.

That's what I ended up doing.
2 years 1 week ago #60404

Please Log in or Create an account to join the conversation.

  • Posts: 215
  • Thank you received: 16
I am using the indi-sv305 driver on both a pi3 and pi4 with good success. I am not using Ekos, rather just PHD2 for guiding, local Astrometry.net for plate solving and AstroDMx_Capture for imaging. No issues. I used sudo apt install indi-sv305 after first adding the ppa per the INDI instructions for the pi3, but had to download and compile from github for the pi4. The only compile issues I saw were warning error messages that were not important. Some C programmers will use variables in functions where the sizes don't match if they know the data in the variable will never exceed the limits in runtime. It is a tiny bit sloppy on the compile side, but causes no real runtime error.

Just FYI, I am very happy with the performance of the SV305 as a guide camera on a 240mm x 60mm guide scope binning 4X4. Nice, crispy stars that plate solve with local Astrometry.net in about 15 seconds and make PHD2 very happy.

Sometimes, if you have messed about a bit, your camera may end up on /dev/video1 or some other number besides video0. This can be caused by something else already on video0, restarting indiserver or some other operation involving video devices. Usually, a reboot will reset things and your first instance of the indiserver calling the indi_sv305_ccd will put it on /dev/video0. If that is not the case, then you might have to change the configuration or find whatever is grabbing /dev/video0 first and move it.
SkyWatcher 10" SynScan Goto Dobsonian, SV106 Guide, ZWO ASI178MC, Svbony SV105, SV305, Pi3HQcam, Pi4, DIY WaveShare focuser, Linux Ubuntu, KStars/Ekos, Carte du Ciel/CCDCiel, AstroDMx_Capture, Siril, StarTools, GIMP
2 years 1 week ago #60468

Please Log in or Create an account to join the conversation.

Time to create page: 0.910 seconds