Right, I've played with MAVlink before and as said it is not a wireless
standard, you can send it over hard link serial if you want. I'm assuming
your are sending the MAVlink over a pair of serial-RF adapters as is usual.
http://copter.ardupilot.com/wiki/common-using-the-3dr-radio-for-telemetry-wi
Hey everyone,
I've mentioned a few times recently the FEC API. It'll be part of the 3.7.4
release (expected later next week), but I just wanted to point out a new
post I wrote:
http://www.trondeau.com/home/2014/6/24/update-and-374.html
Just a few updates on new features and what's been going on.
On Fri, Jun 27, 2014 at 11:24 PM, Hoang Ngo Khac
wrote:
> Thank you Tom.
> I've modified the Decode CCSDS 27. In particular, I changed the code in
> implementation file (.cc):
>
> Existing code:
>
>> const float *in = (const float *)input_items[0];
>> unsigned char *out = (unsigned char *)o
Hey,
I have the feeling that there maybe a misunderstanding about what
MAVlink really is. The MAVlink protocol as such is serialization library
that is used to transfer information, i.e. serialized data structures,
between mobile and stationary devices rather than a whole "communication
system". Y
Follow the instructions in section "Setup Udev for USB (Linux)" at the
following URL for you to be able to access your USRP1 with non-root
permissions:
http://files.ettus.com/uhd_docs/manual/html/transport.html#setup-udev-for-usb-linux
An easy way to locate the 'uhd-usrp.rules' file is to run the
