I have APSync (apsync-rpi-20180918172614.img) installed on a Raspberry Pi 3 B+. I am able to speak to the connected Pixhawk 1 by using the “mavproxy.py --master=/dev/ttyAMA0 --baudrate 921600 --aircraft MyCopter” command line through SSH.
However, I am not able to see any of the mavlink data on the 10.0.1.128 webpage.
I have APSync (apsync-rpi-20180918172614.img) installed on a Raspberry Pi 3 B+. I am able to speak to the connected Pixhawk 1 by using the “mavproxy.py
–master=/dev/ttyAMA0 --baudrate 921600 --aircraft MyCopter” command line through SSH.
That’s probably not a good sign; something else should be connected to the
serial port!
Try “mavproxy.py --master :14550” instead.
However, I am not able to see any of the mavlink data on the 10.0.1.128 webpage.
apsync@apsync:~ $ screen -list
There are screens on:
513.cherrypy (19/12/18 05:32:50) (Detached)
496.DataFlashLogger (19/12/18 05:32:50) (Detached)
2 Sockets in /run/screen/S-apsync.
I am using a beta image of APSync, as the stable image did not boot the “ardupilot” wifi hotspot on the Raspberry Pi 3 B+. Could this be causing the issue. Is there a recommended image for the B+?
Did you ever get this figured out? I am assuming it is related to the beta image as I am running into the same issues several others including yourself are. Is there a stable image for the 3B+ yet. I appear to have issue after issue I’m having to try to work through with the image. I’ve been half tempted to run out and purchase the original 3B and see if I have any better luck with the official release.