For APSync with cmavnode on Raspberry Pi 3 (stock setup, firmware date 10/5/2017):
I have a Win8 PC with mission planner (v. 1.3.59) connected to the local wifi hotspot (called ardupilot) that is created by the Pi 3.
When I try to connect with Mission Planner, it says there are no heartbeats and fails to connect (timeout after 30 seconds of no heartbeats).
Using Wireshark on my PC to analyze all the traffic, I see that UDP packets (including MAVLink packets that DO contain the heartbeat i.e. message id #0) are getting sent from the Raspberry Pi 3 (IP 10.0.1.128) to my pc (IP 10.0.1.73). However, for some reason I am also getting ICMP error packets saying “Destination unreachable” see below for summary):
Source: 10.0.1.128 Dest: 10.0.1.73 ICMP Destination unreachable (Host unreachable)
Source:10.0.1.73 Dest:10.0.1.128 ICMP Destination unreachable (Port unreachable)
Without rebooting, if I manually kill the cmavnode and instead manually run MAVProxy on the Pi 3 with this command:
sudo -s mavproxy.py --master=/dev/ttyAMA0 --out=udpbcast:10.0.1.255:14550
then I am able to connect to Mission Planner.
Why are the UDP packets from cmavnode not accepted by my Win8 computer (according to Wireshark packet analyzer), which presumably prevents Mission Planner from connecting? Whereas, the UDP packets from MAVProxy ARE accepted by my Win8 computer, which allows me to connect through MAVProxy?