First: Welcome to the forums!

Second: Holy run-on sentence BatMan! j/k. :wink:

Hopefully they'll get it right eventually. It IS a bummer having everything done but waiting on one small, yet vital part!

Hooked the MMM back up the Castle Link and it still connects. Yellow light on the MMM comes on. Reset MMM back to defaults. Hooked everything back up and hit the switch.. No Dice. No lights.. No sounds.. Nada.

i would bypass the switch before i tried anything else. i have a mmmv1 and v2 with hours and hours on them . switches died long time ago.

These are the same things that happened to me. Right now, the yellow lights are steady after plugging it in the link. I talked to a rep from CC last night (I have to call at least almost midnight due to time difference) and asked about doing the BrianG mod.

So anyway, I'll be doing Brian's mod but instead of a UBEC(just ordered Dimension Engineering's Sport BEC), I'll be using one of my 6V rx packs from nitro revo. If it doesn't work, I will be shipping a dead MMM to CC and wait a couple of weeks for the replacement ESC to arrive unless Lutach's 10S Chineses ESC arrives first.

Brian, any special wiring diagram/precaution I need to be aware of while doing this with an rx pack? Thanks for your help.

Now that you mentioned it the first few packs on my modded V2 run fine until I change the LVC to a custom 1 and change the brake amount...after that I was able to run it for 15-20mins then it just stop working after serious cogging in forward and reverse....

Not sure if it make sense...not sure how the software affected the HW ...

i would think if the software is "locking up" like a windows pc flashing it and starting from scratch should fix it? did you try that?

That is seeming to be the trend....

Weird thing I was just thinking about when I read this.


I recently had 2 MMMs die on me. A V1 and a V2. I had one of the first 50 or so V2 MMMs that were shipped with the 1.18 software on it. Apparenty it had some sort of LVC program error that didnt cut off the LVC unless you were at less than 1/3 throttle. I read about it on the CC website. They said there were only 50 or so that got out with that version software and the rest were shipped with 1.19. When I read this I checked and found 1.18 on mine so I updated it to 1.19 and the next time I ran it, it died. It only had one race day on it but it had been working perfectly up to that point, and I never got even close to the LVC so I didnt see any 1.18 problem. Didnt really think about it untill jsut now, but I wonder if the software had anything to do with it? :neutral:

I also had a V1 that was running 1.17 and had close to 20 hours of run time on it and was still working well. I updated it to 1.19 at the same time and it died the next time I ran it also.:oh:

I have one V1 left. It still has 1.17 software on it. I am not going to touch it. I has a good 10-12 hours of runtime on it and its still going. I dont know if the software had anything to do with it, but at this point I'm not going to introduce it as a variable. Its working as is. I'm leaving it and I guess I'll se what happens.

Wow I updated both my MMM v2s and have run 1 of them and had no problems.But that might be a problem.Is Thomas from CC in his new thread about the failures asking what software version people are running.

Could just be coincidence, but it just struck me funny that they both went right after the software upgrade is all.

I just saw today that mine too is a 1.18, and I have run it through at least 10 packs on 6S without any problems at all. I upgraded to 1.20, and honestly I'm a bit scared to run it now :(

Run it, has better throttle and no issues

Just came back from running both my MMM powered E-Revo and MM powered E-Maxx, on 6S and 4S respectively. You're right about better throttle response, I tested this out on the E-Maxx and cogging is a lot less apparent on the 7XL. I didn't see any noticeable operating difference in the E-Revo but then I pretty much drive that thing like a 'tard anyway (why else would we run those things on 6S? :D) how ever, the motor seems to run quite a bit cooler now, and the ESC fan didn't nearly operate as regularly as it used to.

me too ive noticed that...i have 5 unit(v3)and the fan come to life at 95F and for a other one unit the fan begin to spin at 125f!!...(both esc had exactly the same set-up)why?????

Well... several reasons. 1st, the calibration routine for temperature is run on the very first power-up of the MMM (which is at our lab in Kansas) -- but the temperature can vary by a few (maybe 5) degrees in the lab (depending on if its a hot day, or a cold day outside...)
2nd, the temperature sensor itself has a few degrees of tolerance.

That's why we set the temperature to a fairly low turn-on temperature. The MMM can run up to 120C (250F) on the heat sink during normal running with no issue at all, and can run up to 200C chip temperature (close to 400F) before any real internal damage starts to happen. We often reflow the solder on the transistors during extreme power testing, (where the solder becomes liquid under the transistors) and in most cases the MMM just keeps right on working normally (until the processor clock shuts down... that happens when the processor internal temperature gets to about 180C -- but that can take a few seconds for the heat to conduct to the processor core. If the processor shuts down, everything just cools off and it restarts a few seconds later, with no issues.)

For production units, we set the shutdown temperature (thermal) at about 90C-100C (about 195F-210F.) I haven't heard of anyone (yet) thermalling a MMM. (let me know if I'm wrong about that!)

I ran the truck again today, and the fan definitely comes on a lot later, and the MMM is quite warm to the touch before the fan comes on. I haven't any kind of thermometer to properly verify the temps, however I'm adamant that the unit runs warmer for longer before the fan spins up. Might this be a sign of a failing fan/thermistor?

thanks....pdelcast...:mdr:now i know why:yes:im reassured:oops: