RiverRay Firmware
Firmware for Teledyne RD Instruments RiverRay ADCP
|
Version
|
Status
|
Changes and Known Issues
|
| 44.24 (Jan. 2021) |
Testing | - This is the minimum firmware version for RiverRays shipped circa November 2020 or later. - Increased scope of supported Bluetooth hardware. |
| 44.22 (Mar. 2020) |
Testing | - This is the minimum firmware version for RiverRays shipped circa March 2020 or later. - Added support for new internal GPS module |
| 44.21 (Jul. 2017) |
Required Minimum as of 8/6/2018 |
- Improved vertical beam ranging. - Increased scope of supported Bluetooth hardware. +May be required for new (< July 2017) instruments. |
| 44.19 (Jan 2017) |
Allowed (Until 8/6/2018) |
- Improved performance in low backscatter conditions. |
| 44.18 (Sept. 2016) |
Minimum Required (2/27/2017 to 8/6/2018) |
- Added fix for Temperature "spike" when reading sensor
under certain conditions |
| 44.17 (Aug. 2015) |
Testing (Until 2/27/2017) |
- Added Feature controlled WM2 and WM12 Manual Modes. - Added water profile menu command WC, WM and WV to the user menu. - Added support for systems with new End Cap 3 separate LEDS internal GPS new bluetooth module |
| 44.16 (Sept. 2013) |
Testing (Until 2/27/2017) |
- Added support for vertical beam with range-to-bottom
output. - Fixed Temperature sensor test to recognize sensor initialization failure. - Added timestamp to recorder download file name. - Progress indication added to recorder block erase. - Added diagnostic output of GPS data. - Fixed error in PT3 cosine duty cycle output. - Report battery voltage without offset. - Fixed transmit length for PD0 output. - Modified PT3 to add option to use 8-bit sampling. - Increased bottom track RSSI sample resolution. |
| 44.15 (Jan. 2013) |
Required Minimum (9/30/2013 - 2/27/2017) |
-Fixed bug that in rare cases prevented proper power-on
initialization of the ADCP. Once successfully powered on,
system would function normally. -Note: No other changes from 44.14. -Set as required minimum in OSW Tech Memo 2013.04. |
| 44.14 (July 2012) |
Testing (Until 2/27/2017) |
-Improved Bottom Track depth measurement. -Issue: In rare cases power-on does not properly initialize the ADCP. Once successfully powered on, system should function normally. Note: Potential compass calibration issues remain when using Honeywell Compass, see: Best Practices for Calibrating a TRDI RiverRay Compass |
| 44.13 (June 2012) |
Testing (Until 2/27/2017) |
-Added TRDI ISM Compass support. -Added support for FPGA code 7002. -Improved system performance in shallow low back scatter conditions and all surface bins. -Issue: Depth not being computed using the actual beam angle relative to vertical but the nominal beam angle of 30 degrees. The actual beam angle is dependent on the speed of sound. |
|
Testing
(Until 2/27/2017) |
-Improved system performance for shallow fast
conditions.
-Improved system performance for shallow, low
backscatter conditions.
-Issue: Potential low velocity bias in low backscatter conditions -Issue: Depth not being computed using the actual beam angle relative to vertical but the nominal beam angle of 30 degrees. The actual beam angle is dependent on the speed of sound. |
|
|
Testing
(Until 2/27/2017) |
-Improved bottom tracking
-Issue: Potential low velocity bias in low backscatter conditions -Issue: Depth not being computed using the actual beam angle relative to vertical but the nominal beam angle of 30 degrees. The actual beam angle is dependent on the speed of sound. |
|
|
44.10
(Feb. 2010) |
Testing
(Until 2/27/2017) |
-Initial Release
-*Requires WinRiver II
software 2.06 or later.
|
Software/Firmware Status Definitions
Required Minimum: Minimum version required. This version has proven stable and may contain enhancements that are significant over previous required versions
Recommended: Shown to have been reliable and contains features that result in a recommended upgrade over the required version. There could be a few specific use cases where this version may have issues that would result in some users not using this version. If so, those cases will be noted.
Allowed*: Deemed reliable during initial testing. Any issues will be noted along with improvements available over prior versions. Use of allowed versions may be desired in cases when the changes benefit a significant number of the user's conditions or equipment. For example: a new version of software is released that adds support for new hardware. If the user has this hardware, they would need to upgrade to the newer software before it becomes recommended or required. Use of these versions by experienced users will also help OSW identify any unknown issues.
Testing*: OSW is currently testing; any known issues or advantages over prior release will be noted. The use of a version that is in testing should usually be limited to advanced users that can trouble shoot potential issues and provide feedback on any irregularities or problems observed.
Do Not Use: A version either prior to the required minimum or that contains issues that significantly affect operations.
*Note: A version may remain in Allowed or Testing indefinitely. Example: A new version is released while the prior version is still in Testing. In this case the prior version may remain in Testing, while future testing efforts are placed on the newer version.
Return to Moving-Boat Deployment - Software and Firmware
Links to the manufacturer's software and firmware are provided primarily as a service for USGS users. However, in some cases, access has also been provided for other agencies with the manufacturer's permission. Software or firmware without a direct download link should be obtained from the manufacturer.