Duty Accel/Decel commands / Stop All
Posted: Fri Sep 08, 2017 10:32 pm
I've been doing a lot of work with duty accel / decel today and have ran into a few things I'd like to bring up.
I've noticed that the Stop All command in Ion Studio uses the Deccel value when stopping, so not a direct stop, but a slow down and stop, (assuming you have a default decel value set.) Is that by design?
I assumed 'stop all' was a sort of software e-stop so I thought it should force everything to stop abruptly.
I can work around this myself with the below command, but I wanted to check if I should need to do this.
I've also discovered that both the PWM sliders in Ion Studio and the DutyM1() and DutyM2() commands in Python ignore the Decel value and instead use the Accel value for both accelerating and decelerating. I'm assuming this is a bug since it wouldn't make sense to have the decel value if it's not used anywhere. Can you confirm?
I've noticed that the Stop All command in Ion Studio uses the Deccel value when stopping, so not a direct stop, but a slow down and stop, (assuming you have a default decel value set.) Is that by design?
I assumed 'stop all' was a sort of software e-stop so I thought it should force everything to stop abruptly.
I can work around this myself with the below command, but I wanted to check if I should need to do this.
Code: Select all
roboclaw.DutyAccelM1M2(address1, 655360, 0, 655360, 0)