Quote:
Originally Posted by jyanof
I don't think 'current control' is any more complicated than what you described. By the way, the open revolt software follows a 'current controlled' scheme.
If the software is tuned correctly, the open revolt will never trip the hardware overcurrent circuit. In fact, the hardware overcurrent circuit was put in mostly to prevent an errant software bug from blowing up the controller.
You could probably get a circuit like yours to work with enough time and spare silicon, but you might want to look at the open revolt software. Admittedly, there's a lot of extra stuff in there to handle things like various throttle sensitivities, overtemp protection, serial communication, EEprom settings storage, etc., but the throttle/output current control is pretty basic at its core. Feel free to ask questions...
Looks like Adam has an archive of the software on his website. |
Hi Mate.
Thanks for the info.
I wasn't saying current control was complicated I was saying that you made my system sound more complicated than it really is. Doing it in software is complicated to someone who struggles with software. I am a computer hardware engineer, software has always been a mystery to me. I like hardwired systems where a collection of bits have one dedicated job to do and are not dependent on a xtal clock running a big list. I know computers crash.
My system is about to get its last chance to work. If it blows up again I shall be getting an OpenRevolt system, so I hope it is listening...
cheers again john