Hello

I can't seem to connect to my vehicle via udp/wifi connection. I can connect with both mission planner and qcg with my setup

My setup is as follows

pix2

raspberry pi 3 (handles networking and mav proxy)

quad plane running arduplane 3.7

futaba t8fg super with futaba receiver

I have mavproxy stream the telemetry through the pix2's telem1 port to the uart on the pi. The pi is a dhcp server and i use a separate wifi device at the ground station. I have tried several ways of getting the remote port, and i really think i got it right. I use tcpdump on the pi to get the remote port, and i have also used the gcs's firewall to try and get it. My wifi signal is strong, and data rate is high, and i am able ssh to the pi with the current wifi setup. Fire wall on gcs is set to allow all connections on all modules and ugcs itself (client, server, and all vsm's). 

Here is my config file:

# Initial VSM configuration file.
# Format corresponds to Java-properties text representation -
# http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html

log.file_path = ${UGCS_INSTALLED_LOG_FILE_PATH}
log.single_max_size=10Mb
log.level=debug

#ucs.transport_detector_on_when_diconnected

# File to dump all generated missions to. Timestamp suffix is appended to the
# name. Leave the value empty (or delete the entry) to disable mission dumping.
vehicle.ardupilot.mission_dump_path = ${UGCS_INSTALLED_LOG_DIR}/mission

# Local address for listening connections from UCS.
ucs.local_listening_address = 0.0.0.0

# Local port for listening connections from UCS.
ucs.local_listening_port = 5556

# Uncomment this to disable serial port access arbitration across
# different processes.
#vehicle.ardupilot.serial_port.use_serial_arbiter = no

vehicle.ardupilot.serial_port.exclude.1 = /dev/ttyS.*
# name matching in Windows is case insensitive
vehicle.ardupilot.serial_port.1.name = /dev/ttyUSB[0-9]+|com[0-9]+
# 57600 is default 3DR radio speed
vehicle.ardupilot.serial_port.1.baud.1 = 57600
#
vehicle.ardupilot.serial_port.2.name = /dev/ttyACM[0-9]+|com[0-9]+
# 115200 is default Ardupilot USB serial rate
vehicle.ardupilot.serial_port.2.baud.1 = 115200

# Connect to proxy (e.g. ZigBee proxy)
#vehicle.ardupilot.tcp.1.proxy = 127.0.0.1
#vehicle.ardupilot.tcp.1.port = 5566

# Vehicle can be connected via UDP.
# Three parameters are mandatory and one optional.

# 1. UDP port which will listen for incoming mavlink messages.
vehicle.ardupilot.udp.1.udp_local_port = 14550

# 2. IP address of the vehicle to connect to.
vehicle.ardupilot.udp.1.udp_address = 192.168.42.1

# 2. UDP port of the vehicle to connect to.
vehicle.ardupilot.udp.1.udp_port = 51694

# 4. Local IP address to listen on. (Optional)
# UDP listener will bind on all local addresses unless
# udp_local_address is specified.
# Can be used to bind to only one specific interface.
#vehicle.ardupilot.udp.1.udp_local_address = 192.168.42.11

# Custom vehicles can be defined to override default model name and
# serial number
#vehicle.ardupilot.custom.my_drone.system_id = 2
#vehicle.ardupilot.custom.my_drone.model_name = My model name
#vehicle.ardupilot.custom.my_drone.serial_number = My serial number

# Index of servo to use for camera trigger.
#vehicle.ardupilot.camera_servo_idx = 8
# PWM value to set for camera trigger.
#vehicle.ardupilot.camera_servo_pwm = 1900
# Time to hold camera servo at the specified PWM when triggering single photo in seconds.
#vehicle.ardupilot.camera_servo_time = 1.0

# Service discovery configuration
# (Uncomment next line to enable automatic discovery of this VSM.)
service_discovery.vsm_name = Ardupilot VSM

# By default plane control via joystick is disabled due to safety.
# Uncomment this to enable direct vehicle control for fixed wing frames.
#vehicle.ardupilot.enable_joystick_control_for_fixed_wing = yes

# Uncomment the line below to disable relative altitude reporting
# Should be used it if vehicle uses RTK GPS.
#vehicle.ardupilot.report_relative_altitude = no

#vehicle.ardupilot.detector.1.udp_local_port = 14550
#vehicle.ardupilot.detector.1.udp_address = 192.168.42.1
#vehicle.ardupilot.detector.1.udp_port = 51694

This is my mavproxy command running on /etc/rc.local

(
date
echo $PATH
PATH=$PATH:/bin:/sbin:/usr/bin:/usr/local/bin
export PATH
cd /home/pi
screen -d -m -s /bin/bash mavproxy.py --master=/dev/ttyAMA0 --baudrate 57600 --aircraft MyCopter --out 192.168.42.11:14550
) > /tmp/rc.log 2>&1

Now my mavlink comes through a different connection on my gcs than my internet. I was thinking maybe i needed option 4 in the udp, but that didn't seem to help (ip of gcs mavlink wifi adapter). The adapter ip domain is totally different than my main internet connect and completely separate. I have read the instructions on how to do this like 6 times, and googling doesn't seem to get me much further than the instructions. I tried redownloading the file, tried using my home wifi network to connect, and nothing seems to work. 

I found somewhere about the detector lines at the bottom of the config file, but they didn't do anything

Also like i said, using mission planner or qgc work without a hitch with my wifi setup.

I don't know if there are any logs for ugcs, if there are, that would be helpfull in diagnosing the issue.

Im thinking about maybe running ROS and seeing if i can get ros to fix the remote port,to allow for a seemless connection process(i will be trying this in the very near future.)

Im very interested in using ugcs as it has some killer features. I don't really want to use a TCP connection, as a udp connection is better suited for this purpose. I am a UAV developer and i really want this to work so any help would be great. Ideally i don't want to be dealing with having to open the config file every time. Its not a good end user solution.

Sorry for the long post.