From: Stephen H. W. <we...@gr...> - 2003-07-21 18:44:26
|
> From: Tobias Klausmann <kla...@sc...> > Date: Mon, 21 Jul 2003 19:43:31 +0200 > > Hi! > > On Mon, 21 Jul 2003, Stephen H. Westin wrote: > > > 0.183359 gphoto2-port(0): Could not find USB device (vendor 0x4a9, product 0x3073). Make sure this device is connected to the computer. > > > > This is your camera. It wasn't found. Does it really work to list files? > > Yes, otherwise I wouldn't know how the first 1200+ pictures I've > archived found their way onto my computer :) > > > > 0.364914 gphoto2-setting(2): Setting key 'port' to value 'usb:' (gphoto2) > > > 0.364944 gphoto2-setting(2): Saving 8 setting(s) to file "/home/klausman/.gphoto/settings" > > > 0.365205 gphoto2-camera(2): Initializing camera... > > > 0.365267 gphoto2-port(0): Could not find USB device (vendor 0x4a9, product 0x3073). Make sure this device is connected to the computer. > > > 0.365326 context(0): An error occurred in the io-library ('Bad parameters'): Could not find USB device (vendor 0x4a9, product 0x3073). Make sure this device is connected to the computer. > > > > See? We didn't establish contact with the camera. This isn't a > > "capture image" problem. Can we see --debug output from a successful > > camera operation? And the output from "cat /proc/bus/usb/devices". > > I've done a few logfiles and experimentation. As it seems, the > camera won't be discovered at all when in "rec mode" and just > crash when asked to capture in "play mode". > > The corresponding logfiles and /proc/bus/usb/devices dumps can be > found here: > http://eric.schwarzvogel.de/~klausman/gp2/ > > capture_play_mode.log trying --capture-image with the cam set to play * > capture_rec_mode.log same, rec mode ** OK, this one is useful. > list_play_mode.log trying --list-files in play mode > list_rec_mode.log same, rec mode This seems to have worked correctly. > * camera crashes on first attempt > > ** camera can be used (dump files, delete files, delete all) > normally but the buttons on the camera have no effect until > camera ist switched off, taken off the bus and let alone for > about 10s, then switched on. That's normal; for the PowerShot cameras, the assumption is that you unplug from USB when you want to use the on-camera controls again. > usb-devices_play_mode.txt after powercycling camera, attach to > usb-devices_rec_mode.txt usb bus and set to play/rec. > > As it seems, the camera is only visible via USB when in play > mode. I agree. And it's normal to set the camera to "play" mode for USB control, even when you want to capture images. > > Come to think of it, is the camera working in PTP mode? A --debug log > > would tell us. > > As far as I can tell, gphoto uses the cam native mode > automatically. That's correct, as I can see from your logs. > In PTP mode there is no "capture" capability, if I > parse --abilities correctly. A limitation of the PTP2 driver, I think; I suspect the hardware can do it, but it would require reverse-engineering of just how Canon handles this in PTP mode. There is definitely a problem: the camera doesn't respond correctly to the "start remote capture mode" command. Here is the interesting bit of your log: 3.575281 canon/usb.c(2): canon_usb_dialogue() cmd 0x13 0x12 0x201 (Remote camera control) 3.575303 canon/usb.c(2): canon_usb_dialogue() called with CONTROL_CAMERA, Camera control init 3.575324 canon/usb.c(2): Payload : 3.575345 canon(3): Hexdump of 8 = 0x8 bytes follows: 0000 00 00 00 00 00 00 00 00- ........ 3.575368 gphoto2-port(2): Writing message (request=0x4 value=0x10 index=0x0 size=88=0x58)... 3.575391 gphoto2-port(3): Hexdump of 88 = 0x58 bytes follows: 0000 18 00 00 00 01 02 00 00-00 00 00 00 00 00 00 00 ................ 0010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 0040 02 00 00 00 13 00 00 12-18 00 00 00 05 00 00 00 ................ 0050 00 00 00 00 00 00 00 00- ........ 3.578074 gphoto2-port(2): Reading 64=0x40 bytes from port... 18.581636 canon/usb.c(2): canon_usb_dialogue: read 1 of 64 bytes failed! (Error reading from the port) 18.581678 canon/canon.c(2): Camera control init returned msg=(nil), datalen=0 18.581715 context(0): Error capturing image *** Error *** Any chance of a USB stream dump from the Windows software? I use SniffUSB, and I can parse that output. -Stephen H. Westin Any information or opinions in this message are mine: they do not represent the position of Cornell University or any of its sponsors. |