I currently have connected a SpeedyBee F405 V4 flight controller to a Raspberry Pi 4 running APSync over serial (rx/tx 2 on the FC side).
I followed the stps in here: APSync — Dev documentation, then attempted the Maxproxy instructions in here: Communicating with Raspberry Pi via MAVLink — Dev documentation.
I can successfully connect to the ‘ardupilot’ access point that is created at startup, I can successfully see FC info through http://10.0.1.128 (e.g. I can see accel / gyro graphs). Then I try to run mavproxy. The result is slightly different every time, but generally the connection keeps alternating between no link / link 1 down and link 1 OK, and generally while it seems to display the correct mode (STABILIZE in this case), it usually does not properly access parameters (I can always see them in GCS). Additionally there is a lot of garbage printed to the screen if I do not use the set shownoise false command. I’ve checked my serial connections, and everything looks okay. Any thoughts on why this might be happening would be greatly appreciated.
pi@apsync:~ $ mavproxy.py --master=/dev/serial0 --baudrate 921600 --aircraft MyCopter --cmd="set shownoise false"
/home/pi/.local/bin/mavproxy.py:21: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
from imp import reload
Connect /dev/serial0 source_system=255
no script MyCopter/mavinit.scr
Log Directory: MyCopter/logs/2024-11-06/flight13
Telemetry log: MyCopter/logs/2024-11-06/flight13/flight.tlog
Waiting for heartbeat from /dev/serial0
MAV> APM: Frame: QUAD/X
online system 1
STABILIZE> Mode STABILIZE
no link
link 1 down
no link
no link
link 1 OK
fence present
no link
link 1 down
no link
no link
link 1 OK
no link
link 1 down
link 1 OK
no link
link 1 down
link 1 OK
STABILIZE> param show ARMING_CHECK
STABILIZE> no link
link 1 down
no link
link 1 OK
no link
link 1 down
link 1 OK
STABILIZE> no link