Valid values are 1,2,3 (with property spy on a healthy camera, or with guesswork if you don't have one).īe careful: setting one property may cause other properties to be changed. TH_assert('TempMovSoundRecord != PROP_MOV_SOUND_RECORD_ON', 'PropertySatellite.c', 0x270) PROP_HANDLER:str:PROP_MOVIE_SOUND_RECORD_FOR_CREAT+420:įf85e22c:Đ28f0e13 addeq r0, pc, #304 *'TempMovSoundRecord != PROP_MOV_SOUND_RECORD_ON'
Magic lantern canon t5i wikia code#
let's look at the code (with GPL Tools/ARM console):įf85e364: 'TempMovSoundRecord != PROP_MOV_SOUND_RECORD_ON' You'll see something like:ġ1: 50.637 ERROR ASSERT : PropertySatellite.c, Task = PropMgrġ2: 50.737 ERROR ASSERT : Line 624ġ3: 50.779 ERROR ASSERT : TempMovSoundRecord != PROP_MOV_SOUND_RECORD_ON save a debug log (call "dumpf", see Debugging Magic Lantern) and look for failed asserts. If you know what property you have changed last time, should be easy (you need to know a valid value to restore it). This is possible because Magic Lantern still loads and is running behind the ERR70 dialog. Solution 1 Īttempt to restore a valid value. Go to C mode, change the affected setting back and forth from Canon menu, reboot in CA mode, then reboot in M mode.
Simply reboot the camera without a card and clear the settings. Known properties which may cause this (based on what we experienced during development):
Since you have no access to Canon menu, you can't reset the camera to defaults. Usually, one of the Properties was set to some invalid value and got saved into NVRAM. When you start the camera, you get ERR70 at every startup, even without ML. Solution: start camera with a HDMI monitor. No display, and ERR70 when attempting to go in LiveView / movie. 2.8 Will removing the clock battery help?.2.7 Possible alternative solution (not tested!).1 No display, and ERR70 when attempting to go in LiveView / movie.
0 kommentar(er)
