Cannot unlock the UI on Canon EOS M50
Antonio Cuni <[email protected]> Mon, 25 May 2020 23:32:54 +0200
| Newsgroups | gmane.comp.multimedia.gphoto.user |
|---|---|
| Message-ID | <CAHPg78xQ309LU_Fm+BU9iWihQD-8pzxZ4HkmEQUvbz+HUVzakA@mail.gmail.com> |
Hello, I have another problem with my EOS M50, regarding UI Lock. I am trying things on two systems and two different libgphoto2 versions, so, first let me try to summarize what are the various configurations. In all cases, I am using a libgphoto2 compiled by me from the git repo. Systems: 1. Ubuntu 19.04 (intel x86_64) 2. Raspian 9 on Raspberry Pi Zero W libgphoto2 versions: 1. git revision acafc3324 (the current master as of today), let's call it "NEW" 2. git revision 0c45b3615 (a version which I happened to have on my rpi), let's call it "OLD" The first weird thing, is the behavior of the camera as soon as I connect the USB cable, before I even invoke gphoto2: 1. on Ubuntu, I can control the camera as normal 2. on raspberry, whenever I press a button, the LCD displays "BUSY" in the bottom-left corner. After a bit of trial&error, I discovered that if I ran "gphoto2 --set-config uilock=0" with the OLD gphoto, I could get the control of the camera back. But now, with the NEW gphoto2, uilock no longer works: 1. If I set uilock=0, I get the following error: gphoto2 --set-config uilock=0 *** Error *** PTP Device Busy *** Error *** Failed to set new configuration value 0 for configuration entry uilock. *** Error (-110: 'I/O in progress') *** 2. If I set uilock=1, the LCD displays the image of a computer, and the camera is locked. If I try to set uilock=0, I get the same error as above 3. If I run gphoto2 --config and try to set UI LOCK to No, I get "PTP Device Busy" as in point (1) 4. If I run gphoto2 --config and go to "Camera Output", I can see that it's set to "MOBILE2". If I set it to "TFT", I get the liveview back and I can control the camera again. However, as soon as I exit gphoto2 --config, the camera is locked again, and "Camera output" seems to be reset to "MOBILE2". So, two questions: 1. Does anybody know why on rpi I get the annoying "BUSY" message as soon as I connect the camera, and how to fix it? 2. Is there a way to fix the UI LOCK problem with newer lbgphoto2 versions? I attach some of the debug logs which I get when I try to run "--set-config uilock=0", in case they are useful. Thank you, Antonio _______________________________________________ Gphoto-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gphoto-user
rpi-acafc3324-uilock-0.txt.gz
(application/gzip, 84.4 KB) - not displayed
ubuntu-acafc3324-uilock-0.txt.gz
(application/gzip, 82.5 KB) - not displayed
ubuntu-0c45b3615-uilock-0.txt.gz
(application/gzip, 77 KB) - not displayed