I`m trying to get Mission planner connected to my Pixhawk through RPI using UDP protocol. But somehow it fails. If i`m using APMplanner 2 everything is working and connections is good.
When i hit the connect button in mission planner it`s saying "waiting for connection" and sometimes its starting to count down and sometimes its start`s to receive packages for a couple of seconds, but ends up in "connect failed" error.
I`v been trying several types of UDP server in my RPI with same result.
I tested my old APM 2,5 board instead of Pixhawk, and its work like a charm.
What is the different between APM and Pixhawk telemetry packages.
If i`m using Pixhawk and Mavlink, it sometimes connects successfully 1 out of 10 times maybe, but the latency is very high.
With TCP connection there is no problem at all APM & Pixhawk connects perfectly. Everything running smooth..
TCP tested method`s:
- Ser2net- Working perfect (Tested without TTL to Eth adapter. TX/RX connected directly to RPI)
- Python TCP script - Working perfect (Tested without TTL to Eth adapter. TX/RX connected directly to RPI)
- Socat comand line ( socat UDP4-RECVFROM:14450,fork UDP4-SENDTO:<DynDns>:14450
So my question is:
Why is UDP working in APMplanner 2 and not MP?
Is there something else i need to considerate when using PixHawk UDP and MP
I will try to use Wireshark to see whats happening to my package, but i could really need some advice on what to look for.
Bernt Christian Egeland