The ring light is showing weapon power/PWM requested from the receiver/transmitter? I love how this shows the exponential relation between sustaining speed and current/power draw. 4k rpm -> ~2.5A, 6.3k rpm -> ~6.3A, 8.8k rpm -> ~14.5A, 10.5k rpm -> ~23A, 11.1k rpm -> ~30A So for every 2k rpm increase you're about doubling the power required. Very informative!
The receiver doesn't come into play here. The ring light is sending out the PWM signals itself, that way it's completely repeatable each time. Originally I was manually moving the throttle, but it was hard to be consistent between runs.
Awesome few hits there. Too bad about the magic smoke. Could you have turned off your dual rates to be a bit faster or would that just lead to uncontrollable drive?
There's a fine line between "not fast enough" and "too fast". I think I had the dual rates tuned well this time around (40% max forward), no more wheelie-ing or accidental inverting. Perhaps with a bit more practice/self-control I could speed things up. But this time around I made sure I couldn't shoot myself in the foot.
when I used blheli32 the bot would always twitch backwards after it advances forwards. I run a relatively low reduction and can confidently say how much better AM32 is for drive purposes. I use tekko 45a ESCs. The disadvantage is there's less settings and using an ST link to directly reprogram is hard, but it's made the world of a difference. My bot is built with drive in heavy consideration, so it's cool to see similar results.
Wondering if using a higher pole count motor would give better control at lower speeds, regardless of the firmware. (Assuming such a motor is available in a similar form factor) My line of thinking here is that you'd have more switching per revolution, similar to at higher gear ratio.
