USB device not detected

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

i am using nvidia jetson AGX orin developer 64gb with ubuntu 22.04. i am a ROS developer and i want to connect the Xsens 320i imu sensor to one of the usb. it shows in lsusb as prolific technology but port is not created like ttyUSB0 or ACM0. any help on further details description of the problem is required kindly ask me. i need to solve this issue. thank you

2

*** Please note that this reply is generated by LLM automatically ***

To address the issue of connecting the Xsens 320i IMU sensor to the NVIDIA Jetson AGX Orin Developer Kit and having it recognized as a serial device (e.g., /dev/ttyUSB0 or /dev/ttyACM0), let’s break down the steps and considerations:

  1. Understanding the Xsens 320i IMU Sensor Connection:

    • The Xsens 320i IMU sensor is connected via USB, and it’s recognized by the system as a device from Prolific Technology, which suggests it’s using a Prolific USB-to-Serial converter chip.
    • Typically, devices using Prolific chips should be automatically recognized by Linux systems, including those running on the Jetson AGX Orin, and should create a serial device file in /dev.

  2. Troubleshooting Steps:

    • Verify USB Connection: Ensure the sensor is properly connected to the Jetson AGX Orin via a USB port. Try using a different USB port if possible.
    • Check lsusb Output: You’ve mentioned that the device shows up in lsusb as Prolific Technology. This indicates that the device is at least partially recognized by the system.
    • Check dmesg Output: Run dmesg | grep tty or dmesg | grep usb to see if there are any messages related to the USB device or serial port. This can provide clues about whether the system is attempting to create a device file for the sensor.
    • Install Prolific Driver (if necessary): Although Linux usually includes drivers for Prolific chips, ensure that the latest kernel and firmware are installed. You might need to install or update the pl2303 driver, which supports many Prolific devices.
    • Create a Udev Rule (if necessary): If the device is recognized but not creating a serial device file, you might need to create a udev rule to specify how the device should be handled. This involves creating a file under /etc/udev/rules.d/ that specifies the device’s VID and PID (which can be found in the lsusb output) and the desired device name.

  3. ROS Considerations:

    • Once the device is recognized and a serial device file is created (e.g., /dev/ttyUSB0), you can use ROS serial packages like rosserial to communicate with the device.
    • Ensure that the serial port permissions are correctly set so that ROS can access the device. You might need to add the ROS user to the dialout group or use sudo to change the permissions of the serial device file.

  4. Additional Help:

    • For further assistance, providing more details about the lsusb output (including the device’s VID and PID) and any relevant dmesg messages could help in diagnosing the issue.
    • Also, specifying the exact model of the Xsens IMU sensor and any specific instructions you’ve followed so far could provide more context for troubleshooting.

Given the information provided, the next steps would involve checking system logs for any errors related to the device, ensuring the correct drivers are installed, and potentially creating a udev rule to manage the device’s recognition and naming. If you’re still having trouble, providing more details about your setup and the exact steps you’ve taken so far will be crucial for further assistance.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

please check what driver is needed for that device. It could be that default kernel does not enable this driver.