Hi @eri3t -
I think everything was working the first time, at least as far as your autopilot goes! That “need to format” message happens post flashing an SD card, as Windows won’t recognize the linux filesystem that was created.
I’d assume your system is using a pixhawk and a pi3?
Have you connected BlueOS to WiFi with internet, via the icon in the upper right?
There are no scripts for sub, but you will need to load the default parameters for your vehicle type. This is failing, as is updating the ArduSub firmware on the pixhawk, because of the limited system resources of this old hardware.
To correct, try navigating to the Video Streams page and removing the video device - don’t worry, we’ll add it back! But when this process is running, insufficient RAM is available to flash the Pixhawk. Once you’ve removed the video stream, navigate to Autopilot Firmware, and flash the latest stable ArduSub version. If this doesn’t work, you may need to connect the Pixhawk directly to your computer via USB to flash via QGround Control.
Once your autopilot has valid firmware, you can add the /dev/video2 device. back (H264, 30fps, 1080p, and I prefer RTSP to UDP for performance, but this requires adjusting QGC settings… it will “just work” for Cockpit tho!)
Finally, navigate to Vehicle Setup and load the default parmaters for your frame type. You can then calibrate your accelerometer and compass normally, or even from within the BlueOS Vehicle Setup page.
Once you have the ROV working as expected, we can dig into what might be the issue for your UGPS and Ping. The latter can be configured with assistance from the “surftrack fixit” extension, which validates parameters necessary for the ping sonar to send distances to the autopilot necessary for the (new) SurfTrack flight mode. The UGPS setup should follow the documentation linked in your original thread, and may require updating the software on your UGPS itself?