Skip to main content
Skip table of contents

2.20.4

Release date: June 13, 2023

Critical Power Budget Notice for RBRsolo3, RBRduet3, and RBRcoda3

Due to component obsolescence, we were forced to change a memory chip. This resulted in increased power consumption that was not accurately reflected in Ruskin. Some users, particularly running at 1Hz or 2Hz, may have had deployments that stopped far earlier than Ruskin estimated. All autonomy figures have been reviewed and adjusted accordingly. An updated firmware image also accompanies this Ruskin release which performs several aggressive power optimizations to improve the situation.

Our apologies for the frustration this will have caused.

New Features

  • Updated autonomy engine estimates for RBRsolo3, RBRduet3, and RBRcoda3 instruments
  • Added support for firmware v1.063 (107) for RBRsolo3, RBRduet3, RBRcoda3
  • Added support for firmware v1.003 (202) for RBRtridente
  • Updated documentation
  • Updated Quick Start Guide (QSG) for RBRduet3 T.ODO, RBRcoda3 T.ODO, RBRcoda3 T.ODO (vehicle integration)
  • Updated Ruskin User Guide (RUG) for Compact instruments, Standard instruments, and Sensors
  • Updated RBR Instrument Guide (RIG) for RBRsolo3 and RBRduet3
  • Updated RBR Instrument Guide (RIG) for RBRcoda3, RBRquadrante, and RBRtridente
  • Updated RBR Instrument Guide (RIG) for RBRduo3, RBRbrevio3, RBRconcerto3, and RBRmaestro3
  • Updated RBR Instrument Guide (RIG) for RBRfermata

Improvements

  • RSK-9831 - Prevent deploying with certain averaging schedules when using gain ranging sensors
  • RSK-9814 - Updated channels for RBRtridente sensors
  • RSK-9833 - Added additional RBRfermata power options

Bug fixes

  • RSK-9822 - Dissolved oxygen concentration channel is missing from the calibration region options
  • RSK-9824 - Ruskin is improperly reading the schedule from the RSK if downloaded using v2.19.1
  • RSK-9833 - Plot export only exports partial image
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.