×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

INDI Driver for SVBONY cameras

  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic INDI Driver for SVBONY cameras

Dear Tom,

I have try it and in the end I was able to configure INDI as you have told me and PHD2 as well, but there is no way, it keep doing the same (with or without powered hub)
Attached is an image of how I set the INDI for the camera in case there is something not well configurated.
I'm using a Raspi4 with astroberry 2.0.3 all upgraded.
Thanks,

Pep

PD: I see that the option to exposure less than 0.01s not is available yet. (the camera accept from 0.001s to 1800s)
3 years 1 month ago #67159
Attachments:
The topic has been locked.
  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic INDI Driver for SVBONY cameras

Hi Tom,

At the end in PHD2 it's working now ... ... is talking, because it has a lot of adjustment errors in the tracking, but the system is working.
Tracking in Ekos does not work.


And after 50 minutes later camera not connected againon phd2.


Thanks

Pep
Last edit: 3 years 1 month ago by Pep.
3 years 1 month ago #67166
Attachments:
The topic has been locked.
  • Posts: 238
  • Thank you received: 15

Replied by Tom on topic INDI Driver for SVBONY cameras

Hi Pep,

What do you mean by tracking in EKOS? Your mount not connected? You are now using PHD2 in EKOS, not internal guider right?

Tom
3 years 1 month ago #67171
The topic has been locked.
  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic INDI Driver for SVBONY cameras

Dear Tom,

About Ekos guiding: I mean the internal of ekos.
With the external guide that uses PHD2, it works, although in the evening it had an error (after about 50 minutes) when disconnecting the camera and I could no reconecting it to activate it (it was too late and I did not try reset everything. I guess it would have worked :( ).
Although if it were possible to use the internal guidance of the Ekos I would prefer it :kiss: .

The mount (OnStep), which is not connected, was in the afternoon when I tried to configure the settings you commented on, and the OnStep uploaded. But it works and connects well after.

I also need to calibrate mechanically the DEC axis because I have had sudden changes on DEC graphyc. I guess that's why the guide stopped every 4 minutes (approximately). In fact, the graphics were creepy.:unsure: :sick: :silly:

The settings of the changes you told me, I changed it correctly, right? I don't have to change any more, do I?:dry:
Aside from mechanically adjusting the mount, is there anything else I need to do or setup?

I use the sv305Pro camera (by USB3 powered HUB).
I will use the camera as a guide, basically. But when possible, I would also like to do in planetary and moon, but I need to be able to lower the times to 1ms, now it don’t let goes down from 10ms.

Thanks a lot,

Pep
3 years 1 month ago #67188
The topic has been locked.
  • Posts: 238
  • Thank you received: 15

Replied by Tom on topic INDI Driver for SVBONY cameras

Hi Pep,

Basically, that's it. Unless you wish to do something more tricky than I do which is I've downgraded my VL805 EEPROM firmware for rpi4 4GB board to 0137ab. This downgrade process is for my ASI120MC which is USB2.0 to run. I assume you are still running 0138a1 EEPROM firmware which I will avoid.

If you wish to check which version of eeprom firmware you are having, issue this command " sudo rpi-eeprom-update " in terminal.

For planetary and moon imaging, I will recommend you use AstroDMx.

Cheers,
Tom
3 years 1 month ago #67193
The topic has been locked.
  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic INDI Driver for SVBONY cameras

Hi Tom,

Thanks a lot.
I don't have enaught knwolegment for to do something about it.
Then you suggest to upgrade my EEPROM? How do I proceed for do it? Of course, first I check which EEPROM version I have.

Thanks a lot again,
Pep
3 years 1 month ago #67196
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi guys,

Sorry, I was away for a long time. Family business and a lot of work...

I just bought an RPi4, to see what's going on.
It comes from china, so, it could take a while...

My first concern is to check if the SV305 and the SV305 Pro behave the same way.
In my mind, it's USB 2.0/USB 3.0 related.

Possibly, Astro-DMX acts in a way which stresses the camera less.

Best regards,

Thx8411
3 years 1 month ago #67507
The topic has been locked.
  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic INDI Driver for SVBONY cameras

Hi thx8411,

Well been back. :)
It will be an important test that you do. I will be on the lookout for what you post.:woohoo: :)
While you wait, weather permitting, I can do some testing, if you need.
I have a raspi4 with 4Gb of RAM and sv305pro connected to a USB3 powered HUB and this connected to the raspi's USB3 port.

I guess you will have seen my latest reports on some tests I have been doing and the results I have gotten. If you need me to repeat something for more information or ... you know.

If you need somthing you will tell me,

Best regards,

Pep
3 years 1 month ago #67511
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Hi folks !

Thanks for your help Pep. I just got my RPi4 today.
I also got an RPi3. I have to do extensive tests RPi3/RPi4/AMD64, SV305/SV305PRO, USB2/USB3.

I actually reproduce the issue on RPi4/SV305PRO/USB2.
The first frame is OK, but I never get the second one.

First observation, for the first frame, we get the usb bulk datas. For the second one, it never comes.

First frame usb sniffing :

d8139900 1127851687 S Ci:1:006:0 s c0 d0 0001 3000 0001 1 <
d8139900 1127852168 C Ci:1:006:0 0 1 = 08
d8139900 1127853454 S Ci:1:006:0 s c0 d6 0001 0080 0001 1 <
d8139900 1127853916 C Ci:1:006:0 0 1 = 08
d8139900 1127854089 S Ci:1:006:0 s c0 d0 0000 3000 0001 1 <
d8139900 1127854550 C Ci:1:006:0 0 1 = 08
d8139900 1128616063 S Ci:1:006:0 s c0 b9 0000 0000 0002 2 <
d8139900 1128616152 C Ci:1:006:0 0 2 = 0113
d8139900 1128816561 S Ci:1:006:0 s c0 b9 0000 0000 0002 2 <
d8139900 1128816640 C Ci:1:006:0 0 2 = 0113
d8139c00 1128974084 C Bi:1:006:2 0 4147216 = d91a3203 00000000 01000000 00000000 01000100 01000100 01000100 01000100
d8139c00 1129010255 S Bi:1:006:2 -115 4147216 <

The second frame starts the same way :

d8139900 1157854005 S Ci:1:006:0 s c0 d0 0001 3000 0001 1 <
d8139900 1157854480 C Ci:1:006:0 0 1 = 08
d8139900 1157855768 S Ci:1:006:0 s c0 d6 0001 0080 0001 1 <
d8139900 1157856224 C Ci:1:006:0 0 1 = 08
d8139900 1157856399 S Ci:1:006:0 s c0 d0 0000 3000 0001 1 <
d8139900 1157856858 C Ci:1:006:0 0 1 = 08
d8139900 1158203763 S Ci:1:006:0 s c0 b9 0000 0000 0002 2 <
d8139900 1158203849 C Ci:1:006:0 0 2 = 0113
d8139900 1158404259 S Ci:1:006:0 s c0 b9 0000 0000 0002 2 <
d8139900 1158404339 C Ci:1:006:0 0 2 = 0113

But then it loops again and again :

...
d8139900 1158604797 S Ci:1:006:0 s c0 b9 0000 0000 0002 2 <
d8139900 1158604872 C Ci:1:006:0 0 2 = 0113
...

The camera datas never seem ready.


To be continued...
3 years 3 weeks ago #68153
The topic has been locked.
  • Posts: 149
  • Thank you received: 31
Further tests :

RPI3/SV305PRO/USB2 : KO aswell

RPI3/SV305/USB2 : OK
RPI4/SV305/USB2 : OK

usb trace :

d8084480 421735653 S Ci:1:004:0 s c0 d0 0001 3000 0001 1 <
d8084480 421736276 C Ci:1:004:0 0 1 = 08
d80843c0 421737537 S Ci:1:004:0 s c0 d6 0001 0080 0001 1 <
d80843c0 421738157 C Ci:1:004:0 0 1 = 08
d80843c0 421738324 S Ci:1:004:0 s c0 d0 0000 3000 0001 1 <
d80843c0 421738930 C Ci:1:004:0 0 1 = 08
d8084480 422017771 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084480 422017872 C Ci:1:004:0 0 2 = 0112
d8084840 422218284 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084840 422218382 C Ci:1:004:0 0 2 = 0112
d8084900 422419177 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084900 422419277 C Ci:1:004:0 0 2 = 0112
d80849c0 422619683 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d80849c0 422619779 C Ci:1:004:0 0 2 = 0112
d8084a80 422820217 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084a80 422820316 C Ci:1:004:0 0 2 = 0112
d8084b40 423020740 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084b40 423020840 C Ci:1:004:0 0 2 = 0112
d8084cc0 423221250 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084cc0 423221352 C Ci:1:004:0 0 2 = 0112
d8084c00 423421750 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084c00 423421843 C Ci:1:004:0 0 2 = 0112
d8084d80 423622238 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084d80 423622330 C Ci:1:004:0 0 2 = 0112
d8084e40 423822784 S Ci:1:004:0 s c0 b9 0000 0000 0002 2 <
d8084e40 423822891 C Ci:1:004:0 0 2 = 0112
d8084780 423858911 C Bi:1:004:2 0 4147216 = 573cf201 00000000 03000000 00000000 5d019701 5d019201 60019a01 5501a601
d8185240 423895898 S Bi:1:004:2 -115 4147216 <
3 years 3 weeks ago #68157
The topic has been locked.
  • Posts: 238
  • Thank you received: 15

Replied by Tom on topic INDI Driver for SVBONY cameras

Weird.....Mine works well with RPI4 4GB and 8GB board. No more frames stopping. Good luck.

Tom
3 years 3 weeks ago #68161
The topic has been locked.
  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic INDI Driver for SVBONY cameras

Hi Thx8411,

You are the MASTER of the Univers B) :)

Thank you so much for continuing to insist on the issue.:cheer: In fact looking at the answer lines, I see some pattern, but I don’t know what they mean.:oops:
I insist, if I can do something, you tell me.;)
Good luck and I look forward to good news from you regarding the sv305PRO (USB3 to raspi4 4gbRam).

{The SvBony company I know that they are interested that sv305pro works on INDI-Driver. I remember that you had the contact of them, don't it?. Could be a great help}

Thanks,

Pep
3 years 3 weeks ago #68184
The topic has been locked.
Time to create page: 1.198 seconds