I had tested this a few Rev’s back and found it wasn’t functioning (from S-curve code) but I thought this was fixed. The 1st symptom is it isn’t updated in Mission Planner when a change is made on the transmitter and the Screen refreshed. And then it doesn’t seem to work in an actual Mission.
Thanks for the report, I’ve added it to the list. I’m pretty sure that do-change-speed works because we have an autotest so it is difficult to break now. I don’t think we have an autotest for the ch6 tuning knob method but the underlying control is the same. In any case, txs again and if it’s broken I’m sure we can fix it!
Thanks Randy. Yes, the do_change _speed Mission command does work. But the Tune chan method seems to not work.
I gave the ch6 tuning of “WP Speed” a test today and it seems to work. I wonder if you’ve got TUNE = 10, TUNE_MIN = 100 and TUNE_MAX = 1000? (or similar).
A couple of things that could cause problems:
- The speeds held in TUNE_MIN and TUNE_MAX are in cm/s (not m/s)
- The speed can’t be reduced to zero. I think the minimum is 20cm/s
These issues are consistent with Copter-4.1 though I think.
Thanks @rmackay9 I’ll check it out!
BTW-Do you see the WPNav Speed range change on Mission Planners Extended Tuning page when making a change on the transmitter and Refreshing the screen? I changed the Tune Min/Max to 750/2000 (cm/sec) and was checking this and it doesn’t change. It used to. I’ll perform a test flight tomorrow.
So I tested this in SITL.
TUNE_MIN < 20 is not working.
I think this is intentional.
I tested this with TUNE=10, TUNE_MIN=20, TUNE_MAX=1000.
Seems like it is working in SITL.
Yes, apparently so. I’ll make a test flight today but I expect it will work.
Yes, working fine. It was a unit mistake on my part and the Tune Values were too low to be valid.