I've recently been refining a technique for capturing MAVLINK packets via Wireshark and I could really use a virtual COM port in order to properly connect. This would work perfectly, except the Mission Planner will not list or recognize anything under /dev/pts (yes, I'm using Linux), which is where the virtual ports are. Does anyone know a good workaround? I'm using socat to create/link the ports and a simple C program to read, split, pipe, and rewrite the data I'm getting.
Thanks for any help!
EDIT: So I got a hold of the Mission Planner source code and changed it so that it recognizes devices from /dev/pts/. Still the same problem, as if it thinks that there is no port there at all. Is there some setting that I need to check/change right off the bat when I create the virtual port in order for programs to recognize it?
Tags:
Permalink Reply by Tommy Larsen on July 24, 2012 at 2:08pm Maybe you find something here : http://com0com.sourceforge.net/
Permalink Reply by Paul Hoi on July 25, 2012 at 9:27am I'm currently using socat (since it's made for Linux), which is very similar to com0com. I'm afraid I would run into the exact same problem with com0com, though--the fact that the Mission Planner won't recognize the virtual serial port that's created. I guess I'll look into it, though.
on linux cant you just ln to a new name? i thought you could
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.1355 members
207 members
24 members
52 members
719 members
© 2013 Created by Chris Anderson.
Powered by
