Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - eloml

I have a M10, which was permanently blinking at startup. The reason was a stuck shutter blade.
I extensively used the bulb timer on other EOS models without problems.

I will do tests without MLV modules loaded and come back when I have got results.
No I can't reproduce the issue. Last night I took ~300 shots without failure. The night before it happend after 146 shots. After that I took 700 dark frames without problems.
I use the camera since 8 months and I didn't change settings or ML version. However, I installed mlv_rec/ 2 month ago, but I didn't use it when failures occured. The issue never occured before I added the modules.

My settings are:

# Magic Lantern lua_fix.2019Mar20.6D116 (e98cf272a50b (lua_fix) tip)
# Built on 2019-03-20 09:34:44 UTC by jenkins@nightly
# Configuration saved on 2021/03/01 15:52:01
beta.warn = 1
menu.first = -16
rec_indicator = 1
fps.override.idx = 11
fps.override = 1
bulb.display.mode = 1
bulb.timer = 1
bulb.duration = 180
interval.start.time = 5
interval.time = 0
global.draw = 0
disp.mode.x = 70

0 3F7BAFD0 3E4A97C4 Expo\ISO
0 3FF8700A 3DEBCD77 Expo\Shutter
0 40CD95B3 3B91AC83 Overlay\Global Draw
0 3F6D094C 3A2A5592 Overlay\Histogram
0 3F7156EE 3B6CC2E3 Movie\REC indicator
0 4124128F 3D4F21B5 Movie\FPS override
0 3F5FAF75 362D4965 Movie\Image Fine-tuning
0 3FE7FF2E 392FC4D0 Movie\Movie Tweaks
0 3FE60932 38A7AC91 Movie\RAW video
0 4102601C 3BA4B098 Movie\RAW video (MLV)
0 423EBCEF 40C043E8 Shoot\Intervalometer
0 40D5F21B 3F9A4C61 Shoot\Bulb Timer
0 3F6C172C 39E8AE60 Display\Advanced settings
0 3F6C539D 39FFF304 Advanced settings\Force HDMI-VGA
0 3F5FE8B9 363E9D89 FPS override\Desired FPS
0 413707E3 3FDA5D04 Bulb Timer\Exposure duration
0 3F5D75F1 35859E77 Bulb Timer\Display during exposure
0 407645C8 3FD96A39 Intervalometer\Take a pic every
0 3F5DE764 35A1ADD4 Intervalometer\Start after
0 402C2E59 38C2348B RAW video\Advanced...
0 419DFD19 3B5B665A RAW video (MLV)\Resolution
0 41004F7B 39584419 RAW video (MLV)\Aspect Ratio

# Config file for module mlv_rec (MLV_REC.MO) = 1
mlv.res.x = 0
mlv.aspect_ratio = 0
mlv.write_speed = 816
No other crash logs than the LOGnnn.LOG files I cited from.
Auto Power Off is set to 15 minutes, while the bulb timer is set to 30s or 60s.
I use my 6D for astro imaging with the help of the intervalometer of magiclantern-lua_fix.2019Mar20.6D116 .
Several times during the last weeks, the camera stopped shooting without obvious reason. This happend after some tens to some hundreds of images taken. After pressing half-shoot the cam woke up again and continued shooting.
Log-files were dumped upon those accidential breaks. I checked these, but I couldn't identify any error.
The last 30 lines always look like these:

   1406:   827.285 [GUI] SetQFocusAreaSelectableFlag Area(27) Not Found
   1407:   827.405 [GUI] SetQFocusAreaSelectableFlag Area(29) Not Found
   1408:   827.672 [GUI] DlgShootOlcInfo.c SetBmpStateToPopupAeb(0)
   1409:   828.045 [GUI] ChangeSelectedItemColor ChangeColorResource(0)
   1410:   841.448 [MC] (delayed) 1
   1411:   878.238 [WINSYS] DrawUtil Bitmap size=9000
   1412:   908.545 [DISP] [Post]CtrlSrv SetAllPaletteToIndexWithoutEnableEngine(OFF)(0) 0xf764
   1413:   909.636 [DISP] [Post]CtrlSrv ChangePhysicalScreen(OFF)(0)
   1414:   909.782 [DISP] SetBitmapVramAddress BitmapAddr:0x40d3c008
   1415:   919.800 < GUI Lock > GUILock_TurnOnDisplay (PUB)
   1416:   919.862 < GUI Lock > GUILockTask 1
   1417:   919.988 [DISP] [Post]GuiLockTask TurnOnDisplay(OFF)(0)
   1418:   920.204 [DISP] [ME]Enable_Pb = 1 (2434)
   1419:   920.220 [DISP] TurnOnDisplay action Type=0
   1420:   920.240 [DISP] (LCDON)(2440)
   1421:   920.331 [DISP] [TFT]0x00000080
   1422:   920.344 [DISP] [TFT]0x00008080
   1423:   920.945 [DISP] SetBitmapVramAddress BitmapAddr:0x40d3c008
   1424:   921.067 [DISP] MuteONImage (1466)
   1425:   921.443 [GUI] MainEventHandler PROP_DISPSENSOR_CTRL(1)
   1426:   921.510 < GUI Lock > GUILock_TurnOnDisplay (PUB)
   1427:   937.269 [DISP] CurrentBrightness=4 (54,54)
   1428:  1017.786 [DISP] BackLightOn
   1429:  1017.815 [DISP] TurnOnDisplay finish Type=0
   1430:  1017.971 [DISP] [Post]DisplayMgr GUILockWaitCBR(ON)(0) GUILockWaitCBR pParam=0
   1431:  1018.305 < GUI Lock > GUILockTask 1
   1432:  1018.438 [DISP] [Post]GuiLockTask TurnOnDisplay(ON)(0)
   1433:  1018.665 [DISP] [Post]DisplayMgr GUILockWaitCBR(ON)(0) GUILockWaitCBR pParam=0
   1434:  1019.494 [FM] LED Permit
   1435:  1019.543 [FM] LED Permit

Is there anything I overlooked?
Hello all.
I've got a (used) main PCB as a replacment for my 1100D. The original mainboard is close to dead, I fear: I need to remove the battery for more than an hour before I can power it up again. But I was able to get Rom0.bin and Rom1.bin from it and would like to flash these to the replacment PCB in order to get the calibration data to it.
Is there a way to achieve this (for a non-developer)?
I use the ML intervalometer for astro-imaging. Typically, I take 60 sec subs in bulb mode and get an image every 63 seconds. The additional 3 seconds per image I attributed to the storage of the raws and perhaps some lazyness of the intervalometer.
But recently I astro-modded a 1100D (filter & mirror removal, cooling). Thereby I also replaced the shutter by an emulator and did some tests with short exposures. When I came to exposure times below one second I left the bulb mode and selected the exposure time directly. And suddenly, the time loss of 3 seconds was reduced to half a second per image!
Is this a know effect, and if so: where does it comes from?
Scripting Q&A / Re: Where is the Scripts menu?
April 29, 2015, 09:11:34 PM
Quote...  consider this one more vote to get scripting support back.

Me too!
Does LiveView heat the sensor also during regular intervalometer / bulb timer shooting? At least during cold nights during the last weeks here, the results I got were not so bad despite I had actived LiveView permanently. Mostly, the final limitation for resolution was due to bright skies or amp glow of the 1100D.

Anyway, here comes into play the biggest advantage of the 1100D: Its low price. I plan to disassemble the body in order to remove the filters and perhaps the mirror, which starts to shadow at F/4 or below. Thereby, I plan to insert a peltier like I did earlier with an IXUS.
QuoteDo you plan to use it for planetary or deepsky imaging?
For planetary imaging the raw video feature should be useful, but since it's not really available for the 1100D (yet?) I postponed this.
I plan to use the silent mode for bright deepsky objects, e.g. globular clusters, for which exposure times well below a minute are sufficient, at least at high ISOs. (Surprisingly, I found that stripe like artefacts, which look like those produced by CCD readout amplifiers, are not amplified proportionally when I increase the ISO value. Therefore, I prefer to set ISO to 3200, take a large number of images (hundreds to thousands a night), and stack them.)
I recently started using ML on a 1100D for astrophotography. Great!
To gain more flexibility towards short but frequent exposures, I would like to use the silent mode.
Therefore, I installed Cygwin/Yagarto as described in and downloaded the fullres-silent-pics branch (
I failed, however, to compile because of this error: "Makefile.filerules:33: rule for destination ,,entry.o" failed" (translated from the german message, possibly not exactly correct). I found that entry.d was built, but not entry.o. When I executed the build command manually, gcc (4.6.2) also created entry.d, but not entry.o - without error message.
Since I'm not familiar with unix, I don't understand what happens, but it looks to me a bit like a compatibility problem. Is the Cygwin/Yagarto setup still up-to-date?