"Failed to fetch available firmware" error in BlueOS

[eri3t (Eric Ruiz)]

Hi @tony-white ,

@tony-white

This may be due to having QGC open at the same time? Or needing to adjust your Cockpit video configuration to show the correct stream

It was a Cockpit video configuration issue, thanks for the info . I’m using UDP over RTSP because for the moment I use QGC, and I’m afraid of doing extra changes before having everything working properly. What does using RTSP reflect on? Does it make a huge difference? I need the ROV to work consistently for coral surveys in southern Spain, and I’m facing new problems constantly.

@tony-white

Have you tried restarting the vehicle and loading the parameters? The battery capacity error you see in QGC is due to the parameter not having the correct value (0.)

Yes, the day after encountering that problem it stopped (I guess because it completed to write the parameters).

Yesterday we tested the ROV in a reservoir. Everything was working except for the light commands on the joystick (lights didn’t turn on, and pressing those buttons resulted in the movement of the newton subsea gripper, even though that was not their funtion, as it’s shown below).

Buttons 14 and 15 control light behaviour (and their “shift” function doesn’t relate to newton gripper movement).

Yesterday, after the first deployement, I disconnected the batteries. For the second immersion of the day, camera tilt buttons stopped working, while I didn’t change any setting; this happened just after reconnecting the battery and opening QGC/Cockpit. I then decided to reset all parameters (see below), which only made the situation worse (thrusters stopped working properly). I loaded the recommended Parameter Sets for the heavy configuration, and it froze the ROV (lights turned on permanently, no possible control over the ROV).

Is there a relation between joystick correct functioning and these Parameters loads? It had never caused a problem before the Ardusub firmware update. Now I have camera tilt buttons functioning again, but light controls won’t work. Is there something wrong with my configuration? I’ve tried Servo 10 but nothing changed.

@tony-white

Is the WaterLink UGPS extension installed? Have you been able to reach the web interface of that system per the documentation, or followed those instructions yet?

Yes I have installed the WL UGPS extension. I couldn’t try the UGPS yesterday, but on other occassions I could see my position in Watherlinked’s GUI, but not in QGC or Cockpit. I have a bridge connection (as the documentation says for locator U1), and I’ve followed every step carefully. Nevertheless, next time I want to do some tests, as on all other occasions Ardusub firmware wasn’t updated (although not sure if it’s related).

@tony-white

how is the Ping sonar connected? Have you enabled it under ping sonar devices?

The connection is through a USB to serial adapter, and a green light lights up as I documented here. Yesterday the ping sonar appeared in Pingviewer and worked perfectly, but I didn’t change any setting (I’m worried about reliability, because for the moment I don’t know when something is going or not going to work).

@tony-white

The BR-ROV deepvision sidescan is not hardware I’m familiar with, and it doesn’t seem to be available for purchase anymore. From what limited documentation I can find, it seems they need to connect to power and an ethernet switch, and you access the data via a web interface?

Yes, it’s connected through ethernet switch, and visualization is through DeepView software. I contacted DeepVision, and they told me the steps to activate the sonar for the first time, which I leave here for whom it may concern, since there’s no indication in their documentation:

1. After installation of BR-ROV deepvision sidescan and downloading the DeepView software, you should activate the DSSP file that comes with your purchase (Settings>Sonnar Setup File> Open DSSP_BR_ROV). You can make sure the sonar is properly connected pinging it at 192.168.2.62
2. The fist time after installation you should select a range (if not, no image will ever show up). This is done clicking the icon right of rec/play button in DeepView software (recording properties>sonar setup>select range)
3. Apparently there is some windows issue if you have your wifi turned on. I turned it off and the software immediatelly started to work. Here I leave the first (and improvable) test we did:

Sorry for the long reply.