Using a different GCS instead of MAVProxy via UDP on a different machine

Hi everyone,

I am following the ArduPilot documentation at Using SITL — Dev documentation for using a different GCS instead of MAVProxy via UDP. My other GCS (QGC) is running on a different machine. I’ve been able to use UDP packet forwarding with MAVProxy to connect on QGC on the second machine, but when I try to use QGC as the only GCS via a UDP/UDPclient connection via the following command:

cd ardupilot/ArduCopter
sim_vehicle.py --no-mavproxy -A “–serial0=udpclient:14550”

I get a separate XTerm pop up terminal that says:

Setting SIM_SPEEDUP=1.000000
Suggested EK3_DRAG_BCOEF_* = 16.288, EK3_DRAG_MCOEF = 0.209
Starting sketch ‘ArduCopter’
Starting SITL input
Using Irlock at port : 9005
PANIC: Invalid device path: udpclient:14550
Running: sh …/Tools/scripts/dumpstack.sh 817637 >dumpstack.sh_arducopter.817637.out 2>&1
dumpstack.sh has been run. Output was:
-------------- begin dumpstack.sh output ----------------
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
/tmp/gdb.817639:2: Error in sourced command file:
No stack.
-------------- end dumpstack.sh output ----------------
Running: sh …/Tools/scripts/dumpcore.sh 817637 >dumpcore.sh_arducopter.817637.out 2>&1
dumpcore.sh has been run. Output was:
-------------- begin dumpcore.sh output ----------------
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
/tmp/gdb.817645:2: Error in sourced command file:
You can’t do that without a process to debug.
-------------- end dumpcore.sh output ----------------

I have the ip address of the machine running QGC for . Any help in resolving this would be much appreciated

Turns out it was just a missing colon. This ardupilot documentation is missing the colon in “-serial0=udpclientcolon:14550”