microcontroller for e-bikes article (attn Joe Perez et al)
06-24-2013, 02:16 PM
#2
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,022
Total Cats: 6,590
Interesting.
The current crop of motor controllers are pretty "dumb." Even though they are programmable for things like speed and phase-current limits, they mostly just translate the throttle input to a motor duty cycle. This works on on low-power units, but is very twitchy at higher voltages. (eg: 10% throttle makes the bike want to wheelie from a stop.)
I'm using a piggyback solution at present, with a device called a CycleAnalyst. This computer sits between the throttle and the controller, and takes in data from motor temp and battery current. In addition to various logging and display functions, it also allows you to implement a closed-loop throttle rescaling mode, which turns the throttle into a "current request" function, similar to how a Subaru DBW system works. It generates a synthetic throttle output (to the controller) which aims to achieve a specific amount of current for a given throttle input. Works quite well, and is something which ought to be a part of all current-gen controller ICs.
No reason this couldn't all be integrated into a single box, I'm just not aware of anyone who has done it yet. This looks like a step in the right direction.
The current crop of motor controllers are pretty "dumb." Even though they are programmable for things like speed and phase-current limits, they mostly just translate the throttle input to a motor duty cycle. This works on on low-power units, but is very twitchy at higher voltages. (eg: 10% throttle makes the bike want to wheelie from a stop.)
I'm using a piggyback solution at present, with a device called a CycleAnalyst. This computer sits between the throttle and the controller, and takes in data from motor temp and battery current. In addition to various logging and display functions, it also allows you to implement a closed-loop throttle rescaling mode, which turns the throttle into a "current request" function, similar to how a Subaru DBW system works. It generates a synthetic throttle output (to the controller) which aims to achieve a specific amount of current for a given throttle input. Works quite well, and is something which ought to be a part of all current-gen controller ICs.
No reason this couldn't all be integrated into a single box, I'm just not aware of anyone who has done it yet. This looks like a step in the right direction.
Reply
0
0
06-24-2013, 03:13 PM
#3
Elite Member
Thread Starter
Join Date: Jul 2005
Posts: 6,420
Total Cats: 84
"Current request" is approximately equal to "torque request".
I considered it really dumb to do a fixed duty cycle which translates to motor speed - ergo at low speed and you open the "throttle" slightly you get full torque until the motor is at the target speed.
I considered it really dumb to do a fixed duty cycle which translates to motor speed - ergo at low speed and you open the "throttle" slightly you get full torque until the motor is at the target speed.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
Motorsport-Electronics
ECUs and Tuning
0
09-05-2015 08:02 AM
Mechazawa
Methanol/Water Injection
22
09-08-2007 02:17 PM
