Mission Planner dont' connect with ArduPlane on Navio2

Navio / Edge Hardware
2

Yes, the message about Raspberry Pi 2 is normal.

Regarding the telemetry connection, you have a few things confused.

EDIT: I just had a closer look at your picture. Since you have no network connection to your RPi, you should use this as your startup command:

sudo ArduPlane -C /dev/ttyAMA0

Your problem is, you are starting APM with UDP network telemetry and then you try to connect through your 915MHz serial telemetry kit. If 192.168.1.93 is the IP of your GCS PC, then you should simply select UDP in Missionplanner and enter 14550 as the listening port (should be default).
Lengthy explanation below. :slight_smile:

There are two possible telemetry connection types in general:

  1. Serial: This can be a direct cable connection or any kind of serial RF link. Your 915MHz telemetry kit is a serial link.

  2. Network: This can be anything, that uses tcp or udp packets. Ethernet cable, wifi, 3G, 4G etc.

You can specify two telemetry options with APM startup:

  1. The -A option is usually used for network connections, because it is set to 115200baud in APM by default. Baudrates and all other settings are set through the serial_0 options in APM.
    You can use it with UDP, like you did in your startup command. UDP has less overhead and lag, but you need to know the IP of the GCS computer. If you change networks or want to use different GCS computers, an automated startup with UDP can be cumbersome.
    TCP is client/server based and you can start APM with -A tcp:0.0.0.0:6000 and it will listen on any device, any IP, port 6000 for an incoming connection.

  2. The -C option is used for serial telemetry connections, because it is set to 57600baud by default and 3dr radios for example are set to 57600baud, too. Baudrate etc. is set through serial_1 in APM.

2 Likes