I am re-posting a question from another subforum, with additional info.
I am trying the following MAVProxy commands and keep getting the corresponding results (in both Linux and Windows environments):
open mavproxy (it connects to Bluerov2 normally) arm throttle (motors armed as shown in console) rc 3 1510 (motors start spinning trying to move rov forward) rc 3 1500 (motors continue – although I think they should stop) disarm (motors stop – camera servo starts “hiccup”) arm throttle (motors start spinning) disarm (motors stop);
I was expecting that I could start/stop thrusters with “rc” mavproxy commands, but this doesnot happen.
In addition, I tried the same thing by connecting to the companion raspberry (through “SSH email@example.com”) and issuing the following commands in order to get into MAVProxy:
% sudo screen -ls #to find mavproxy's PID % sudo screen -r "PID" #where "PID" is the process id of mavproxy
This gets me into the running MAVProxy with the prompt:
Then I enter the above MAVProxy commands with the same results.
What is happening and how can I control the bluerov through commands in MAVProxy command line?
PS: During the above tests, I had not QGC running.