Open GoogleCodeExporter opened 9 years ago
TCP datagrams are not supported. If you remove that packaging and send it
directly TCP it will work. You can test with my GPS emulator by selecting TCP
in both the GCS and emulator and enterint localhost:30300 in both. You'll need
to hit connect on the GCS first and then connect on the emulator.
I don't know what the benefit of a datagram is...and you're the only person who
has asked for it thus far. Others have asked for more in the way of TCP and UDP
(UDP is one way communication from auto pilot to GCS currently). TCP is 2-way.
Original comment by paulbmather@gmail.com
on 30 May 2011 at 9:43
What is the difference between TCP datagram and normal TCP ??
I will check again, but i was not able to use TCP neither, this was to link to
the serial port through an IP radio link and netcat similar solution.
Original comment by olivier....@helidream.fr
on 1 Jun 2011 at 11:34
A TCP datagram has a wrapper to be used across the internet. It includes a
sender, a receiver, timestamp and data packet. I currently do not parse out
this data...I'm just looking for the data packet, nothing else.
Original comment by paulbmather@gmail.com
on 5 Jun 2011 at 7:13
A tcp packet by definition has those. that is how it gets from it source socket
to the dst socket and back.
they are not included in the payload that you get as data so you do not need to
parse them.
Original comment by borna.em...@gmail.com
on 5 Jun 2011 at 7:35
Then I don't know what the issue is. I can send the raw data from my emulator
to the GCS without issue....now I haven't tried MAVlink....so who knows, maybe
there's something in the binary it doesn't like.
Original comment by paulbmather@gmail.com
on 5 Jun 2011 at 7:46
[deleted comment]
Please support TCP. I want to use SITL (software in the loop) drone simulator
for a large project and it never connect:(
Original comment by ad...@serveurperso.com
on 8 Jul 2015 at 7:10
Original issue reported on code.google.com by
borna.em...@gmail.com
on 30 May 2011 at 9:13