I was working on my BR2 today, it opened in Cockpit, then I lost all coms/video stream , (and Blue OS not able to connect). I tried two other tethers and spare computers, but all same result , then tried my spare BR2 and that connected without a problem , so not a tether or computer issue.
When I connect the battery, it make the normal start sound, and the internal lights come on ,(I bought a new electronic enclosure 7 months ago)
Any ideas what I should try ?
What about reflashing the onboard micro card ? if that may be a solution , what download link should I use to reflash with BalenaEtcher ?
It’s always worth pulling the housing off and connecting an Ethernet cable from the Pi directly to your computer. If it works, you’re problem is the tether/slipring/Fathom board/box, etc. If it’s still not talking, we find corrupted or loose SD flash card is the most common fault, so maybe flash another card and try again (we have seen cards die completely a few times).
thanks , do you mean to disconnect the lan cable from the navigator board and then connect a lan cable from the navigator board straight to my laptop and disconnect the Fathom USB cable ?
If yes I tried that and replaced the SD card , but still no activity ,
I have never seen this type of issue before (all lights on the Navigator are all flashing as I think normal )
Hi @Mac1 -
Do you know what version of BlueOS you were using?
When you say all lights are flashing normally, can you better explain what you observe? You should have a flashing blue light on the navigator, and a small (occasionally) flashing green light next to a solid red light on the Raspberry Pi underneath it.
If you’ve previously connected the vehicle to a local WiFi network, you may be able to find it’s IP address on the network and access it via that address - if so, double check that you have a static IP address assigned (via the network icon in the upper right, showing two computer terminals linked.)
Yes, that’s the idea. You go from the Raspberry Pi directly to the laptop. with an 8 wire Ethernet cable with RJ45 connectors (standard Ethernet cable in a LAN). But of course you must remember to change the laptop’s Ethernet adaptor settings, but first changing the IP address assigned to the FathomX topside box and then change the IPv4 settings on the physical Ethernet port on the laptop to the correct IP address. You could also open the Fathom X and plug in directly to the Ethernet to USB converter as well.
And Tony’s comment is another great place to look (and dead easy): change update software on both system BlueOS and Cockpit/QGroundControl.
please see pictures of the navigator lights and the PI , also the other side electronic board ( I have disconnected the upper sonar electronic board, until I can resolve my issue ).
Hi @Mac1 - Do you not have any blinking lights on the ethernet switch indicating traffic? The ethernet switch could be having problems, tough to tell from the picture.
The suggestion of plugging an ethernet cable straight from computer to Raspberry Pi is a good one, as it shows the issue is likely in networoking hardware if it works fine.
Sometimes when I connect cockpit I am able to connect through wifi , but does not last for long and have problems reconnecting. (What is the BlueOS network passkey?)
I have also tried connecting the Fathom x directly to the rasberry PI Or is that board called something else? (blue, blue/white tether connection terminals) but still no connection in my laptop.
Excuse me, as I do not know my way around computer and electronic boards
I somehow managed to get things back working , re flashed the SD card again and played about with video sources.
I have a couple of things now needing sorting
camera tilt is not working on the BR camera , all settings are still correct in the joystick settings , buttons show #4 and #4 mount tilt up/down, but no movement
pilot gain going up/down in 25% increments; I normally like them set at 10% increments. Where do I find this alteration setting ?
If your camera tilt servo is connected to the default channel 16, then in BlueOS on the vehicle setup page , PWM outputs, you should see that function next to channel 16. Please share a screenshot.
Simply edit the JS_Gain_Steps parameter in BlueOS under Autopilot Parameters.
Note that since you re-flashed your SD card, you will need to recalibrate your motion sensors. If you save your autopilot parameters after doing so, you can avoid this in the future by uploading them after a fresh install!
How do you re calibrate the sensors , and then save them for future
Also i have downloaded ping viewer into BlueOS, I now have ping sonar device and ping viewer next , which one should be active and how do I create a widget in Cockpit for it ?
when I click on ping viewer next in BlueOS, it opens an independent tab and ping viewer opens and is active in the tab, so its working ok in BlueOS, just to have it active in cockpit.
(if I get the ping viewer widget active in cockpit will it save/show the data in the telemetry, video playback ?)
PingViewer Next has a widget that should come up when you go to edit interface in Cockpit - it is not a mini widget, but alongside things like video widget and iframe. Make sure you’re running BlueOS 1.4.3!
If you’re using PingViewer Next with the BlueBoat, I don’t believe it will record anything in your video subtitle file. You can configure a generic indicator widget to display the rangefinder measurement, and then choose to display it in your subtitle telemetry file, to get that data into any recorded videos.
Hi @Mac1 -
Without knowing what the issue your encountering is, I’m not sure how we can help you! Please share, or reach out to the support team via the help center.
its a software problem , I have been dealing with Rafael, but he is not available , is anyone available over the weekend ?
my issue is video streaming in cockpit, with Rafael we thought the issue was that the CPU was maxing out , but not I have a new pc which should be all ok (as advised by Rafael) but on switching it on I cannot connect to cockpit , no video stream, I have connected about 6 pcs these last few weeks , but not able to connect this one , I am using i92.168.2.1 and 255.255.255.0 but nothing
Hi @Mac1
The IP address of the vehicle is 192.168.2.2, .2.1 is what your computer IP is configured to. That change should resolve your issue!
Generally, Blue Robotics is not available on we weekends- we sometimes respond on the forums in that time on an entirely voluntary basis- not to be expected!
Hi @Mac1 -
You seem to have things misconfigured. Please review the setup instructions - the ROV is at 192.168.2.2, and your computer should be at 192.168.2.1 (technically when using Cockpit, the last digit doesn’t matter!)
When your computer has the same address as the ROV, things just aren’t gonna work!
