Hmmm…interesting. I assume it doesn’t do that when the pixhawk isn’t
connected?
For the dev board the easiest way to connect to it is via an FTDI cable.
I’m pretty certain this one is what I used:
The end connector is
https://www.digikey.com/product-detail/en/jst-sales-america-inc/GHR-06V-S/455-1596-ND/807818
And you can get pre-crimped wires
https://www.digikey.com/product-detail/en/jst-sales-america-inc/AGHGH28K305/455-3074-ND/6009450
Just cut the FTDI cable to whatever length you want and then solder the
pre-crimped wires onto ends of the FTDI cable wires. I think this is best
since you don’t have to get the expensive crimping tool.
The pixkawk 2.1 cable pinout is here
FTDI cable datasheet:
Connections are:
Red wire - do not connect
Yellow wire - telem 2 pin 2 (FTDI RX to pixhawk TX)
Orange wire - telem 2 pin 3 (FTDI TX to pixhawk RX)
Green wire - telem 2 pin 4 (FTDI RTS to pixhawk CTS)
Brown wire - telem 2 pin 5 (FTDI CTS to pixhawk RTS)
Black wire - telem 2 pin 6 (FTDI Gnd to pixhawk Gnd)
You only really need the tx and rx connections, but the others can be made
just cause they’re easy and no reason not to.
It shows up on the tx2 as /dev/ttyUSB0. I configure the pixkawk with a baud
of 921600 which has been pretty reliable.
Thanks,
Jason