I would assign the motor on off to CMD and try it couple of times. My guess is that if you get the motor on with the CMD command and leave it on before assigning the CMD for other function, it will stay on next time you start. This is just a guess, but as mentioned for me the SumPPM works fine. I also tried the Motor on off, but did not like the logic on it.
On what profile does it start (if CMD (no input) or is set LOW on "no action")
Is the CMD level sent at the start LOW? what if it is MID or HIGH?
What if you assign some other profile than 1 to LOW? Or some other action
What level is your 'Command Assignment' LOW? (micro seconds?)
Just some ideas...
I have Profile 2 on LOW, Profile 1 on MID and Profile 3 on HIGH and it works. (Profile 1 at LOW works also at least with FW 2.3, I have not tested profile 1 and LOW with 2.4)
On what profile does it start (if CMD (no input) or is set LOW on "no action") .... Profile 1
Is the CMD level sent at the start LOW? what if it is MID or HIGH? ... I try on start LOW MID and HIGH. Doesn't work
What if you assign some other profile than 1 to LOW? Or some other action ... Than start de motor's
What level is your 'Command Assignment' LOW? (micro seconds?) ... I dont know whatt you mean
Just some ideas...
I have Profile 2 on LOW, Profile 1 on MID and Profile 3 on HIGH and it works. (Profile 1 at LOW works also at least with FW 2.3, I have not tested profile 1 and LOW with 2.4) .. Doenst work