ESC Firmware Suggestions
 

The purpose of this thread is to discuss possible firmware improvements for the CC ESCs. Please leave the idle chatter for other threads so CC staff doesn't have to sift through a ton of chaff.


1: Change Punch Control Algorithm
RCM Mike and I were talking this evening and the subject of punch control came up. As I am primarily a basher, I like a higher amount of punch control to help compensate for my fairly heavy trigger finger to smooth out powerful starts.

However, Mike being primarily a racer, feels that punch control is detrimental for anything beyond initial take-off. When taking off, having some punch control is nice to make power delivery smooth, but once you are up to speed, this messes with the timing when hitting the throttle for multiple jumps or rough areas. He would rather have the ESC mirror the throttle input to get a better feel, essentially 0 punch control. And I can see his point.

So, how about a hybrid system? Basically, have the PC (punch control) be a function of static setting and motor rpm. Let's say you have PC set to 60% in the programming. At startup, 100% of that 60% would be in effect. But at say, 1000 rpm 90% of that 60% would be in effect (54% total). And at 2000 rpm, 80% of that 60% would be in effect (48% total). And so on until the rpm is high enough where there would be 0% of that 60% setting in effect (0% total). This would satisfy both groups.


2: Adjustable lipo cutoff.
This has been mentioned by someone else, but I thought I'd throw it here as well. When auto-lipo LVC mode is selected, I assume the default setting is 3.0v/cell. But how about a place where you can set the cutoff threshold to something else, like 3.1v or 3.2v? So, let's say you set this to 3.2v/cell; when you plug in a 4s pack, the LVC will automatically detect the 4s pack and apply the LVC at 12.8v (3.2v*4s) instead of 12v. Then, if you want to do some speed runs, you could plug in a 5s pack and get the LVC at 16v (3.2v*5s). This would allow us to retain the 3.2v/cell LVC "safety net", yet still allow the convenience of auto-lipo mode.


3: Custom arming tones
Ok, this is kinda silly, but still a request. :smile:


4: Programming card
A little tough for many to bring a laptop to the track, so a programming card would be a nice option. Or maybe even a "white paper" on the protocol/signals used so someone (individual or third party) could develop one?


5: ABS braking
I'm not really sure how this would be implemented, but make it so the tires don't lock up on braking. This really should be a settable feature, because I like to powerslide around corners. :smile: The issue would be how does the ESC know the difference between a sliding vehicle and one that is simply stopped because in both situations the motor rpm is monitored. I can also see this conflicting somewhat with the brake force setting, but I'll leave that up to the firmware programmers over there.


6: Increasing braking efficiency
I personally have not compared runtime figures using mechanical brakes vs motor brakes, but some people claim lower runtime with motor brakes despite the regenerative braking feature.


7: Logging function
Of course this is limited by available ESC memory and support components, but maybe some type of rudimentary logging? If memory is short, just take constant voltage and current measurements and continually calculate average and peak values of each based on time and store the values (min A, max A, average A, min V, max V, average V, max temp) into memory for retrieval? Yeah, all the data points over time would be preferable, but not sure if there is enough memory.


8: Trainer Mode
For new users trying to get used to their setup. However, short of effectively reducing the throttle (the same as setting tx EPA), which is not very efficient, the only way I can see this be used is to use this as a "shortcut" setting that adjusts max punch control, max timing, etc all at once.

Ooo a Punch Control Exp. curve! That would be cool. :yes:

What about custom arming tones? :lol: Like a MIDI file or something... Have your truck ring like your phone!

Actually, I was thinking more of a linear value, not exponential. But whatever works.

And custom tones is just plain silly. Besides, I don't think Patrick put tons of memory in the ESC so it can play Nickelback when you turn it on! :tongue: :wink:

Well, It'd be the same as the throttle/brake curve adjustment. Linear, or +- exp.

I know it's silly. Didn't you see the :lol:?

I would like to be able to adjust the settings on my MMM at the track or park (for bashing) without having to lug around a laptop. An idea would be a tuning card or box. Another idea could be to have an onboard data logger that could log say 20mins of data ranging from current, temps, throttle percentage.
But i would happily lug around a laptop and use a temp gun if they could release an MMM that was capable of larger currents regardless of physical size and be capable of say 10s or 12s

I don't know if this is a firmware issue, but it would be nice to see improvements in the efficiency of regenerative braking. For now it seems like mechanical braking gives more runtime in the same setup than esc/motor-braking.

And I don't know if this is possible or already exists, but ABS-braking would be a nice feature.

hi ive got one some sort of launch control like f1 used to thats armed like buy holding the brake on for say 4 seconds.

thanks pete

ABS is a nice feature

Logging features from the ICE

Trainer mode to reduce power so my son can drive the car

I had not thought about the punch control but it addresses some issues I have been having. The illustration about Mike and the Jumps really helped me figure out what was happening.

The program card would also be a big +++++.

Added suggestions offered to the original post....

Beeps for low voltage and over temperature in tandem with the current visual alerts implemented in F/W 1.20 would also be nice.

Current limitter and auto LiFe LVC would be nice :)

all sick ideas:yipi:
more memory would have to be packed into the brain board though:whip:
like the custom arming tones:na:
shaun

Bluetooth connection, program it with your cell phone!

that's probably not that silly...
prolly hard to do and i realise there is limited memory in a mamba based ESC...

a lot of us run 2.4ghz transmitters, some of these like the spektrum and nomadio have a "tranciver" which has the ability to transmit telementery information. if it were pissible, castle could probably tap into this and hence gain a wireless castle link:yipi:

but hey...we all already have awsome ESC's with the mamba and MMM and this programability so how can we complain:neutral:

lol, if it gets too complex, pretty soon you'll have some hacker taking over your R/C. All he has to do is gain control and drive out of your sight and then he has a new vehicle.

Seriously, some of these ideas are very good. However, my original intents was more towards augmenting current functionality and adding things that would be fairly simple and not require 1GB of memory to accomplish.

Brian, 1GB is nothing. :mdr:

http://i52.photobucket.com/albums/g4...h_DSC00338.jpg

But I know what you mean...

lol, I know. I have one of those mircoSD cards in my celly, but in 4GB flavor. Could beat the price at ~$10 (incl a regular SD adaptor) when the 1GB was only $2 less. Anyway, I wonder how tolerant those are to the elements?

They are completely sealed. Just don't flex them too much.

You know the cell phone idea is nice. If they could modify castle link to work with windows mobile, I would be in good shape. Already got the USB and Windows Mobile on my phone.

I was thinking more on the lines of the temperature extremes...

The casing material would need to be changed, but my guess would be the internal transistors can handle anything the ESC could produce. Short of a fire, of course. I don't think the cold would be a problem, except for the casing becoming brittle if it were not changed.

I would do away with the punch control and replace it with a current limiter. That would allow you to handle the initial power like a current limiter and not interfere with the rest of the throttle unless you set it too low and the ESC would feel flat. It would allow better runtime since less current would be flowed for the instant you would be above the current limit. I always liked the current limiters in the ESCs I had. The punch control is not that useful for me compared to the limiter. Punch control seems like a 2 stroke hitting a power band if you set it too hi. It can also be dead acting until it hits the power band.

I tryed the punch control once and forgot i had it on, thought i had a bad 4600 motor. Never used it again, I say lose it

What did you set it for? If around 20-30%, it's hardly noticeable IMO unless you are a hardcore racer.

As for the current limiter, I don't think the current hardware supports this type of measurement. So, that leaves having the ESC detect voltage dips past X amount and pull back on the power until it levels out again. I personally think this would be kinda cool because it would help prevent people with substandard batteries from puffing them, or damaging something else. However, if you have really good batteries that don't drop much voltage under heavy load, the current limiter would be useless.

Again, these ideas are for firmware updates that uses the existing hardware. While some of these ideas hold merit, they require additional circuitry.

I think all these ideas are really good. The cell phone/PDA programing would be a fun touch. I would gladly settle for a speedy that could handle much larger amperage even if double the size of the MMM especially if a HV version

I agree on the current limiter, I was able to run a Neu 1515 1.5D on 18 cells NiMH in a E-Revo with my MGM 16018 and that would have blown the cells apart with a MMM. Also, as the pack loses juice it would limit the current draw to keep the cells above 3v/cell. The previous owner of the ESC ran a 15C 1500 mAH lipo in a MM5700 powered Rustler and it did fine, he tried the same lipo with a MM and it puffed the pack.

Nice thread.... keep the suggestions coming. I'm gonna print out this thread and bring it to the next engineering meeting.

Patrick

I run in the expert class. Current limmiting is the real answer. I run 5s and 6s and the punch at 100%. It does not seem to have much limmiting effect at 6s. I think it must have been setup around a 4s setup. I hope they expand the limmiting capibility.

About ABS... that wouldn't be difficult to implement in theory. When the brakes are applied, there's reverse flow of current, so measuring the size of the wave would allow the ESC to vary the brake at a preset point i.e. when the size of the wave becomes large (when the motor has almost stopped spinning) it will reduce the brake. Of course, there is the problem of when the ESC will know if the vehicle has come to a stop or not. 1:1 vehicles have all sorts of sensors which tell the computer the vehicle is still in motion even when all the wheels are not moving; our humble ESCs will not know how to distinguish between locked wheels during motion and a full stop :(

try the best of both worlds...
maby provisions for an optional hall sencor and magnet could be built into the ESC.
this would allow the ABS part of it to know weather the wheels were locked or not.

this is getting complicated..that's bad:lol:

ABS should be fesable above the start up algorithm.
so once the motor has completed start up phase (motor sound changes to higher pitch) then this point the ESC is gathering info from the motor on the unused phase.
the ESC can use this data in the ABS braking.

so final outcome would be...
ABS at high to medium speeds (where it's needed most..you dont wanna be doing speed runs and lock em up when braking)
and back to normal style when it gets down below the secoring RPM.

sound fesable?

Don't know if this is just firmware or would require hadware updates:
The mmm has an onboard temp.monitor to protect from overheating? It would be nice to be able to plug the mmm into an eagletree data logger or the dx3s receiver (maybe via servo y cable) to be able to monitor/review temps. Same thing goes for reading rpm's.

These things can already be done with the datalogger/dx3s, but it would somehow simplify setting up for temp&rpm.monitoring.

Doubt it is possible without a hardware change but an adjustable bec output would be cool. Even if it was a simple micro screwdriver on a pot that could vary from 5.5 up to 7 volts. I liked overvolting my servo a little bit, 6volts is a bit slow.

I love the idea of cell programming - even if were on a limited scale.

Why does everyone always go on about a portable programmer? I use my Tx to make simple adjustments in the field if I have to.

Is it possible to have RPM limiting? would it be any use? maybe it could be used to run a high kv motor on high voltage.. then again, you could just buy a lower kv motor haha.

Sometimes there's things you want to change that the Tx can't do. For example say you're switching from LiPos to NiMHs and need to turn off the LiPo cutoff. This may be more useful for say the Mamba Max than the Mamba Monster, but it would still be a nice feature to have. I run both LiPos and NiMHs on my MM powered Losi XXX-S and it's a pain to have plug in to my laptop to turn off the LiPo cut off to switch to NiMHbatteries, or I have to risk running LiPos without a cut off.

A programming card similar to the ones that Losi Xcelorin systems come with would be perfect in my opinion. Simple jumper based system.

Check out p25 of Drivers ed, you can switch the lipo cut off from None to 5V to 6V to 9V to 12V. I'm not sure how this works with the Moster (no 5 or 6s options...)

I mean don't get me wrong, a field programmer would be good, but the only thing you really need the computer for is to adjust throttle/brake curves or to set custom values for settings which allow it.

Id like to see option.
Disable switch, so you dont have to worry about switch braking, so you could bypass it, its pain in the ass, when your racing on track and switch decides to go OFF.

New Firmware V3.16
 

I just flashed my MM, I didn't notice any obvious new features.

I'm just wondering what's new with this update?

...won't be able to try it out until tomorrow.

From the CC site

Added release version of firmware for Phoenix-ICE controllers
Added release version of firmware for Mamba Max Pro controllers
Many changes to the Graph-Viewer application used by data-logging controllers