New Mamba software (beta) posted today

You know what else would be great? If we could set a value where the toque contol would not functon past a certain rpm so it wouldn't work over, say, half throttle. This way it wouldn't affect top speed.

[thzero]

Better yet another curve that we can manipulate based on throttle position.

Originally Posted by alvinsmith75

You know what else would be great? If we could set a value where the toque contol would not functon past a certain rpm so it wouldn't work over, say, half throttle. This way it wouldn't affect top speed.

Hi Guys,

While we're on the subject, I have a Mamba Micro Pro/CM26 combo that I'm very happy with. However, I can't seem to get it to run the kv test to set up Torque Control. My situation is this:

Throttle range just calibrated.
ESC off, no battery connected.
Motor dismounted from truck.
ESC firmware 1.28, castle link 3.255.

Procedure:
1. Plug ESC throttle cable into Field Link Card, card into computer via USB (XP SP2).
2. Castle Link software correctly identifies ESC and reads out settings.
3. Check "Perform Required Motor Test" box in power tab, change torque control setting to 1.0.
4. Click "Update" button.
5. Settings appear to be written to ESC successfully.
6. Unplug throttle cable from Field Link card, plug back into throttle channel on Rx.
7. Turn Tx on, make sure throttle EPA is at max.
8. Turn ESC on. Normal arming sequence proceeds.
9. Run to full throttle. Motor spins up normally.

At this point, it seems like the ESC is just operating normally rather than being in test mode. It's hard to tell looking at a bare motor, but it acts like all my settings were correctly written, I can run forward and reverse with the right lockout setting, etc etc.

Do I have something wrong in the procedure? Anyone else had this happen?

Thanks! I sent an email off to Castle support about this, but I'm not holding my breath waiting for them to debug a beta firmware for me. I'm a software engineer, so I understand that one...