Hi All,
I would like to connect PixHawk to TX2 via USB to transfer a mission with MAVLink.
I can see the usb device with lsusb but the serial port is not visible (port ttyUSB0).
Anyone could help me?
Thanks in advance
Maurizio
Maybe the USB port has another name?
Try this:
- unplug the USB transmitter/receiver
- start, in a command line window, “sudo udevadm monitor”
- plug in the USB transmitter/receiver
The command line will now show you what udev thought about the device. This should include the actual name it gives to the device, if it gets any name.
Monitor dmesg as you plug in the device, it may offer some information on its naming. You can run “dmesg --follow” to see what pops up as you insert or remove the USB connector (you might want to post a copy of the plug in/out dmesg content). And as @snarky mentioned the device name may differ…normally a rename of device special files to a standardized name like “ttyUSB0” only takes place if udev has a rule to do it.
HI maucod:
when i plug the usb to pixhawk the window of udevadm monitor shows:
KERNEL[744.406519] add /devices/3530000.xhci/usb1/1-1 (usb)
KERNEL[744.423793] add /devices/3530000.xhci/usb1/1-1/1-1:1.0 (usb)
KERNEL[744.425064] add /devices/3530000.xhci/usb1/1-1/1-1:1.1 (usb)
UDEV [744.447331] add /devices/3530000.xhci/usb1/1-1 (usb)
UDEV [744.452666] add /devices/3530000.xhci/usb1/1-1/1-1:1.0 (usb)
UDEV [744.463611] add /devices/3530000.xhci/usb1/1-1/1-1:1.1 (usb)
i don’t know which tty* to use
What does dmesg say about tty when you insert the device (this might give more information about the tty or type of USB device, e.g., “dmesg --follow” and insert connector)? Possibly this is nothing more than a bridge and you need a serial USB UART driver (many exist, mostly the FTDI brand bridges are there by default, though not always…and other brands are usually not there by default).
Hi,
I have the same problem as maucod when connecting Pixhawk to Tx2 via usb. udevadm doesn’t show any name like tty* assigned to the device. When I connect Pixhawk to my desktop computer on Linux, udevadm clearly shows ttyACM0.
dmesg provides no information about the tty* assignment, either:
[21841.309128] usb 1-2.1: new full-speed USB device number 18 using xhci-tegra
[21841.415618] usb 1-2.1: language id specifier not provided by device, defaulting to English
[21841.432937] usb 1-2.1: New USB device found, idVendor=26ac, idProduct=0011
[21841.446833] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21841.461537] usb 1-2.1: Product: PX4 BL FMU v2.x
[21841.470744] usb 1-2.1: Manufacturer: 3D Robotics
[21841.480096] usb 1-2.1: SerialNumber: 0
[21841.488312] usb 1-2.1: ep 0x83 - rounding interval to 1024 microframes, ep desc says 2040 microframes
[21841.507744] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
[21845.974883] usb 1-2.1: USB disconnect, device number 18
[21845.986803] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
[21847.709134] usb 1-2.1: new full-speed USB device number 19 using xhci-tegra
[21847.989666] usb 1-2.1: New USB device found, idVendor=26ac, idProduct=0011
[21848.003543] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21848.018431] usb 1-2.1: Product: PX4 FMU v2.x
[21848.027618] usb 1-2.1: Manufacturer: 3D Robotics
[21848.037336] usb 1-2.1: SerialNumber: 0
[21848.045713] usb 1-2.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[21848.063977] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
Do I need to install a driver or smth on TX2?
According to that log the ID of this device is “idVendor=26ac, idProduct=0011”. This means you should be able to refer to a verbose listing via:
sudo lsusb -d 26ac:0011 -vvv
What does this report? It may provide a clue towards driver requirements.
Thanks linuxdev,
my problem is resolved by following the hack in
http://www.jetsonhacks.com/2017/07/31/build-kernel-ttyacm-module-nvidia-jetson-tx2/