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.

Messages - l_d_allan

Pages: [1] 2 3 ... 10
Thanks for the coaching. I admit to my shame that much of it is over my head at this point.
Our local library has a book on Lua, which I've checked out. First impression: powerful and impressive language with modern features.

Is there some kind of Canon DSLR simulator / emulator that runs on a Windows desktop computer? If so, this newbie Lua developer wouldn't have to continually take the flash card in and out of the camera and the card reader / writer. At some point, it seems like there could be some wear & tear on the camera, reader, cables, etc.

I recall "back in the day" when doing development for now-ancient Palm Pilot devices, it was much more productive to develop and test with a Palm emulator.

Thanks for the coaching. I admit to my shame that much of it is over my head at this point.

I did use a hold-my-nose work-around to defeat the time-out ... include a camera.shoot() within the loop with 60 second sleep.

Code: [Select]
while battery.level > 90 do
    io.write(battery.level, "% ")

I speculate that the existing Intervalometer functionality + advanced BULB could accomplish my objective by perhaps doing ten five-minute captures. I'll guess that would depend on how healthy or unhealthy the battery was.

I wonder if I would be yet again shooting myself in the foot to baby the battery while sacrificing the shutter.  :-\

I did briefly look around for the equivalent of beep() or blink() functionality within existing ML code, pondering if it might also work-around the time-out.

I tried to use msleep(120000) for a two minute delay within the loop, but that seemed to also time-out. I'll search around for the powersave functionality.

*** Edit ***
I did find a reference to powersave within ML .zip code, but within the binary file I'll scavenge around the forum.

Hope people don't mind that this Lua newbie is re-opening a stale thread to document my baby-steps to get a script to launch

The content of the OP was about attempting to use a Lua script to recover from a bricked camera. Probably not going to happen.

However, to address the question in just the Subject: How do you write a script? ...
Following are a series of simplified baby-steps to modify the existing hello.lua script.

The steps worked for me with a Canon 6d, a 5dm2, and Windows-10 computer. It may or may not work the same for other cameras and platforms:
  • Find ML/scripts directory in the unzipped directory
  • Copy hello.lua to hi_noob.lua
  • Edit hi_noob.lua and change 6th line
    print "Hello, World!"
    print "Hi noob launched. Good job!"
  • Change 14th line
    name  = "Hello, World!"
    name = "Hi noob (press SET here)"
  • Save file
  • Copy hi_noob.lua to the camera's flash card and put back in camera
  • Start the camera.
    Observe the camera's LCD console and check that hi_noob.lua successfully loaded.
  • If it hasn't already been done, activate the lua module and re-start the camera.
    Then confirm that the lua module has OK next to it.
  • Navigate to the MagicLantern menu tab for Scripts (currently two tabs to the left of the Modules tab on my 6d.)
  • Navigate down to select the newly added hi_test which will be identified as "Hi noob (press SET here)"
  • Push the SET button to launch.
  • Drum roll ....
    Did the expected text string with Good job! show up on the camera's LCD console?
  • Press any key to finish the script and return to 'the real world'.
  • If it works, save the hi_noob.lua some place to preclude it getting over-written at your next upgrade.

The are possibly omissions, unnecessary steps, typos, errors, misconceptions, etc. on my part. Assistance appreciated to clean up.

Since this is posted in the Scripting Corner I suppose you wan to run the LUA, "Hello, world!"
... snip ...
That's the beauty of LUA scripts, no special development environment required.

Thanks for the reply. As you mention, it isn't all that difficult once you start grappling with it and get it wrestled to the ground.

I did manage to modify "hello.lua" to "hi_lda.lua", upload to ML/scripts on the SD card and ... magical drum roll ... it worked.

Big Fun!

Now for a script to "Drain Battery to 95 Percent"

Crude PoC version starting to work. Will attempt to drain to 90%. The script shows progress every 10 seconds.

Code: [Select]
function main()
    io.write ("Drain battery to 90% starting at: ", battery.level, "% \nProgress: ")

    while battery.level > 90 do
        io.write(battery.level, "% ")

    print "Press any key to exit."

keymenu =
    name   = "Drain battery to 90 percent",
    help   = "Prints progress of battery-draining on the console. The intent is to extend the life of the Li-Ion battery by avoiding storage at 100%.",
    select = function(this) task.create(main) end,

Intended output to camera's LCD console:
Drain battery to 90% starting at: 93%
Progress: 93% 93% ... 93% 92% 92% 92% 92%
92% 92% ... 92% 91% 91% 91% 91% 91% 91%
91% 91%
Press any key to exit

Problem: seems to work by draining several percent, but then the camera apparently times-out.

Sorry if this has already by asked & answered ....

Is there a tutorial available with step-by-step instructions on getting "Hello, world!" to appear on the LCD of my Canon DLSR's (6d, 5dm2, 600d)?
  • Tool-chain involved, if any.
  • Setup on Windows 10 desktop, if any.
  • How to upload the Lua script to DSLR flash card. My speculation is that it would be similar to updating the ML code and/or modules.
  • How to access and launch the uploaded LUA code to see if it worked.
  • For extra credit, perhaps get a button to light up, or something to beep, or ???

Not tested; it's just how I'd expect it to work.

Sorry if I'm being useless / lazy, but this ML fan-boy is ignorant of Lua scripting. I admit to my shame that I am clueless how to get even something as simple as "Hello, World" to show up on my 6d.

Instead, I looked around and found an existing Lua related thread started by dmilligan. I then did a Reply with your proposed Lua loop.

Quote from: dmilligan
You don't even need to compile this branch, just write your test script and post it in this thread and I'll run it

*** EDIT ***
Starting to work, but seems to time-out. See Feature Request for more info.

This rusty C++ developer (and Lua pre-newbie) hopes a Feature Request can be accomplished with a Lua script suggested by A1ex.

Suggested PoC Lua loop from A1ex earlier today with hard-wired parameters of 10 second delay until battery at 50%:
Code: [Select]
-- Discharge battery until 50%
-- battery.level is reported in percentage
while battery.level > 50 do
    -- optionally print battery level somewhere (exercise for the reader)

tl;dr ? Sorry ...

The intention is to "baby" the Li-Ion battery so that it isn't stored for an extended period of time at 100%. My impression is this can be preferred to get a longer life-time out of the battery. So, maybe our batteries would last 5 years instead of 3?

I realize this issue may be a "Who cares?" ... since reputable knock-off clones aren't that expensive.

Actual script might have a parameter of 90% rather than 50%.

Perhaps issue a "Beep" or "Flash Light" within the loop to confirm something is happening. Or actually cause the text with the Battery Percent to show up on the LCD screen.

To shutdown the camera, the only method I know (at the time of writing) is to set auto power off to some low value, then keep the camrea active while you want it not to shutdown. I know how to reboot the camera on demand (camera.reboot() in Lua), but not how to turn it off.

With the experimental lua_fix or crop_rec_4k builds, powersave is disabled by default while running a simple Lua script:

Thanks! for the prompt reply. Yet again, I'm impressed.

If I read the above correctly, it seems like the second half of my feature request is already possible, at least with an experimental build. Or not?

Code: [Select]
-- Discharge battery until 50%
-- battery.level is reported in percentage
while battery.level > 50 do
    -- optionally print battery level somewhere (exercise for the reader)

When the script ends, the powersave is re-enabled and should turn off the camera after 1 minute (or whatever you have set for auto power off).

Not tested; it's just how I'd expect it to work.

This retired C++ developer guesses that the above Lua loop with 10 sec delay may closely or even fully accomplish the first part of my request for the threshold of 50%. Wow! You know your stuff!

I'll look around for a ML read-me or tutorial on HowTo get started getting lua code written and then uploaded to my 6d/5dm2/600d. Any hints where to look? (which would be greatly appreciated).

    Please consider features related to "battery management"
    • Drain battery to [fill-in-the-blank] percent if over that state-of-charge (SOC).
      My understanding is that to "baby" Li-Ion batteries for longer life, they prefer to be stored at a SOC significantly less than 100%.
    • My K.I.S.S. practice has been to return from a photo event, upload the photos, and plug the batteries used into one or more chargers.
    • More than a few times, this non-professional doesn't take photos for several days or weeks, which is somewhat hard on the battery to sit at high SOC.
    • ...
    • Related feature request:
    • On/Off toggle to not allow battery to be in sleep state with the Power switch ON to go below [fill-in-the-blank] percent.
    • Can happen with Time-Lapses, which can also corrupt the SD card. Why do I know that?  :o
    • The intent is to diminish the occurrences of the battery getting to fully drained status.
      That can also be somewhat hard on the battery, especially if the battery stays at 0% for an extended period of time.
    • ...
    • Corner cases probably make this more complex than I realize.
      Wish this rusty embedded developer (not ARM) had the skills with the ML tool-chain to help implement, but alas, not. Mea culpa.
    • ...
    • A model to perhaps serve as a baseline to reverse engineer:
      My recently acquired Dell laptop has built-in Windows-10 battery management. It seems quite a bit improved since the last time it played with it with Win-7.
      It also has a Dell-specific app for somewhat more advanced battery management capabilities.

    Sorry if something equivalent has already been requested ... or if this rusty ML fan-boy isn't aware that it has already been implemented.

Can I just throw in that this guy may just be biased against canon in favor of Nikon...

Not really sure how relevant that may or may not be, but it's just an observation after looking at the webpage

Stale thread from this inactive ML forum user (sorry to have missed a1ex post on Jan 5, 2016), but is "this guy" ... l_d_allan (OP) or Bill Claff (from PhotonsToPhotos)?

Which webpage, por favor? DPR thread?

And here is an updated 6D "Special Edition" chart for ML Dual-ISO from Bill Claff ... I am unclear how to interpret ...,Canon%20EOS%206D(ML)

This MTFMapper pre-newbie would find it interesting to see MtfMapper charts for the 6D at various settings for ISO and ML DUAL-ISO. My less-than-informed impression is that there is a trade-off of DR for resolution, but I'm fuzzy on how much that amounts to. IIRC, I asked about this is in a thread from about the time when Dual-ISO was originally implemented "way back when".

General Help Q&A / Errors encountered during running of cr2hdr-20bit.exe
« on: September 12, 2016, 03:24:41 PM »
Using 20bit version of cr2hdr-20bit.exe, and date-stamp seems to be: 2015-Nov-24

Following are warnings/errors produced during processing:

Last update: ab1e90c on 2015-11-24 09:50:10 UTC by a1ex:
cr2hdr: moved safeguard from medium_int_wirth to kth_smallest_i...

Active options:
--amaze-edge    : use ...
--cs2x2               : apply ...
--wb=graymax    : set ...
--compress    : Lossless DNG comrpession

Input file    : 160911q_3791_MefSteveGreen.CR2
Attempt to reload aborted
Compilation failed in require at C:/Perl/lib/ line 93.
Compilation failed in require at C:/Perl/lib/IO/ line 269.
BEGIN failed—compilation aborted at C:/Perl/lib/IO/ line 269.
Compilation failed in require at C:/Perl/lib/IO/ line 101.
BEGIN failed—compilation aborted at C:/Perl/lib/IO/ line 101.
Compilation failed in require at C:/Perl/lib/IO/ line 133.
BEGIN failed—compilation aborted at C:/Perl/lib/IO/ line 133.
Compilation failed in require at –e line 162.
**WARNING** Could not identify the camera from EXIF. Assuming 5d MARK III ... actual camera is 6d
... cr2hdr-20bit.exe proceeded and seemed to process OK

Also happened with following files (7 of 426 total .CR2 files)
Input file    : 160911q_3786_MefSteveGreen.CR2
Input file    : 160911q_3788_MefSteveGreen.CR2
Input file    : 160911q_3789_MefSteveGreen.CR2
Input file    : 160911q_3792_MefSteveGreen.CR2
Input file    : 160911q_3793_MefSteveGreen.CR2
Input file    : 160911q_3794_MefSteveGreen.CR2
Input file    : 160911q_3795_MefSteveGreen.CR2

To speed up processing and help keep the desktop computer responsive, I use cr2hdr-20bit.exe with 10 separate below-normal-priority threads in 10 command prompt windows (see next line). Only the first file for 7 of the batches had problems.

for %%n in (0 1 2 3 4 5 6 7 8 9) do start /belownormal for %%c in (1609???_???%%n_*.cr2) do cr2hdr-20bit --compress %%c

I'm hoping ML devs consider preparing a version for the recently announced 5D iv when it becomes generally available.

(and sorry if this is considered trolling).

Hmmm ... I wasn't able to create a "New Topic" in the "Camera Specific Discussion" sub-forum.

Not meaning to be impatient, but did the research on this get to the point of making it into a "Nightly Build"?

The info on the introductory OP from Jan, 2014 seems to indicate it is still experimental if someone is willing and able to do a compile from source. Or not?

Modules Development / Any update to cr2hdr.exe since Dec, 2013?
« on: August 16, 2016, 01:17:12 AM »
Id the cr2hdr.exe from Dec. 7, 2013 the "latest / greatest"?

Seems like there was a 20-bit semi-experimental version that was supposed to be compiled. Or is that the Dec 7, 2013 version?

Scripting Q&A / Beep when zoom lens is at specified focal length
« on: July 16, 2016, 07:39:20 PM »
On the DPR forum for Sony full frames, the issue of "focal length detents" came up. Silly?

Anyway, a member suggested a work-around of having a beep at a specified focal length. That prompted me to suggest it as a feature request to the ML gurus.

After all, if a camera can beep, and put the Focal Length in the EXIF, then it seems like "only magic" involving firmware-only. Correct?

The FR in the Sony forum specifically mentioned FL / 2 (such as 47mm for a 24-70mm zoom).

Obviously, low priority. It was my way of gushing about the ML Devs.  ;D

I appreciate that my Rebel T3i / 600d is back to being actively supported. Thanks!

And it seems the installation has gotten smoother .... don't need to use the old Stable 2.3. Grrrrreat Job!

General Help Q&A / Appreciate help updating the Wikipedia entry for ML. Thx
« on: February 26, 2016, 03:22:27 AM »
I've attempted to update the Wikipedia entry for MagicLantern over the past year or so:

There are several {{citation needed}} warnings, and some information I believe to be accurate has been removed.

  • A version for the 6D is available, but less fully supported because none of the principal developers own the camera.[citation needed] Still true? Or is the 6d now a "1st class supported camera?"
  • A version for the mirror-less EOS M is less mature than fully supported cameras that one or more of the principal developers own.[citation needed] Still true?
  • Project policy is to not develop a version for the pro body 1 series like the 1Dx.
  • has Canon 5d3's available with Magic Lantern installed.

Feature Requests / Re: [DONE] RAW overexposure warning
« on: January 04, 2016, 04:10:35 PM »
The [DONE] in the thread title is a pretty good hint  ;)

Sorry for re-opening this old thread.

Just wanted to express to A1ex and others:
The extraordinarily rapid development of RAW-based histograms/blinkies/zebras/etc (and then Auto-ETTR) is among the top two most impressive feats of software development expertise I've encountered in 45+ years of paid and FOSS s/w development. Beyond humbling.

Camera Emergency Department / Unbricked. Now even more of an ML FanBoy
« on: December 30, 2015, 06:42:28 PM »
Yay! Im glad its okay! Walter saved the day! I had a feeling it had something to do with the SD card.
I'm very relieved and happy. AND APPRECIATIVE !!!

I remain an ML FanBoy  :D   And I will be Extra Careful when I get around to re-installing the latest/greatest Nightly Build of the 6d ML.  Plus, refresh the 600d-ML.

Without diminishing Walter's role, I think it was a team effort from both of you.

You two can decide how to split up your fee.  :-\

Summary of status: 6d un-bricked. Seems to be back to fully operational in Canon o/s firmware mode. ML not yet re-installed.

Correct me if I'm wrong but you shouldnt have to do a deep format on the computer to get rid of Bootable part of the SD card. Try what's mentioned above.
1. Format in card reader on computer normal or deep
2. Then try to power on 6d and Format SD on 6d normal or deep.

The 6d should boot fine.

WS: Using ML with this card on both cams will not work and it is not intended to do that.

Sorry, we are still having something of a "failure to communicate" ...  :o

And thanks for your (and Walter Schultz) continued patience to resolve this.

DONT format in a different camera and then put back in the 6d. It might not be getting rid of the bootable part of the card.
OK and correct. Even after a "low level" format (trash-can) on the 600d, there was still some residue of 600d-ML, to my surprise.
If you insert a card that is bootable with no ML files on in into and camera with the booflag set, it will not turn on.
The 6d actually partly powered up, but there was an error message:

Magic Lantern

The 6d wouldn't power off. I had to remove the battery to power off.
  • Did a Quick-Format on the SD-600d in a USB-2 card-reader known to be good. That succeeded.
  • Installed SD-600d in 6d.
  • Powered-up.
  • "IT's ALIVE !!!! "
  • Did low-level format (trash-can) with 6d.
  • Powered on and off five times, each time successfully.
So if the camera doesn't boot after using a freshly formated from your computer SD card with a genuine 6D Canon battery then there is an issue.
I would buy a new card or battery too but that's me.
OK. Seems un-bricked. THANKS!

For now, I'm going to leave ML off what was the SD-600d card.

Also, the older USB-3 card-reader may not be working correctly. I got it when USB-3 first emerged, so it is fairly ancient. The USB-2 card-reader is even older, but has been very reliable. One of the USB connectors on the desktop is about worn-out. (Sometimes, it's amazing that it works at all?)

The former SD-6d card appears to be corrupted and unusable. I did a Quck-Format on it with the same USB-2 card reader (succeeded), but the 6d returned to "semi-bricked" state. I've put white electrical tape on it, marked it with a big Question-Mark ("?"), and put in in a "junk" area for now. I'll be on the look-out for a good price on another 32 GB SanDisk SD card. I'll also plan to get a modern, name-brand card-reader.

For now, the 600d doesn't have an SD card, so in not operational. The 6d has a "vanilla" SD card with no ML installed. That's ok for now.

In a week or three when "the dust settles" and I have fresh SD cards, I may go about getting ML back on the 6d and 600d. I may start with the "Stable" 2.3 version, and go from there.

WS: I realize that each camera has to have the correct version of ML on it. I would never expect a card with ML-6d to work in a 600d, or a card with ML-600d to work in a 6d. But, I do appreciate your thorough and patient guidance.

Sorry if I was unclear.
  • I took the SD card from the 600d (aka SD-600d) with working ML, and put it in the 6d. I was hoping the 6d might power up to Canon OS, or give a ML error message. Not un-expectedly, on power-up, the 6d remained in a state of "semi-bricked". In retrospect, I probably wouldn't do that again. I can see where the misunderstanding comes from.
  • I did a "deep format" (with trash-can) of that SD-600d  card in the 600d. Format seemed to work fine. The 6d was not able to do that format, as it was semi-bricked.
  • I put deep-formated SD-600d in the 6d. I tried several times to power-up the 6d, and each time, it booted to the Canon O/S. Whew.
  • I used a card-reader to put the latest/greatest (at the time) nightly build for the 6d on SD-600d, including the ML-SETUP.FIR file.
  • I put the deep-formatted SD-600d with 6d-ML in the 6d and attempted to power-up. It was back to being "semi-bricked". (not whew  :-X )

Good points. However, at this point I don't actually have an SD card that is known to be "a good bootable ML card".

The closest is an SD card that had a working ML on my Rebel T3i/600d. IIRC, the 6d wouldn't boot with that card directly out of the 600d (non unexpected). Note: the latest/greatest ML for the 600d was from back in April, 2015.

However, when I did a "deep format" of that card using the 600d, the 6d would boot normally to the Canon O/S (whew). At that time I didn't try a shutter activation.

My recollection is that I then used a card-reader to put the latest/greatest 6d ML (Nov, 2015 at the time) on that SD card from the 600d, including the .fir file. I'm pretty sure it not only wouldn't boot, but acted like it was bricked ... not even the red power-on would blink. (not whew  :-X )

I'm actually overdue on something so I can't continue. Sorry (and it has been a very long week).

Do you think it would be a good idea to try to get that card from the 600d working again? Perhaps first with "deep format" by the 600d? I don't remember checking if the 600d worked with that card after it had been in the 6d.

Again, THANKS! I'm looking forward to your further thoughts.

Second thing I thought of is maybe your experiencing the battery drain issue that is caused by removing the SD card before the red light blinks and tells you its okay to remove the ML card. This has been known to drain batterys even though the cam is off.
Thanks for the reply ... with reassuring tone.

Nothing has changed, except my memory of just what happened is that much more fuzzy. I haven't had time to do any more wrestling or do diagnostics. Sorry.

Third, is it possible to be more specific on the "glitchy" things you were experiencing other then dead batterys?

Not really ... sorry.

I'd have thought that putting in a formatted, blank SD card with fresh battery would have the 6d back to working in non-ML mode ok, but that is unreliable. I probably should buy a new SD card that has never had ML on it. I've tried a formatted SD card from a Nikon One, but there seems to be some "residue" from being formatted by the Nikon. I think I did a "quick desktop format" with card-reader on it.

Same for SD card my Rebel T3i (600d) that has had ML on it. I used "deep format" with the SD card in the 600d. I've done quick-formats on my desktop with card-reader, but there seems to be remnants that confuse the 6d. I haven't yet tried "non-quick deep format" on the desktop with card-reader.

The 6d will boot with fresh installed battery other than the original 6d LP-E6 and no SD card. Then maybe boot with formatted SD card ... once or twice. Then semi-bricked again.

IIRC, it won't boot with the freshly charged 6d LP-E6 that shows "Green" from the charger, but no SD card installed, but I could be mistaken.

I don't think I've been able to get the 6d to format an SD card, deep or non-deep. I do recall seeing a .log file indicating problems, but I don't recall the specifics. I don't think the 6d has gotten to the state of actually being able to do a shutter activation. Even if it did, I don't think the capture was saved to the SD card.

It has been really hectic here, and will be for at least another week or more. Being methodical hasn't been an option yet. Sorry.

Also I would never ever use a non Canon battery with ML ever. Even if you claim its trusted, ML might not like it.

Good point.

I've noticed the LP-E6 from my 5d2 and 6d aren't truly interchangeable. The chargers are also a bit different. The 6d charger doesn't like to charge the 5d2 LP-E6 battery ... will sometimes go into "never finish" with 4 blinks. The older 5d2 Canon charger seems to charge the 6d battery fine.

Very oddly, the 6d's LP-E6 is just a bit too large to fit in the 5d2 ... it binds up and is tough to extract. I suspected it may be a knock-off / counterfeit, and checked with Canon support. The battery came with the 6d from B&H or Adorama in sealed box. The original 5d2 LP-E6 works ok in both cameras, but it is down to "1 of 3 stars" Recharge Performance. Until this incident, I didn't use the 5d2 that much.

I'm really suspecting the 6d LP-E6 with "2013" marking may be "worn out" somehow, or started off not-perfect and barely within spec, or (unlikely) it was a counterfeit / knock-off. I'm hesitant to purchase a pricey OEM LP-E6 unless nothing else un-bricks the 6d.

Again, THANKS! Hope you and yours had a Merry Christmas. "God bless us, everyone." (Tiny Tim)

My 6d has gotten to the state of being semi-bricked, admittedly at least somewhat operator error. Assistance appreciated.

Sorry for the tl;dr ... I'm attempting to provide all hopefully relevant information, but it no doubt has extraneous info, may be incomplete, or reflect flawed memory (don't get old  :o )

  • Happened December 13. Was using the most recent build at the time from Nov, 2015 ... not the Dec 20, 2015 build which wasn't yet available
  • I'm not sure of the exact sequence, but the following is my best recollection .... sorry, in retrospect, should have kept log.
  • Canon OEM battery with "Recharge Performance 2 of 3" with 100% charge reported. I use either the Canon 5d2 or 6d OEM charger.
  • Happened during lengthy star-trail testing ... time-lapse + BULB stopped by battery going flat
  • Using ML BULB and Intervalometer with "unlimited 4 minute exposures". I've done this at least 50 times with no previous problems.
  • IIRC, the last file was semi-intact and could up uploaded with card-reader to desktop, but some visual glitches indicating corruption ...
  • Don't recall if this was the end of the star trails that night, or if I put in another LP-E6 battery to continue with making a "star trails pano"
  • I always start with the 6d OEM battery, but it is possible I was using a reputable non-OEM battery that has worked very well since I've owned it .... 3 of 3 "Recharge Performance" if that means anything for a non-OEM battery.
  • Recharged battery at home in Canon 6d OEM charger, and all seemed well. Re-installed battery.
  • Star trail ok, since you don't really need the final capture
  • At this point, everything seemed ok
  • 6d seemed bricked on next usage within day or so ... no activity light when turned ON. Did I forget to charge?
  • After 10 slow breathes, diagnosis was that battery was flat. Whew, but ...
  • Did some swapping of other LP-E6 batteries from Canon 5d2, along with other SD card from Canon T3i with ML.
  • Could get 6d to power up with no SD card, but not real reliably.
  • I was running late to get to a Christmas-related event, so I was less-than fully rational on diagnosis efforts. Sorry.
  • Later, 6d with formatted SD card from T3i (maybe by desktop in card-reader) seemed operational, without ML
  • Re-installed ML, not sure on which SD card.
  • Checked FAQ on ML "Camera Emergency Dept" sub-forum, and did the recommended steps ... maybe 2x.
  • I've read about, but not used the "Diagnostic Tools" in this sub-forum. At this point, the 6d is probably unable to run them yet. Is it ok to practice using the "Diagnostic Tools" on a a5d2 or T3i with fully functioning ML while or before working on the 6d?
  • Once before, I've dealt with an apparently bricked f.f. in the past that had ML installed, so at this point it didn't seem like a big deal, and no cause for panic. I don't recall if it was the 5d2 or 6d
  • FWIW: Note that on the DPR forums, I am probably one of the biggest fans of ML ... perhaps the biggest ... almost a fan-boy.
  • The 6d got back to working for a while ... all seemed ok (not sure whether using time-lapse, but pretty sure SD card had Nov, 2015 ML)
  • At this point, everything seemed ok again.
  • Next usage within a day or so ... battery dead again ... back to original semi-bricked
  • Powered off 6d with ML on possibly corrupted SD card seems to be draining battery.
  • When I remove the SD card and battery for 10 to 60+ seconds, 6d will power-on. May or may not work by putting in non-ML SD card with power left on.
  • Batteries other than the 6d OEM card seem to work better ... almost as if the 6d OEM battery has been corrupted somehow
  • IIRC, 6d is glitchy with non-ML SD card.
  • IIRC, powering up 6d with ML disabled (press SET during power up?) doesn't work.
  • With very busy Christmas season, I've been using my 5d2 with Nov, 2015 ML build  (just noticed Dec nightly build ... will install)
  • I regret and apologize that I haven't had the luxury of taking a coherent approach to diagnosis. Fortunately, I've got the 5d2, T3i, etc.

I would Greatly Appreciate help to take a rational, coherent approach to diagnosis and getting the 6d working ok again. It clearly isn't fully bricked, but not really usable, maybe even without ML.

At this point, this volunteer hobby'ist has tens of thousands of captures in my post-processing backlog from about a dozen unpaid Christmas related events. I'm hoping the fix is simple, like replace SD card, but it may not be. I will make every effort to work with anyone willing to help, and check this forum regularly for any replies.

Pages: [1] 2 3 ... 10