Issue Report: Unable to Connect to BlueROV2 Navigator via USB/Ethernet

Blue Robotics Software
1

Background

  • Hardware: BlueROV2 with Navigator board running BlueOS.

  • Connection method: USB tether (interface appears as enx00e04c360208 on host).

  • Hosts tested:

    • Ubuntu laptop (works) → Previously configured, can connect to BlueOS and SSH into Navigator without issues.

    • Jetson Orin Nano (fails) → Tried same setup, cannot reach BlueOS.

    • Ubuntu desktop PC (fails) → Same behavior as Jetson, cannot reach BlueOS.

Observed Behavior

  • On Jetson Orin Nano and Ubuntu desktop:

    • USB interface comes up as 192.168.2.1/24.

    • Attempting to ping 192.168.2.2 or 192.168.2.10 (typical BlueOS defaults) →

      Destination Host Unreachable (from 192.168.2.1)

    • Running arp-scan across 192.168.2.0/24 → no response at all.

    • ifconfig shows RX=0, TX=0 packets on tether interface.

  • On working laptop:

    • Able to connect to Navigator normally.

    • Network settings already established.

    • Confirms BlueOS + Navigator board are functional when accessed from that machine.

Expected Behavior

  • Navigator board running BlueOS should respond on 192.168.2.2 (or assigned IP) when connected to host via USB tether.

  • Host should see ARP responses and be able to ping BlueOS.

Troubleshooting Already Done

  • Confirmed host interfaces get IP 192.168.2.1/24.

  • Disabled Wi‑Fi routing conflicts.

  • Tried multiple IPs (192.168.2.2, 192.168.2.10, .20, etc.).

  • Ran nmap and arp-scan → no device detected.

  • Verified the USB‑Ethernet device (enx00e04c360208) is up and recognized by Linux.

  • Issue is reproducible on two different hosts (Jetson Orin Nano + Ubuntu desktop).

Summary

  • Works: Ubuntu laptop (can ping and SSH into Navigator).

  • Fails: Jetson Orin Nano + Ubuntu desktop (no ping, no ARP replies, RX/TX = 0).

  • Suspect: Either host‑specific driver/USB compatibility issue or BlueOS/Navigator only binding correctly to the original laptop configuration.

Could the team confirm:

  1. If there are known compatibility issues with Jetson Orin Nano or some desktop USB controllers?

  2. Whether BlueOS/Navigator requires special udev/network rules for hosts other than the first configured laptop?

  3. Any recommended steps to reset the Navigator’s network configuration to factory defaults so it can be discovered on new hosts?

2

Hi @Zi-Hao

Sorry for the issue. If I understand correctly, your’e having issues connecting a BlueOS system to your Jetson, but it works ok with an Ubuntu laptop?

Is the green link light on the Fathom-X tether interface at all times? Are you using the same USB cable for each connection to host computer?

If it works on some machines but not others, the likely issue is with the control computer’s network configuration. Typically the static IP of the computer needs to be configured, and is not automatically setup?

3

Hey Tony,

Yes, the attached video shows what happens while connecting the usb ethernet to the laptop and the jetson orin nano. An hour ago, the connection to the laptop still worked, but now it doesn’t. I just can’t figure out how to cope with this kind of unstable connection.

Thanks
Zi-Hao.

(attachments)

connection_issue.zip (3.95 MB)

4

HeyTony,

Yes, I trying to connect the usb ethernet to the laptop and the jetson orin nano. An hour ago, the connection to the laptop still worked, but now it doesn’t. I just can’t figure out how to cope with this kind of unstable connection.

Thanks

Zi-Hao.

5

Hi @Zi-Hao -

Lots of things can cause an intermittent connection - often it is simply a bad USB cable or port!

Since your link light is on, but you’re still having issues, installing the tether diagnostic extension in BlueOS and sharing screenshots of the results it gives may inform what is happening with your Fathom-X tether interfaces. How long is the tether to the vehicle you’re trying to communicate with?

If you’re connecting ethernet directly from the Pi to the laptop or jetson, and still not getting a connection to 192.168.2.1, then a configuration issue with your IP address and subnet mask is likely….