Will this ever be integrated into Astroberry? I just installed astroberry-server_2.0.4.img on a fresh card, ran the updates, but I still don't see the SV905C, only the SV105/205/305 cameras.
Hello,
How to put the right pixel size in V4L2 for the Svbony SV205 camera, because in V4L2 the size is 4µm x 4µm, while for the SONY IMX179 sensor the size is 1.4µmx1.4µm.
Sylvain
Hello Sylvain.
To set the pixel size, you have to connect your Camera and start the Indi Server first.
Once connected, go to "Image Info" Tab and set Pixel size in the right column. You may also want to set the Max Width and Height of the Camera.
One you are done, click the set button see attached ScreenShot.
Note that the values are unfortunately not kept between sessions. This may be improved in the future.
Last edit: 1 year 7 months ago by Deneb-l. Reason: Forgot to mention tjat value are not kept.
[quote="Here follows two images meant to illustrate what I have been talking about.
Messed up-
Correct?-
"[/quote]
Is there still no one else who have seen this behaviour on their setup?
I tried connecting the camera to a Windows PC, and the same behaviour was still there. USB cable does not matter. Connecting it through the hub on my 533MC or directly to the PC does not matter.
Hello. Good news, I had the same issue with my SVBony cameras (so you are not alone with the issue), bad news, I do not remember how I solved it. What I perfectly remember was that I never had this issue with the camera and AstroDMX (I'm using Ubuntu ) on the same setup so I knew this was not a hardware but a soft/setting matter. I will retrieve my setup this evening and try to post my driver settings in few hours.
Grrrr, several hours later, I retrieved my PC but my Camera is not here and I cannot see my settings unless I start an Indy session with the device plugged-in. Will take a while until I can post. Sorry.
That's alrigt, I am ín no hurry. The mother of all clouds have placed herself over where I live anyway. I haven't seen the stars, and won't see them, for at least a week.
In the meantime, maybe I need to familiarize myself with all the settings available in the INDI drivers.
I have tried astrodmx for few minutes, this was on WIndows. I can at least say that the images from the camera looked different. Will look more into this.
Are you using astroberry ?
Since astroberry's INDI is version 1.9.7 as of July, I am thinking that the drivers and SDK for the SVBONY camera are not up to date.
Can you try to check the version of the SVBONY Camera SDK library by running the following command in terminal ?
This is the what the terminal said:
libSVBCameraSDK.so.1.6.11 (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libSVBCameraSDK.so.1.6.11
libSVBCameraSDK.so.1 (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libSVBCameraSDK.so.1
libSVBCameraSDK.so (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libSVBCameraSDK.so
I thought that I should also perhaps add that there is another annoying issue. Every time that ekos is started and I tries finding and connect to all of my devices. The first attempt will never succed for my camera. I always have to disconnect, press stop and then start again, and now the 305m will be found.
Related to this is that If I ever need to stop ekos, it is very unlikely that it will be able to reconnect to the camera if I start ekos once again. It takes a reboot of the RPi to solve this.
Various fixes have been made to indi-sv305-ccd since INDI 1.9.8.
In particular, the still unreleased INDI 1.9.9? has improved exclusion control and is less likely to freeze.
"Another annoying issue" can be improved by using the latest INDI and indi-svbony-ccd.
If it still freezes, killing all indi processes such as indiserver and indi_svbony_ccd* will usually reconnect to the camera without rebooting.
* In your case, it is indi_sv305_ccd.
I believe that probably the next astroberry release will support up to INDI 1.9.8.
The aforementioned improvements will have to wait further until the next release after 1.9.8.
The latest astroberry INDI is 1.9.7.
From the version of the libSVCameraSDK installed, it appears that the INDI in your environment is 1.9.7.
I don't know the cause for the image being binary.
I think I have seen a similar phenomenon with SV405CC, but I wasn't concerned about it because the image was normal when I reconnected.
Okay, good to hear that things seem to be moving along in a positive direction.
I am a total Linux-noob so will have to look into "killing processes" and such. Rebooting the Pi when I can't connect to the camera takes too danged long.
My experience has been such that because my newly acquired EQ6-R mounts seems to perform badly I am therefore watching over the guiding like a hawk. And I then have noticed that, sporadically, the images will look like that, with all of the dynamic range gone. I have no idea if it has any effect on the guiding, mostly because the guding is bad ALL of the time, and the images only look bad SOME of the time. But I need to try and rule everything out until I can find the cause of my mounts poor guding performance.
Perhaps I should get a guide camera from one of the big brands, such as ZWO, and see if they too show this behaviour. Or, as I am already in the process of getting started, trying out a PC running Windows, and try the svbony camera there..