Hi Jacob,
My most recent tests used QGC 3.2.4 rev4 (GPU safe mode), with Companion 0.0.10 on the Pi, and ArduSub 3.5.1 on the PixHawk. This still produced video lag up to 2 sec. So, hopefully your comment means that it’s the Companion update that fixes the video lag issue.
So, I tried updating the firmware by manually downloading the files (this is where searching the old forums seems to be necessary, for these links). Unfortunately I am not able to use the wireless approach; due to system restrictions by my IT department, I can’t set the static IP and also have wireless activated.
Both the Companion and the PixHawk updates failed, as follows:
Companion update failure:
I downloaded ardusub-raspbian.img.zip from https://s3.amazonaws.com/downloads.bluerobotics.com/Pi/stable/ardusub-raspbian.img.zip. I connected the ROV tether, directed a Chrome browser to 192.168.2.2:2770/system, selected the zip file under “Upload zipped update”, waited while it churned through loading the 1.3 GB file, and got this message:
“validating archive
Archive does not look like a companion update!”
PixHawk failure:
I downloaded ArduSub-v4.px4 from http://firmware.ardupilot.org/Sub/stable/PX4, selected that .px4 file to upload, and here is the output:
Attempting upload from file /tmp/data/ArduSub-v4.px4
Stopping mavproxy
Flashing Pixhawk…
Loaded firmware for b,0, size: 789796 bytes, waiting for the bootloader…
If the board does not respond within 1-2 seconds, unplug and re-plug the USB connector.
attempting reboot on /dev/ttyACM0…
if the board does not respond, unplug and re-plug the USB connector.
attempting reboot on /dev/ttyACM0…
[… message repeated 5 times…]
Found board 9,0 bootloader rev 4 on /dev/ttyACM0
WARNING: Firmware not suitable for this board (board_type=9 board_id=11)
[… message repeated MANY times…]
Timed out trying to catch bootloader!
Please try again.
Waiting to restart mavproxy…
Restarting mavproxy
Complete!
Guidance please? Thanks!