×

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
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 2 months ago #60404
The topic has been locked.
  • 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 2 months ago #60468
The topic has been locked.
  • 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 2 months ago #60956
The topic has been locked.
  • 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 1 month ago #61006
The topic has been locked.
  • 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 1 month ago #61026
The topic has been locked.
  • 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 1 month ago #61035
The topic has been locked.
  • 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 1 month ago #61037
The topic has been locked.
  • 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 month ago #61057
The topic has been locked.
  • Posts: 215
  • Thank you received: 16
MG!IFOS=> That's the same camera/guide scope/computer platform I am using (except I am using Ubuntu Mate 20.04). I had the best luck with 4x4 bin (as I have said above) with PHD2. 1 second exposure is good for deep sky, but you are going to have to back it down a bit for the Moon and maybe Jupiter as well. About 50-60% gain seems to be a good starting point. I find the guide scope focuses with that camera set at about 2.3 using the scale on the tube. That might save you a few minutes of fiddling to get an image.
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 month ago #61087
The topic has been locked.
  • Posts: 10
  • Thank you received: 0
@JonCarleton Thanks much for the tips, I'll try with those settings tonight and report back
2 years 1 month ago #61099
The topic has been locked.
  • Posts: 13
  • Thank you received: 0

My mount (iEQ 30 Pro) can record PEC, but I must use the guide port in order to do so. That's the only reason.
2 years 1 month ago #61101
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi,

I also own an iEQ30 Pro, and you don't need an ST4 camera for PEC record. Using serial pulses works nice for me.

I did many tests in "real conditions" (on Mars) these days. No more "Gain settings" issues. Pull Request on it's way...
Thanks again Sarwar.
Sorry to be so late. Clouds, clouds, clouds.... One month of clouds...

I'm waiting for an SV305 Pro sample from SVBony, in order to fix the driver.

Best regards,

Blaise
The following user(s) said Thank You: Connor Ness
2 years 1 month ago #62153
The topic has been locked.
Time to create page: 0.774 seconds