@Tom and Pep, are you comfortable with the linux command line ? Could you try this for me :
- login as root
- start the "usbmon" usb kernel sniffer : "modprobe usbmon"
- go to "/sys/kernel/debug/usb/usbmon/"
- plug the camera and look at its usb bus number with the "dmesg" command
You should see something like this :
[ 6508.972745] usb 4-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 6508.993494] usb 4-1: LPM exit latency is zeroed, disabling LPM.
[ 6508.994309] usb 4-1: New USB device found, idVendor=f266, idProduct=9a0a, bcdDevice= 0.00
[ 6508.994313] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6508.994316] usb 4-1: Product: SVBONY SV305PRO
[ 6508.994318] usb 4-1: Manufacturer: SVBONY
in "4-1", 4 is the bus number
- start the SV305PRO INDI driver
- sniff the usb bus with "cat <bus number>u > /tmp/sv305_pro_dump.txt" in the "/sys/kernel/debug/usb/usbmon/" directory
- trigger some frames in INDI
- stop the "cat" command with CTRL-C
- post me the "/tmp/sv305_pro_dump.txt" file back in the forum
I looked a bit forward, sadly, it seems firmware related.
I just sent a mail to Rita at SVBony with the usb dumps.
I hope to have a moment today and be able to try it. They will be images with nothing, as it is raining today but there should be no problem, right?
When I have it I will send it to you. (I hope to know how to do it)
It helped a lot. Your camera works ok on RPi and acts exactly like on AMD64.
I asked myself : How could it be ? Could it be a firmware difference ?
And good news, there is no issue anymore ! (I hope so...)
Just let me explain :
When installing my raspberry, the driver provided by the astroberry repo wasn't up to date (libsv305 vers 1.6.4).
The astroberry repo seems up to date now (since 1st of march ?). After an apt update, I got the libsv305 vers 1.6.5, with the last svbony firmware.
I can't reproduce the issue anymore.
The SV305PRO works now on my RPi.
@Tom and @Pep, could you please check your libsv305 package version ?
It should be 1.6.5 for Tom, and 1.6.4 for Pep.
@All : check your libsv305 package version (it should be 1.6.5) , and please update your indi packages, it should fix the issue.
I have done different tests to see what results I get ... and nothing in the last one I managed to make images of (and without much success, too).
In the attached pdf, you will see a table where I have tried to describe what tests I have done.
In the compressed file are the sv305_pro_dump_vN files of each test (where N is the test number or version, which I named). My dmesg results is like 1-1.3 (connected directly to USB3 port) or 1-1.4.1 (from Hub powered usb3). On "cat " instructions I put "1u" , this is correct, don't you?
I hope it helps you with something ... If I have to clarify something, tell me. Or if some other test needs to be done, too.
I have a raspi4 with 4Gb of ram, astroberry 2.0.3 and I have either connected via VNC (via web) or remotely via PC (Ekos).
Thanks for everything.
I will waiting your news
I didn't know how to check the version but looking at ekos (INDI-Panel) I can tell you I have versions1.1 interface 6
Now I upgrade the lib and I have 1.6.5 version. Is to say I had just had the before one.
I hope it serves.
Today I'll try it and tell you what happen.
I just upgrade the system and works perfectly well.
In VNC mode (web access) and remotely (by Ekos (PC)). The camera is connected directly to the USB3 of the RasPi4 without Power Hub.
In both cases I try to do different exposures (from 0.001s to 60s), videos, guide and works perfect. I check if on 12bits works and works too, but have to much noise (normal, of course).
Now I only need a cloudless sky and check if works guide, in internal mode, from ekos works too.
Thanks a lot Blaise.
I attach the dump files if you will check them. <em>v1C</em> is in VNC mode and <em>v2C</em> is remotely mode.
Thank you. You are a master ... (we will leave the universe for other occasions
Thank you so much for the work you have done and the dedication you had put into it. (By the way, only one thing: the minimum time of the camera is 0.001s but in Ekos you have to set it manually, if you put the minimum with the arrows to go up and down the value continue only accepting 0.01s. Hey! but it do the pictures of 0.001s if you put the value manualy, therefore OK)
I insist, Thank you very much,
Have you noticed that the frames there is 1 frame lag between when you capture using PHD2? i.e. the frame being presented by the driver after nth exposure is actually what was taken during the (n-1)th exposure?
I noticed it before after optimizing my mount to remove DE backlash the impact it has on calibration data is throwing off my guiding.
I had this issue with the very first SDK. (CKCameraSDK). I had to systematically drop the first frame. The first versions of the new SDK (SVBCamera) mostly fixed this issue, with sometime a junk frame.
I didn't notice this issue with last SDK anymore.
I don't use PHD2, but the Ekos internal guider. It works great for me. Did you notice the same issue with the Ekos guider ?