indi-gphoto driver does not work

Bug #777925 reported by Paweł T. Jochym
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libindi
Won't Fix
Undecided
Unassigned

Bug Description

The indi-gphoto driver does not work with any client I could find (kstars, xephem, also others).
Tested with my build from svn as well as with package from launchpad ppa (https://launchpad.net/~mutlaqja/+archive/ppa)
and two canon cameras EOS40D and 500D.
The code attempts to send the testimage.fits file instead of the real file and what is more it is unable to transmit blob data.
The message reads "xxx bytes behind. closing" (or similar - i do not have logs with me).
I have investigated the source a little and there is unconditional code sending test image in place of the real one.
After removing this the code still does not function. The setup works with other imaging sources (QHY5 cam, philips webcam).
I'll be happy to run any tests/patches etc.

Revision history for this message
Jasem Mutlaq (mutlaqja) wrote :

Thanks for the report, will notify the driver's author ASAP.

Revision history for this message
Paweł T. Jochym (jochym) wrote :

It looks like the work-around with -m <size> works. Thanks!
However, I still think there is something fishy going on here.
I have tested it with CCD simulator from the indiserver setting it to the
full resolution of the camera (so huge transfer - essentially the same size
as from my DSLR) and it worked fine - no problem with the transfer (no
compression used). I have tested it even with quite huge frames 10kx10k
(100Mpix) and it still worked. So while the work around works I conclude
that there is still something wrong with the driver.
(I have posted the same message at sourceforge)

Revision history for this message
Jasem Mutlaq (mutlaqja) wrote :

Just run INDI server with large -m so that the client doesn't lag behind traffic. I usually put -m 100

Changed in libindi:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.