Hi @tony-white ,
I installed the BlueOS image on another microSD, and I was able to access to blueos.local through the tether connection. Some strange things happened (e.g. I was able to access to BlueOS when I choose “Obtain an IP adress automatically” on my computer, instead of 192.168.2.1), but now this is back to normal. I still can’t access with the microSD I was using before. Maybe it got corrupted? What are the reasons that can make this happen?
The teather diagnostic is the following. Do you still think this issue is related to the tether or the Fathom-X tether interface module?
I believe the low fall of Mbps of the pink line happend when the computer entered in sleep mode.
Because I installed BlueOS on a new microSD card, I had to reinstall the ArduSub firmware and reload my parameters. I ONLY have a video feed in QGC, but not in Cockpit. I can still control the camera, lights, thrusters… in Cockpit, but there’s no video.
In QGC, I no longer see the dropdown menu I previously used for camera settings—I can’t choose between H264 or RTSP anymore, only the file format mkv, mov, or mp4.
In Cockpit, I’m also seeing additional video devices (?) that I hadn’t seen before (I used to see only my H264 USB camera option: /dev/video2).
Despite having a video feed in QGC, the joystick controls are all messed up. The worst part is the left stick—it’s usually used to move forward, backward, and laterally (left/right), but now it’s controlling the lights and gain. I don’t know how to change the stick functions. At the same time, the directional pad is currently controlling the thrusters, but there’s no modulation.
In the photo I shared in the previous post (when the RPi was booting), there’s a line that says: “IP address is 192.168.1.40”.
Update: I’ve connected the RPi to a monitor, and confirmed that the IP is correct (192.168.2.2), but I’m still confused why the other IP showed up.
.