I have this problem communicating with my raspberry pi and pixhawk.
with this error
“pi@raspberrypi:~ $ mavproxy.py --master=/dev/ttyAMA0 --baudrate 921600 --aircraft MyCopter
Connect /dev/ttyAMA0 source_system=255
no script MyCopter/mavinit.scr
Log Directory: MyCopter/logs/2021-08-02/flight10
Telemetry log: MyCopter/logs/2021-08-02/flight10/flight.tlog
Waiting for heartbeat from /dev/ttyAMA0”
i also enable, “enable_uart=1” and disable “dtoverlay=dsibale-bt” in my “sudo nano /boot/config.txt”
i thought im full set but it didnt work to communicate sad.
so manage to execute this “mavproxy.py” command line and i notice my /dev/tty" is ttyS0 whenever i execute it i also got the same error message before.
yes, I follow this instruction but still haven’t fix yet. my baud rate “921600” so whenever i enter the higher baud rate it wouldn’t connect so i will go on lower baud rate let me test it later i hope it works.
I’m sorry it is not working for you. Perhaps another reader can contribute. Another resource to consider is https://dojofordrones.com/. Caleb walks you through the entire hardware and software builds for the RPi to Pixhawk configuration.
“…but i switch the rx to tx and it work but ive noticed whenever i switch flight mode it wont change…”
This indicates you had the wiring crossed, so keep it that way. The fact it is not switching modes is a software issue. I would suggest starting over and reinstalling the software, checking your Mission Planner settings. I have done this often in the past and it helped because I missed a dependency or such.
I suggest you start easy = use a FTDI usb to serial adaptor and do a terminal to terminal test between RPI and a PC then , once the communication link is proven working it will be much easier to work on Mavlink