I installed new Navigator with new Blue OS SD card and installed new firmware; Official version Ardusub. Ran on different computer with fresh install of QGC. DVL connected but no installation of its firmware or any other parameter changes. Tested ROV and Stabilize and Depth hold were steady as should be.
I installed latest version Ardusub Beta 28 and tested again with no DVL set up and back to Jerking just like before!I
If this was in QGC, it may help to make sure you’re using the latest recommended version, and to try reconnecting the vehicle if it failed to fully load the parameters.
BlueOS is the software that runs on the onboard computer, and is unrelated to the vehicle’s motion control (beyond serving as a communications proxy), so changing BlueOS version is not expected to effect jerkiness in flight modes.
ArduSub is the vehicle’s autopilot firmware, which is what I suggested for you to try the latest beta release of - it can be installed onto the flight controller board from the Autopilot Firmware page of BlueOS’s web interface (or the Vehicle / Firmware page in BlueOS-1.0).
This does not explain why fresh install of everything including QGC and Blue OS Official worked perfectly fine. Install of Beta 28 back to Jerking and returning to Official Ardusub continues Jerking! Only changes were the Ardusub versions.
Discovered that to get rid of Jerking I had to reload the “Official” Firmware but if I tried to go back in Blue OS to run Beta 28 right back to Jerking.
After some discussions with Geoff Cook at SeaView systems and trying to replicate his set up I loaded the Firmware 4.1.0 (Stable) then switched back to run the Version Beta 28 and no Jerking anymore. Loaded DVL Extensions changed PIDs and all looks good.
Note: the i for information with the “Official” firmware says it’s latest stable version which was assumed to be 4.1.0 or newer. Not sure what it is but it doesn’t work and if you leave 4.1.1 (Beta) install it doesn’t work.