I had a thruster fail during a run, so we began troubleshooting by replacing the thruster, but nothing changed. We then swapped in a different speed controller and it still did not work. After that we moved the same thruster to another position on the navigator and it worked immediately. That helped narrow it down to a problem with the original port on the navigator.
When we opened the settings we noticed that servo1Function was assigned to RCIN9. Once we corrected it to Motor1 the thruster came back online. I am not sure how that setting changed, but it seems worth mentioning for others since checking that first could save a lot of unnecessary disassembly. I am also curious if there is any known reason for this setting to switch on its own.
RCIN9 is the servo function that used to be assigned to lights outputs, and it’s currently still used in the BlueOS lights setup page (with an auto-migration to the new dedicated function when the autopilot reboots, if there are also lights joystick button functions assigned).
Is it possible someone with access to your vehicle was looking at or tried to do lights configuration, and accidentally assigned the lights as the first motor output?
I’ve recently been thinking a fair amount about how we can provide more comprehensive troubleshooting guidelines, especially with respect to vehicle-related problems. One of the first recommendations when one or more motor outputs isn’t working as expected should indeed be to check the output configuration, as well as the values the autopilot is reporting that it’s outputting on a given pin
Nope - output functions should never automatically change toRCIN9 (although as mentioned, they will occasionally change away from it).
The unit is experiencing intermittent cutouts and reboots. We have performed the following diagnostics:
· Umbilical Cable: Manipulated the entire length, but were unable to induce a failure.
· Thrusters: All appear to be functioning normally. One unit produced an unusual sound, so we reduced its power setting as a test. This did not resolve the issue.
The root cause of the intermittent cutouts remains undetermined.
Darren Horler
Seaveyors Environmental & Marine Services Ltd.
darren.horler@seaveyors.ca
1-250-207-5620
Hi @darren.horler -
Can you perform a network speed test in BlueOS and share the results?
Can you also install the tether diagnostic extension and share a screenshot of the results it has when the ROV is connected to your topside? You can read more about it here.
I am intrigued when you say reboots- do you hear beeps from the thrusters indicating the Raspberry Pi has actually restarted? What is making you think reboots are occurring?
Hi @darren.horler -
If you’re not running BlueOS 1.4.2 (latest stable), you’ll likely find many performance and stability improvements. What version are you using now?
Updating is as easy as connecting your vehicle to WiFi with internet, and going to the BlueOS Version page!
