Arm_test.py is displaying the following connection error:
My problem (and suggested Drone Dojo solution) is basically the same as the following:
I modified the code using the above suggested solution, but received the subsequent error:
Help is required.
@Caleb, am still waiting for support.
I’m basically at the final steps; everything is downhill from here once I test these scripts out in the field.
It was strictly advised numerous times in these forums that we stick with unsupported Python 2. And so, we obliged. But it’s becoming clear that Python 3 is necessary.
After confirming that the scripts (arm test, takeoff, & SINGLE aruco precision landing) are still working today for you with your current Python 3, Ubuntu 20, etc. builds, can you:
please list here all of the required installs/dependencies including versions of Ardu firmware/dronekit/MAVProxy/pavlink, as well as RPI OS version, ROS version, etc.?
I know this is old, but if you are on a Pi connecting to a Pixhawk via UART, your connection string would be “/dev/ttyAMA0”
/dev/ttyUSB0 could work, but it would require plugging in a USB2 to the Pi, and plugging into the micro USB port of the Pixhawk.
Additionally, our newly renovated drone building course has a pre-configured Pi image you can use to flash to the Pi. Those have hardcoded the python-dronekit scripts to connect to /dev/ttyAMA0
This isn’t a python2 problem, it appears to be a connection string problem
Yeah … UDP never worked for me …
Using /dev/ttyAMA0 & /dev/ttyUSB0 resulted in much less issues for me.
But ultimately, what allowed me to finally get the all important precision landing aruco scripts working, was running non-conflicting dronekit/mavproxy/pymavlink versions, i.e. 2.9.2/1.8.17/2.4.8 using Buster on an RPI 3. There shouldn’t be any problems testing my installations on my RPI 4, but I haven’t yet got around to ascertaining …
