[Dr_C2]

Some more progress…

1/ I found a method for de-activating the ‘motor-stalled’ cut-out which is important for very low speed handling. It makes sense to set a throttle threshold (perhaps 25%) for re-engaging the motor-stalled cut-out. This can all be handled inside the decoder firmware. Decoder damage during high speed collisions could become a thing of the past.

2/ Next, the TI driver places some stringent demands on the control signals. For bespoke decoders this can be handled by the core decoder firmware itself. But what if  we want to use standard SSD decoders, D132 decoders or even O2 wireless decoders to drive the brushless motors? Here I believe there is a solution too. My design will include an interface IC option which translates the PWM signals from any of the above decoder types to a signal formal as required for the TI brushless motor driver module. If this proves successful, the brushless technology should be compatible with SSD, D132 and O2 control ecosystems using their respective standard decoders.

3/ Meanwhile the tacho signal I showed in my previous post can be fed into the car windscreen display modules I also demonstrated earlier in a separate thread. With a small software tweek the display will default to showing car ID. However, when the LC button is pressed, the idea is, this would switch the display to show rpm in 1000s i.e. a display of 45 would represent 45,000 rpm.

This could be useful as a pit lane diagnostic… lift the rear wheels, throttle to max position then read off the resultant rpm - is it the expected value? 

c