Menu
▾
▴
[gphoto-bugs] [ gphoto-Bugs-2891504 ] Timeouts on long exposures
|
From: SourceForge.net <no...@so...> - 2009-11-03 21:27:02
|
Bugs item #2891504, was opened at 2009-11-03 21:27 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=2891504&group_id=8874 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kanoalani () Assigned to: Nobody/Anonymous (nobody) Summary: Timeouts on long exposures Initial Comment: I'm doing long sequences of host driven images using gphoto2 --capture-preview and a Canon 350D and libgphoto 2.4.7. There is a very high error rate, especially when the exposure time is long (ie: more than 1 second). A typical debug logfile is here: http://www.cfht.hawaii.edu/~kanoa/tmp/500timeout.log The relevant lines show: 1.692562 gphoto2-port(2): Getting timeout... 1.692592 gphoto2-port(2): Current timeout: 5000 milliseconds 1.692623 gphoto2-port(2): Setting timeout to 500 millisecond(s)... 1.692655 gphoto2-port(2): Reading 64=0x40 bytes from interrupt endpoint... 2.196482 gphoto2-port(2): Setting timeout to 5000 millisecond(s)... 2.196537 canon/usb.c(0): canon_usb_poll_interrupt_pipe: interrupt read failed af ter 0 tries, 0.504 sec "Timeout reading from or writing to the port" 2.196571 canon/canon/usb.c(2): canon_usb_unlock_keys() ... 2.212636 canon/canon/canon.c(2): Exit release control-- 2.212683 context(0): Error capturing image 2.213123 gphoto2-camera(2): Operation failed! 2.215283 gp-camera(2): Freeing camera.. Tracing some calls backwards I look in: libgphoto2-2.4.7/libgphoto2_port/libgphoto2_port/gphoto2-port.c And find two timeout definitions: GP_PORT_SERIAL is set to 500 milliseconds GP_PORT_USB is set to 5000 milliseconds Taking a stab in the dark I change GP_PORT_SERIAL from 500 milliseconds to 6000 and the errors go away. I see the 6000 ms figure in my new debug files so that is the number that is being applied. I won't pretend to understand how these different timeouts are applied but changing that one parameter seems to make it work like a charm (unless I find out later that is messes something else up). Thanks for the software, it's really great! -Kanoa ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=2891504&group_id=8874 |