Re: Canon 7D locks up with "Full PC" when controlled from Pi1
David Bell <[email protected]>
| Newsgroups | gmane.comp.multimedia.gphoto.user |
|---|---|
| Message-ID | <CWXP265MB0022240BEFCE4E1E61C9F662F6360@CWXP265MB0022.GBRP265.PROD.OUTLOOK.COM> |
Hi Marcus, Thanks for the response! I’m not using gphoto to shoot the picture at all; the actual shot is triggered from an Arduino connected to the exposure trigger. Image is recorded to the CF card as if I were manually pressing the exposure button. (Reason is, I require sub-5ms accuracy for controlling bulb mode. I’m doing bulb-ramped timelapses and gphoto’s part is to switch the ISO.) The error occurs even before shooting the first picture. Reading the ISO (or anything else) too often in a short space of time is enough to put the 7D into the FullPC error state. two new data points: - Raspberry Pi3 also triggers the behaviour - got my hands on a 5D Mk IV. Can not reproduce the problem with that camera. Re Mac - not sure I understand the question; I’m using gphoto2 so I’m implicitly using libgohoto2. But I haven’t built any own program just using libghoto2. But the Mac is just for the cross-check; since it works fine there, it demonstrates that the problem isn’t cross-platform. Regards, Dave ________________________________ From: Marcus Meissner <[email protected]> Sent: Friday, August 24, 2018 8:59 AM To: David Bell Cc: [email protected] Subject: Re: [Gphoto-user] Canon 7D locks up with "Full PC" when controlled from Pi1 Hi, On Wed, Aug 22, 2018 at 10:36:53AM +0200, David Bell wrote: > Hi, > I'm seeing the problem that my 7D (Mark 1) locks up when I do too many > consecutive gphoto2-calls in a short space of time. The message on the > 7D-LCD-display is "Full PC". Once it's in that state, nothing works, and > the error is usually only cleared by power cycling the camera. > > I'm only seeing the problem when the 7D is connected to a Raspberry. Tested > on Pi 1 (running the Pi variant of Debian 8.0), and also on a Pi Zero W > (running debian 9.4). Connected to a Mac, I can't replicate the problem. > > gphoto2 --summary doesn't cause the problem, get-config (for example > gphoto2 --get-config iso) causes the problem. Calling gphoto in, say, less > than 3 second intervals, is very likely to cause the problem; with > intervals over 5s it happens much more seldom. > > Versions in all cases: gphoto-version 2.5.17, libgphoto2 2.5.19, > libgphoto2_port 0.12.0 > > Any idea as to possible causes? Are you using libgphoto2 on the Mac? Two things might be possible: - You did not download all the SDRAM capture pictures. If some are left, the SDRAM of the camera will fill up. - The SDRAM capture mode is also weird a bit. The library tells the EOS camera how much diskspace is left and the camera uses this knowledge. We try to set a fixed high value, but the camera might get confused. First check if you download everything :) Ciao, Marcus ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gphoto-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gphoto-user