Mavproxy serial works, IP doesn't

#1

I can get mavproxy to connect direct to the serial port:
mavproxy.py --master=/dev/ttyAMA0
Connect /dev/ttyAMA0 source_system=255
Failed to load module: No module named ‘terrain’. Use ‘set moddebug 3’ in the MAVProxy console to enable traceback
Log Directory:
Telemetry log: mav.tlog
Waiting for heartbeat from /dev/ttyAMA0
MAV> online system 1
STABILIZE> Mode STABILIZE

but not via IP address and port:
mavproxy.py --master=127.0.0.1:14550
Connect 127.0.0.1:14550 source_system=255
Failed to load module: No module named ‘terrain’. Use ‘set moddebug 3’ in the MAVProxy console to enable traceback
Log Directory:
Telemetry log: mav.tlog
Waiting for heartbeat from 127.0.0.1:14550
MAV> link 1 down

Did I miss a configuration step to tell the UART what UDP port to be on?
Thanks!
Mark

#2

Hi Mark!

Are you using a Pixhawk RPI drone or a Navio2 RPI drone?

If Pixhawk, you won’t be able to establish a Mavproxy connection via IP, but I do believe you will be able to port forward your serial connection to a different IP address. For example, I believe you could connect the RPI to the Pixhawk via UART, then through the RPI internet connection, port forward the data to your GCS through IP .

#3

Caleb,
I’m using Pixhawk. I’ve discovered the command
mavproxy.py --master=/dev/ttyAMA0 --out 10.0.0.253:14551
works fine. I was just curious about the IP version.
Thanks!
Mark

#4

Glad to hear Mark!

1st @caleberg
Closing topic due to problem resolution

closed #5