John in CR wrote:Until we have torque throttles, we're stuck with what we got, and that reality is a throttle that works differently at different speeds, so the guys doing micros need to get a wire tied in to detect speed. eg at very low speed somewhere in the range of 20-30% throttle from there on up is the same as 100%, but as speed increases that relationship changes to where at high speed anything below say 80% throttle is the same as 0% throttle.
Sure the most critical is the low speed stuff, where it's downright dangerous, so if the MC spreads out the effect of the first 1/4-1/3 of the physical twist to be 50% or so of the electrical range the throttle will be better than what we have, but the increased sensitivity at cruise is going to be bothersome. Something that varies with speed will probably seem weird at first, but someone will have to try it to see if it's comfortable once you're accustomed to it.
Yeah, you might have hit the nail on the head, John! I really like that idea of using the speed of the bike to change the throttle range & sensitivity. It could create a much safer and more fun setup for medium to high powered ebikes and it seems to me that as long as it's smooth it would be easy to get used to. Can just connect a pin on the MC to the speedo or DD hall sensor output to measure the speed directly, or it could be read from CA's serial output (with ~1sec delay, but you also get battery info).
So maybe at 0-5mph, the throttle control ramps up very slowly, 3/4 turn is only 15-20% "throttle". And when the bike is moving close to maximum speed, the throttle ramps up extremely quickly and then gets sensitive over the 80-100% range. In the middle, you have a more flat full range throttle. The software would have to adjust the curve based on speed data, dampening the adjustments so the effective throttle doesn't shift too fast. The only thing I'm wondering is how hard will it be to maintain a constant speed that is not WOT... (add one button cruise control function = fixed?)
Edit: Long term, maybe a better torque throttle is what's needed? I dunno. It seems to me that we're always going to have problems implementing a torque throttle based on measuring input amps and varying the speed selector "throttle" input to the controller. What is needed is a BLDC controller that does this internally and offers a torque throttle input... right?