I wouldn't call it a lag. It is more of a deadband issue. For example, I have my initial point set at 1.1 msec. My throttle cut is set to 1.045, that is 55 μsec below the initial point. I use this switch to arm the ESC. With the brake switch off, I turn the Throttle Cut off and the motor starts and idles at about 600 rpm with a pulse width of 1.162 μsecs. Once in the air I can turn the brake on and the brake engages when the throttle stick is in full low. At this point the pulse width is 1.058, 42 μsecs below the initial set point. Now it would seem one could set his throttle curve so that one click of the stick would get you back to 1.162 μsec and the motor would start and idle at 600. In actual practice the motor probably would not stop on landing approach even with the brake on so the transition would be seamless. I believe the bottom line is you want the brake setting and idle setting as close together as possible. By the way, I'm using the Jeti Mezon. The Jeti Spins don't seem to want to start at idle so you must jog the stick to get them to start. This means you will always have this deadband between brake and idle. Dave is right the OS doesn't have this problem and as I recall the YGE didn't either. And Kirk you are right, the OS does not work on the Hacker 28 pole motors.

Jim O