ok, here is my issue:

1.29 doesnt run at all. mamba max starts fine, beeps and all, then a red led flashes rapidly. no throttle response, no extra beeps, no nothing.

i flashed back to 1.28, problem solved.
flashed again to 1.29, same thing again. reloaded the settings, nothing changed. default settings, nothing changed. i pretty much tried everything.
1.28 works fine [other than the random startup hesitations], but 1.29 refuses to work.

any ideas?

Did yall remove the KV reading from the 1.27 and 1.28 firmware? My buddy bought a Neu motor and we really think it was miss labeld. It is paired up with a MMPro esc. The neu motor is 4875 KV and is really slow on 2s lipo. He put his other motor back in which is a 4600kv motor and the truck runs great. He is using a 13t pinion on both. I told him to install the 1.28 firmware so he can see what the motor kv is and he said it just says motor info aquired. I guess he will have to wait till monday to call Neu unless you guys have any ideas of things he can check.
Thanks,
Alvin

I think that the difference is in the castle link software and not in the firmware..

Castle link 3.255 may show you the KV..

^^^^^^^^^^^^Yep I believe you are right. Thanks.

I just bricked my Mamba max trying to update the firmware, tried with and without the usb chicklet, and cannot get this esc to come back, just sits there with red and green led's.


I need this for the bash(saturday) is there any workaround

How do I go back to 3.255?

same probrem...

new feature signal the over voltage in the esc..
is possible remove this

I use the sidewinder in the my 1/16 e-revo in 4s configuration....
:whip::whip::whip: is possible remove this :whip::whip::whip:

why this version not show the KV motor?

sorry for my bad english...
tanks in advance Luca

Over voltage detection feature is to prevent people from blowing up their escs by using them outside of specification. :rules:

The kv detection feature was removed to stop people from phoning up asking why their 2200kv neu motor was being reported as a 4400kv motor; the feature is designed for 2 pole motors, the user has to do the math based on how many poles their motor actually has = lots of stuid people didnt understand this and kept phoning up castlecreations to ask for help. No more kv feature = no more phone calls. The kv should be on the motor/ label anyway. :rules:

Roll the firmware back to an earlier version if you dont like the current features. :neutral:

How are people getting on with the torque control as opposed to punch control? I'm still using 70% punch to reduce wheelspin but don't like the time lag effect it gives and am hesitant about trying torque control as i wont be able to adjust it at the track.

Is no one using torque control?:whistle:

For those of use who have the Blur version of the MMM, HPI has not allowed Castle to release the newest firmware with that feature yet.

1.29 Feedback:

Firmware does not work with 6s and the Tekin 1400kv motor w/o the sensors. (haven't tried the sensors yet.) Even with torque control disabled, the motor will have no torque and spin at about one rotation per second, even at full throttle. Another person had the same problem with 4s using the Tekin 2050 also without the sensors. In my case I am able to run the 1400 with 4s with an occasional glitch (delay in throttle followed by a sudden burst of power). No issues running the 1400 on just 2s :lol:.

I've installed and reinstalled V1.29 three times with the same result. Esc is the MMP.

I had the same problem with my MMP/TEKIN 1700kv sensorless. Its smooth as silk running sensored now. On the other hand i have 2 MMM that i upgraded the firmware on have that problem also. I also have two other MMM that i didnt upgrade the firmware and they are fine.

I don't have a flux etc to test it on but pretty sure that would take me about 5 mins to change if you were interested... :whistle:

Is it a Castle Link registry mod or do you need the ESC to do the mod on?

Probably just a db update.

Changed it to a 5 min update but it would be all done on your PC - I'm NOT going to post it up though unless I get an OK wink from the castle guys...

They always do good by me and I don't want to upset them or anything they have with HPI or Axial.

We've bought them enough pizza....

:lol:

Haha I've sent more since then Neil :)

They'll get another batch soon when the next project is completed for sure... I owe Lee, Thomas and Patrick big time...

OH yeah, totally a small db mod. :)

I may have a problem with my MMP. I swapped in the MMP in my Revo conversion, using a Tekin 2000kv on 4s. It ran beautifully with the MMM. But when I put the MMP in, it just sits there and jerks and jitters. A video below:

http://s11.photobucket.com/albums/a1...=Video0006.mp4

I've tried 3 different motors with the MMP and all do this. I've tried a couple different setting and different firmwares but no luck.

Bad esc or help?

I updated to the newest Beta Firmware, and now my MMM won't receive any settings, nor will it arm by itself. The red light is very very feint, and is flashing. Please don't tell me that I'm going to have to send this back? I'm hoping I can force some sort of reset? Anyone know?

Btw...when I try to go backwards in Firmware, I get an error that says it didn't install properly. Basically my brains are messed up. Also, it seems that my software can READ my settings, but nothing else.

Thanks

Jason

Hi Jason,

Call tech support -- they should be able to help you out. Usually a second *forced* download will fix the issue.

Thanx!

Patrick

I'll do that. However, I went back to v1.21 which isn't beta, and it works again. I tried incrementally going up to the newest beta version, and that seems to be the problem. My ESC doesn't want anything to do with Beta versions for some reason. I was able to get v1.27 installed, but couldn't get it to send any changes to my ESC. I wasn't able to get v1.28 or 1.29 to install at all. I have two more Mamba Monsters here that I can try, to see if it's just this particular one or not.

P.S. To be honest.. the only reason I want to try these beta versions... is to see how that Torque Control feature works. So, if that's not working for anyone, then perhaps I'll just stick with v1.21 since I'm not having any problems with my MM.

P.M.S - My lipo shut off is set to 3.2v. I'm running a Marinepower 6s pack, which has been amazing. Just want to double check that 3.2v is ok.

Jason

UPDATE: Didn't need to call CC. I did a series of magic tricks, special stunts, and ancient tribal movements, and managed to get it to take hold of and work with Beta v1.24. I then tried my other MM, which was already on v1.24, and it really didn't want to work with anything other than that either. So, I'm feeling a bug... and I'm going to hold off until v1.30.

1.21 or 1.24 are good versions, never had any issues so I've stuck with those on my two MMMs- moderating your throttle finger ~= torque control anyway... :lol:

I called Tech support, Thomas said sounds like 1 phase of the MMP went out. I'll send it in for repairs.

Hello, firware update the beta is running smoothly?
I have wanted to test the torque control, but I like to have technical problems while I'm at the other end of the map.
Far to send to service ...
Greetings.

This post was edited by yours truly

:whistle: