DIY Electric Car Forums banner
1 - 2 of 7 Posts

· Registered
Joined
·
127 Posts
Here is my friends explanation of it-"cycle by cycle" current limit that does not require manual reset. It is reset each PWM cycle. The PWM clocks a flip flop. The output of the flip flop is ANDed with the PWM. The flip flop is cleared by the over current signal. So the PWM is started on the leading edge of the PWM. It is ended by the end of the PWM or the over current signal - whichever comes first. You need to make sure the flip flop clocks on the leading edge of the PWM signal and a few other such details. If you try to command more than the current limit this limits to the current limit and will run at the current limit rather than shutting off.

He showed me a schematic of it and it looked like an AND gate and a latch. The pwm signal and the latch both went to the AND gate and the circuit would operate as normal but whenever your lem current sensor goes to a certain voltage it triggers the reset of the latch to turn the circuit off for sometime.

I would just like to know has anyone tried this? What are the pros and cons?
What you have described is exactly what is already in place on the open source cougar motor controller. It is very effective that limiting current to what the trim pot is set for. When it is limiting current, it makes the motor make a growling noise from it switching the pwm on and off so quickly.


-Adam
 

· Registered
Joined
·
127 Posts
Maybe I am wrong but from what I understand the p and s motor controller board relies a lot on software whereas this would be strictly a hardware thing that uses just a pwm code with a micro or analog board. If I could build this with 3 or 4 parts why buy that board with 100 or so parts on it?
The open source controller takes the reading from the LEM current sensor and pass' it to the LM393 comparator. The other side of the comparator is a voltage reference generated from a trim pot. If the sensor is above the setting of the trip pot (495 amps to 776 amps) it causes the lm393 to disable the PWM through the NAND gates. The controller then re-enables this on every 4th PWM cycle I believe. But in the end, It is hardware over-current as well as software as a second.

-Adam
 
1 - 2 of 7 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top