×

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
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.

  • Posts: 13
  • Thank you received: 0
I got my sv305 Pro in the mail yesterday, and did some guiding with phd2. This was my first time guiding, but I did identify some periodic error from my ieq30 pro, so I wanted to record the PEC. I do have the sv305p hooked up to the st4 port, and set up the phd2 equipment profile to use an on-camera mount, but the option to "connect" stays grayed out. This is on a rpi4 running astroberry.

If I connect to the camera directly with a windows machine, the on-camera mount "connect" button is available, but the windows driver doesn't seem to support binning, so I couldn't see any stars (class 8 bortle with a full moon).

Is on-camera guiding a WIP for this device yet?
2 years 3 days ago #60956

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

  • Posts: 149
  • Thank you received: 31
Hello,

The guiding features are enabled, but I don't own an SV305 Pro, so, I can go beyond "it should work".
I my mind, the major issue is related to the camera detection (SV305 or SV305 Pro).

I asked SVBony for a camera sample, to test and fix the driver with a real camera.
I hope they will help.

Best regards,

Blaise
2 years 2 days ago #61006

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

  • Posts: 13
  • Thank you received: 0
Cool, hopefully they can provide one. Until then, perhaps I can help?

Looking at a couple of other st4-enabled drivers on github, it seems there needs to be another driver built specifically for the on-camera guiding. Here are a couple of header files for st4 guiders. The first, asi-st4, might be more useful as it also has a separate ccd driver. They both share a similar format though, in that they provide the same methods. Perhaps we need a sv305-st4.h and corresponding cpp file? I don't yet have the sv305 sdk though, so I'm not sure what those would look like beyond what's already common between the asi-st4 and arduino-st4 drivers.
2 years 2 days ago #61026

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

  • Posts: 215
  • Thank you received: 16
I'm presently using a SVBONY305 as the guide camera (not Pro) with PHD2 and the indi_sv305_ccd driver for Ubuntu Mate 20.04 (Raspberry Pi 4b) as a guider. No issues whatsoever. I have found that 4x4 bin works best, though, especially when plate solving. And yes, I realize this is a bit off-topic for a st4 discussion, but I felt it would be useful to manage expectations for binning. My guild scope is a 60mmx240mm.
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 2 days ago #61035

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

  • Posts: 47
  • Thank you received: 0
Yes. Smoothly guiding at .5-.7 rms.

I have a f3.4 scope and with 2x2 binning @ 1.5 sec, I get enough stars to plate solve.

@gingerbreadassassin
Why not use pulse guiding, its better than st4.
2 years 2 days ago #61037

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

  • Posts: 10
  • Thank you received: 0
Reinstalled ABerry (rPi4), installed sv305 and everything works! Now, before I delve into the minutiae, what are some common settings folks here are using for guiding with the sv305 (not the Pro version) ? From comments I'll probably use PHD2, and this will be the *first* time I'm using guided capture, so I'll be spending some time in simulation to get a feel. Any recommendations are helpful - my equipment are: azeq5 mount, sv305 guider through a 60mm SVBONY guide scope, ZWO asi294MC (uncooled) through an Orion f4 Mak Cass (extended to something like 2300mm and thus narrower effective fstop). Targets will start with moon and bright planets, then I'll want to quickly seek out some darker stuff. Thanks for the great help from the forum!
2 years 1 day ago #61057

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

Time to create page: 0.879 seconds