To resolve the issue you have to update your camera to the latest firmware revision. Because of the described firmware bug the lower 32 bits ( 0xDDCCBBAA) of the memory cell get chopped away during the conversion and only the 0x0000000E remainder makes it into the final string resulting in erroneous “14” serial number being reported back to ShutterCheck.įrom our testing, the following cameras with specified firmware versions are subject to the S/N issue:ĮOS-1D X (3-2.1.1), 5D Mark III (3-1.1.5), 5D Mark IV (3-1.2.1), 6D (3-1.1.9), 6D Mark II (3-1.0.3), 7D (3-2.0.3), 550D (3-1.0.9), 650D (3-1.0.1), 760D (3-1.0.0), Rebel T4i (3-1.0.1), Rebel T5 (3-1.0.1), Kiss X6i (3-1.0.1). In a full 64-bit big-endian hex it would look as 0x0000000EDDCCBBAA. Imagine you have a serial number 63850724266. Internally in camera a S/N is stored as a 64-bit integer value, so an int-to-string conversion is needed. When ShutterCheck asks a camera about its serial number the special PTP (Picture Transfer Protocol) command is issued and device replies with a S/N in form of a text string. It’s caused by a bug in camera firmware where Canon developers messed-up a simple integer to string conversion by accidentally chopping the lower 32 bits of a serial number. This is a known issue that affects several Canon EOS models with outdated firmware versions. Relaunch the ShutterCheck, reboot your camera and try again.Simultaneous access has unpredictable behaviour - both applications may not work properly. Look for Image Capture, Aperture, Lightroom, EOS Utility, Dropbox and so on. Check that no other application on your Mac is trying to access the camera at the same time.Failure to do so will prevent the app from being able to talk to your camera. If you have macOS 10.15 Catalina you should verify that you’ve granted ShutterCheck the permission to access USB-connected cameras.Active Wi-Fi interface completely disables camera’s USB communication abilities.
Make sure you’re running the latest ShutterCheck version.Please follow these steps in order to fix the issue:
0 kommentar(er)
