APSync Help - Web Server not showing Mavlink data- Rsapberry Pi 3 B+

Hi Everyone,

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.

Is there something I need to do to get the web server to request mavlink data from the AP, or should it do this automatically on startup?

Thanks in advance for your help,

Luke

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.

Which web browser are you using?

Thanks for the reply @peterbarker,

No luck with “mavproxy.py --master :14550”. It just hangs on “Waiting for heartbeat from :14550”.

I have tried using both Google Chrome and Internet Explorer.

Thanks,
Luke

I’m assuming you ran that on a fresh reboot?

Please paste the output of “screen -list”

Yes, it was on a fresh reboot.

Also on a fresh reboot:

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.

OK, that’s way too few processes :slight_smile:

In particular, neither cmavnode nor mavlink-router are running, which is
bad.

Check the screen log files in ~/start_cmavnode and ~/start_mavlink-router

  • one of them should have a screen log indicating why it didn’t start (or
    stopped!) running.

There doesn’t seem to be any log files in the ~/start_cmavnode directory:

apsync@apsync:~ $ cd start_cmavnode/
apsync@apsync:~/start_cmavnode $ ls
autostart_cmavnode.sh cmavnode cmavnode.conf log.conf start_cmavnode.sh

There also doesn’t appear to be a ~/start_mavlink-router directory.

apsync@apsync:~ $ ls
dflogger mav.tlog MyCopter start_apweb start_cmavnode
GitHub mav.tlog.raw start_apstreamline start_cherrypy start_mavproxy

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.

I also have the same issue. Any update?