Waiting For Video Connection

Tony, see pictures below for what versions of ROV software and QControl I am running. Am I running compatible versions or does one or more need to be updated?

You mentioned about Windows interfaces - I don’t have a mismatch between windows interface. It appears like that because I’m running a laptop touch screen and I have an attached monitor thats is not touch screen. That is why some photos appear differently as I would’ve taken pics from both however it’s all running through the one laptop.
Also I did a network test - see last pic. Is that showing upload and download of info (packets) to and from sub? If so, then it seemed to be OK?

Hi @ROVoz

If you unplug the USB cable going to the FXTI, the interface “Ethernet 2” should disappear. Is this the case?

The problem is clear here:

Because the link light is not present on the ROv Fathom-X tether adapter, which converts 2 wires in the tether to an ethernet connection, is not functioning. This could be due to damage to that board, such as corrosion, or damage to your tether. You can check the tether is connected correctly by verifying low resistance from end to end with a multimeter:

While you are using the very old Companion OS instead of BlueOS, that isn’t the cause for your issues! If you’re satisfied with the performance (when things are connected and working) there is no reason to upgrade.
Were you able to load that companion interface in your web browser currently? That would suggest that communications through the tether are ok… can you perform a network speed test (top left) if that’s the case?
The Blue Robotics technical reference recommends QGround Control 4.2.8, which is an old version that will prompt you to update on every launch, however it is much newer than the version 3.2.4 you’re using!

The pixhawk in your vehicle is running ArduSub 3.5.4 - this is also very old, but if it works for you, please continue using. As they say, if it ain’t broke don’t fix it…

I would be concerned that the potted penetrators will not make your vehicle reliably water-tight. Blue Robotics recommends replacing all potted penetrators, as they are known to leak. Due to the many leak reports, a much more robust option, the WLP. The WetLink Penetrator can be installed in seconds without adhesives, potting compounds, or rubber molding.

To replace the thruster potted penetrators, either of the following methods can be employed:

  1. Disassemble the thrusters, replace the thruster core, and reassemble them with the same components.

  2. The cable length on some thrusters installed on the ROV is too short to cut the potted penetrator off and install a WLP. As this forum post shows, some users applied heat to remove them and avoid losing cable length. Once the potted penetrators are removed, you can replace them with WLP-M10-6.5MM-HC for 18 AWG cables.

It’s also imperative to replace the potted power cables. Similarly, there are two options:

  1. You can upgrade to the dual power cables with preinstalled WLPs. You’ll need an extra hole on both end caps and a new Power Sense Module, or you can terminate your current PSM with 5.5mm bullet connectors to fit the dual cables.
  2. You can purchase the high-power cable by the meter, compatible with WLP-M10-8.5MM-LC. You must terminate the cable with 3.5mm male/female bullet connectors for your ROV’s current power setup.

Before doing all that, I would recommend you get a connection to the vehicle. If you get link lights on both the FXTI and the BlueROV2 Fathom-X, and things still don’t work, your hardware may be damaged. You can upgrade the electronics with Navigator Retrofit Guide. In addition to the parts listed in the guides, you will also need a 5V 6A Power Supply.

Hi Tony, before I dig deeper can you please confirm the link light your asking about is the one I’ve just taken a picture of is working??


Is this what you mean?? - see pic below

Hi @ROVoz -
Yes, that’s good news - the link light is on, and you have normal bandwidth through your tether.
The issue is the autopilot isn’t communicating with the system it would seem, although the blinking blue light on the pixhawk shows it seems to be working. Weird! Those old pixhawks can sometimes just die…
Can you give the newer, 4.2.8 version of QGround Control that I linked a try?

Please also share a screenshot of the webpage 192.168.2.2:2770/mavproxy

The next step may be opening the ROV and connecting a micro-usb cable from the Pihxawk to your laptop, and seeing if QGroundControl will allow you to communicate with it directly. It may need to be replaced if it doesn’t connect or take an update…

Thanks Tony, I’ll try that in a few hours.

I have all the same issues BUT, as stated earlier, have both leds on the Fathom X box on.
Tony did not answer my previous question…is the blue led on top in the electronics enclosure supposed to be blinking?
I’m running QGC 4.2.8. I have WLPs on all the connections. Triple checking and the IP addresses are entered correct.

Now what?

Yes is the initial answer, am un-installing and reinstalling QGround and see what happens

Hi @bajaMike -
The Blue LED blinking is normal, yes, and indicates ArduSub is running on the Pixhawk (or Navigator in your case.)
Mike, your ROV is likely newer and so is running BlueOS - can you access 192.168.2.2 in the Chrome web browser? If not, review these network setup instructions for R4 systems. You should also be able to reach your Sonoptix sonar at the default IP address if your network connection is properly configured. Make sure you are setting up the entry in “classic” control panel in Windows, and for the interface that appears when you plug your FXTI in.

Ok will go over all of that again but suspect something different. My ROV was all set and running good weeks ago, and now Not Connected. Yes, running BlueOS. I type 192.168.2.2 into my Chrome browser and no connection. I also ping it and it timed out.
Really at a loss here and suspect something different. I reviewed AGAIN, the adapter settings, and it is set correctly.

Hi @bajaMike -
If you can’t ping or reach BlueOS, and the Fathom-X is connected, the network settings are the only thing that I’ve encountered that can prevent connection, given everything else seems to be working. It does take a couple minutes for the ROV to start up of course, but after that it should be accessible!

I went into my network settings and the Realtec controller has a red X on it! So it’s not functioning? I had not noticed that before.

@bajaMike
As the posted link details, as well as @ROVoz 's screenshot, the red x is not your friend! It needs to be configured.

WOW, don’t know how it lost its config, so I opened it up, selected the Configure tab, and it shows several tabs at top. But it does say “the device is working properly” so now what are the config settings?

Come on now Tony, I did all that!! Many times. What else? Nothing says what to do if a red X appears. Make a new connection from scratch? I have tried to enable that Realtec connection but nothing works.

Oh well updating QGround didn’t work so now I’m stumped. Ok you win, can you list whats needed to upgrade to the BlueOS please.

@bajaMike -
Configure the adapter that appears when you plug your FXTI into your computer. This is the interface that is used to connect the ROV. An interface with a red x may be another network adapter on your computer. If no network port shows up, you may have a faulty USB cable that is only providing power. Please share screenshots of your configured interface if the issue persists, you haven’t provided much to go on!

@ROVoz -
We’ve proven upgrading isn’t strictly necessary since you can reach Companion OS - the issue is likely your pixhawk. You can connect it directly to your computer and update its firmware.

Otherwise, a complete guide to updating can be found here.

I have given you what I see. I notice that the Link Active led on the FXTI blue box goes in and out. I’m certain it is not the USB cable and same one I used last time and new. So when I connect/disconnect the USB from the FXTI to the computer I hear audible sounds of connection wouldn’t the X appear/disappear if the connection is made? I now suspect the FXTI box to be defective.

Note: I opened up the FXTI box and guess what I see? 3 of the 4 paired wires are disconnected! Well gee, how about that.So now maybe Tony can tell me where they go back onto the little board?

Too much focus on settings and not enough on a different component. Thanks.

Hi @Mike
As stated earlier, none of those extra wires need to be connected - only a single twisted pair of the tether is used. This is also visible in the picture shared - the green/white pair connection there is going to an accessory connector - as the extra 6 wires are intended for user applications. Additionally, the polarity of this connection (+ to + or + to - does not matter) - just a consistent low resistance for each tether wire - the value in ohm/m is in the technical details - 0.127 Ω/m.

However, as the link light is not staying lit, this is the source of your connection issue. You should follow my earlier advice and check hat your tether connection has a low resistance from end to end, Fathom-X to Fathom-X terminal.

This is the first mention of the Link light going out - if it ever is not lit, the connection is not going to happen!

The X will stay present until ethernet communication is happening across the link - but the connection/disconnection noise is a good sign that windows is correctly recognizing the device. You have not shared any screenshots of the name of the device you’re setting up, but I would assume it matches the USB to ethernet adapter shown in the documentation.