Hello,
Our BlueROV2 has stopped connecting today. It has been working fine for months and all day this morning. We were doing camera testing with gstreamer on a Linux laptop that I set up today. After we switched back to our main windows laptop that we normally use. It would not connect to Qgroundcontrol or BlueOS. The blue and green lights are on the pi, the 2 green lights on the fathom box are on. I noticed now when we plug in the battery it makes the first chimes, but the other sounds it makes a few seconds later when it connects no longer are there. I was able to ping and get a response from 192.168.2.2. I can no longer get it connected to any laptop. I also tried new cables from the fathom to the computers usb port. Due to the lack of connection sounds made from the BlueROV2 I suspect it to be a problem with the pi itself
Hi @ssicari -
If you are able to ping 192.168.2.2, can you load that address in a web browser?
If you don’t hear the start-up beeps fully complete from the speed controller, this is expected to happen immediately only with pixhawk based systems. Newer systems with the Navigator don’t make this beep until the Raspberry Pi finished starting up, which takes 1-2 minutes typically.
I won’t be able to try to load it in the web browser until Monday. However I let it sit on multiple attempts over 10 minutes and it did not complete the start up beeps. It also was unable to connect to both qgroundcontrol and BlueOS on multiple laptops
When I go to 192.168.2.2 it brings up BlueOS. However there is no heartbeat and there is an error message saying that, “This vehicle is running its factory version of BluePS. This generally means something went wrong, and the system reverted to this version in order to recover. It says to file an issue on the forum and if possible add the system logs. I’m trying to click on the log browser but it will not load. This happened when we were testing the other day on Friday. I was using a Linux laptop that I had just set up to test some gstreamer code and the Linux laptop was having intermittent connection issues all day. I eventually switched back to the windows laptop I normally use and it won’t connect or play the connection beeps. I will also mention the BlueOS side bar shows the raw html and the setup wizard it’s trying to run is hanging, both of those presumably because of the lack of connection from the BlueROV itself. EDIT: Looking into this I do remember an apply bootstrap button appearing for the first time that day but I did not click it or apply it at that time as we were testing. I see an old forum post about a BlueROV reverting back to factory settings because of them not applying the bootstrap. However I can now not even connect to attempt to apply the bootstrap anyways so if that is the problem I still don’t know how I would resolve it.
Hi @ssicari -
It sounds like you’re using an older version of BlueOS - this had a bug that would cause the ROV to revert to a very old factory version on occasion. Please re-flash your SD card with 1.2.6 stable, so this doesn’t happen again! This should restore your connection, and not make applying the bootstrap necessary.
Thanks I’ll give this a try. I recently upgraded BlueOS a few weeks ago but I can’t remember what version I was running. I have an older BlueROV2 that I needed to flash BlueOS onto anyways so I’ll just do it twice
I flashed it and it is connected again. I am having a problem that started last Friday before it reset. In qgroundcontrol roughly every 5 seconds it will flash the waiting for video screen for about 1 second before the stream returns. In BlueOS the preview window for the stream it also disconnects at about the same frequency. I checked that hardware and nothing appears to be loose.
Hi @ssicari -
Are you aware of this technical bulletin? This could be related to your camera issue. Please reach out via the support form, problem with a product, to obtain a replacement if relevant.
I was not aware but I’ll be sure to take a look to see if that applies to us
Hello,
I inspected the resistors and there are very minor markings on the camera mount case. However, compared to the tech bulletin it is not nearly as bad. Furthermore, the transistors themselves seem fine upon visual inspection. We measure their resistance as well with 2 of them reading about the specified 100k and one of them reading 1.3 megaohms which seemed rather high. All in all, the resistors seem to be operating seemingly fine besides that high reading, but we are still having camera problems. Just to add the camera seems to be working fine right now after reassembly, perhaps loosening the screws on the camera to the mount is giving the resistors more room and not pressing them against the mount?
Hi @ssicari -
We strongly recommend trimming the mount! Did you do this before re-installing the camera?
It sounds like the resistors may be ok, but if one of them breaks the camera can enter a wonky state where it’s performance suffers. If either of the other two break, the camera becomes completely non-functional.
If you continue to have camera issues and need a replacement, please contact us via the support form.