Originally Posted by
Mudcat981
I would run it in free mode then flip the switches one at a time and apply the resistive load to see how the motor responded to loads from a start and from a running motor. Worked very well to determine RPM motors and torque motors.
The only thing with a slave motor and resistive load is that it can't go very low, and you have only very granular resistance, which will slow it down to a certain level (so you only get the torque at the RPM that it'll go down to).
Or does it?
Would a slave motor with a set resistance could be used in place of a flywheel to do a spin up, to get most of the torque curve? It wouldn't go all the way to zero (it'd stop short of the free running RPM), but would it generally work for the rest of the RPM range?
I'd be a bit worried that the torque reading wouldn't be linear through the RPM range, but if you optimize for each given RPM (use the timing that gives you the best torque at each RPM), it could make sense, right?
Originally Posted by
Mudcat981
Plus it was great when you could change brushes, springs, timing, etc. Lot more tuning options than with today’s motors.
Thought of building one again, but with so limited tuning options, the G-Force motor analyzer reads timing and RPM plus amps, though does not check loads is sufficient for now.
For blinky, there's not much to tune, but for boosted, there's a lot of information that you need to optimize the motor, and that's information a dyno can give you (more or less) easily.
The G-Force motor analyzer sounds good enough for blinky, IMHO. Getting the true timing measurement from each sensor is good for getting (more) consistent results from one motor to another, and the amp reading can let you see how much timing is too much.
