Communicating with Raspberry Pi via MAVLink using MavProxy

I’m currently trying to establish MAVLink communication between a Raspberry Pi 4B (running Raspberry Pi OS) and a Pixhawk 2.4.8 using MAVProxy, but I’ve run into issues. Here’s a detailed breakdown of my setup and problems:

Setup:

1. Raspberry Pi 4 running Raspberry Pi OS.
2. Installed MAVProxy in a Python virtual environment

python3 -m venv ~/mavproxy_env1
source ~/mavproxy_env1/bin/activate
pip install mavproxy

1. Connected the Pixhawk to the Raspberry Pi UART(TELEM2) (serial port /dev/serial0) and disabled the login shell via raspi-config.
2. Configured the Pixhawk using Mission Planner:

• SERIAL2_PROTOCOL = 2
• SERIAL2_BAUD = 921
• Confirmed that /dev/serial0 is present on the Raspberry Pi and connected correctly to the Pixhawk.

ISSUE Link 1 Down" in MAVProxy:

When I successfully start MAVProxy (without sudo), I see the following output:

(mavproxy_env1) aryan@raspberrypi:~/mavproxy_env1 $ mavproxy.py --master=/dev/serial0 --baudrate 921600
Connect /dev/serial0 source_system=255
Log Directory:
Telemetry log: mav.tlog
Waiting for heartbeat from /dev/serial0
MAV> link 1 down

It keeps repeating link 1 down, indicating that no heartbeat is being received from the Pixhawk. ### What could be causing the “link 1 down” issue, and how can I debug it further?

2 posts - 2 participants

Read full topic