I've been trying to get the simple ros_erle_takeoff_land package to work - I followed the readme instructions and YouTube videos to compile and run the package: https://github.com/erlerobot/ros_erle_takeoff_land
I edited the main .cpp file to change the mode from GUIDED to STABILIZE since I don't have a GPS module (otherwise arming fails).
My drone is powered on. The green LED is solid and the orange LED is blinking (so autopilot appears to be properly launched but not armed). Then I run these two commands directly on my Raspberry Pi 3 (not SSHed in):
$ source takeoff_land_ws/devel_isolated/ros_erle_takeoff_land/setup.bash
$ rosrun ros_erle_takeoff_land ros_erle_takeoff_land
set mode send ok 1 value:
ARM send ok 1
srv_takeoff send ok 0
srv_land send ok 1
Based on the output above, arming is successful but it appears that srv.response.success is returning 0 instead of 1 for the takeoff command.
Currently, I do not have a RC for the drone. I have the propellers off and am simply trying to get a basic ROS example working as a first step.
1.) How do I debug the failed takeoff command on the Raspberry Pi 3 (I'm running the ROS package directly on the device - not from a laptop nor SSH)? Should I use MAVProxy or APM for this? What's the best way to install these on the RP3?
2.) I've noticed that after installing the apm-copter-erlebrain binary, it defaults to booting into CLI mode. This fine but then if I try to boot into GUI mode via raspi-config it causes HDMI out to no longer work. My external monitor connected to the Pi just displays a blank, black screen. When this happens I have no choice but to reflash the SD and start everything over from scratch. This has happened at least three times now. How can I prevent this issue?