RCM Software Support
RCM Release History & Compatibility
There are some notable differences with each point release (2.0.0, 2.1.0, 2.2.0, and 2.3.0). When there’s a maintenance update (e.g., 2.1.0 is updated to 2.1.1), there’s generally no feature changes, only bug fixes.
Version 1.0, 1.1, and 1.2 were custom applications run on different internal hardware platforms than 2.x. Units running version 1 cannot be updated to version 2.
The version 2 releases are generally forward compatible, but as of June 2019, due to hardware a compatibility issue, there are some limitations.
Any version from 2.0.0 through 2.2.0 can be updated to 2.2.1. It is not necessary to go through sequentially incremental updates. It is acceptable to update from 2.0.0 directly to 2.2.1. The files for this must be requested directly from Marway.
Also as of June 2019, all new products can be shipped with 2.3.x only (or later if there’s been an update since this writing). It is not possible to ship new units with older firmware versions. Units shipped with 2.3.0 can be updated to the latest version.
Standard catalog Optima 8 Series products are always shipped with the latest version which may change at any time without notice. Custom products may be flagged with specific version freezes which, barring hardware or other circumstances we cannot control, we will attempt to sustain as long as we can.
Should You Update?
In our opinion, updating firmware should only be done if a known specific feature enhancement or problem fix makes a difference to your PDU’s application. Every firmware update in the field always includes risk of having the system become inoperable if the firmware update gets interrupted, or otherwise fails. While we perform some version update testing, we do not test every permutation on every hardware combination. There may be unknowns. If you believe your system should be updated, please contact Marway Support. A unit can always be returned under RMA at the customer’s expense to have firmware updates applied and tested at the factory.
RCM 2.x Release History
Updates and Fixes in 2.3.5
- Fixed a critical bug which could create an endless loop at startup when the user settings were exported then imported, and included the SystemSettings.txt file.
- NOTE: For systems with 2.3.0 through 2.3.4, the bug can be avoided by not importing the SystemSettings.txt file. Exporting is safe, and importing all other files is safe.
- Go to RCM Bulletin 235 for documents and firmware updates to apply to older PDUs.
Updates and Fixes in 2.3.4
- Added configurability to ignore relay sense to accommodate custom low voltages on the relay board.
Updates and Fixes in 2.3.3
- Fixed a bug which could ignore the outlet on delay during startup.
- Fixed a bug which incorrectly showed an AutoOff option in FTP with the getNetwork command.
Updates and Fixes in 2.3.2
- Fixed a bug which incorrectly showed the Environment web interface main menu item when it did not apply to certain models.
- Include OS updates for new FLASH parts in the SOM.
Updates and Fixes in 2.3.1
- Fixed a bug in NetworkSettings.txt importing which caused HTTP mode to be forced to HTTP regardless of the value recorded in the settings file.
Updates and Fixes in 2.3.0
- In NEW units shipped from the factory, the default state of outlets is ON. (Prior to this version, the default was OFF. We've had several requests to have the outlets enabled so the PDU is functional when there may no plans/provisions to access the software initially. Those who will be doing software setup can change the default Startup State to OFF if desired.)
- After a Factory Reset, via Serial, web page, or command line, the default Startup State of outlets will be ON.
- Removed IPv6 settings. here has been little interest in using it, and not all services were capable of running on IPv6, so it has been removed.
- Added temperature and humidity (T/H) sensor Setpoints and Alerts. These behave just like the setpoints and alerts for power objects. Prior versions have had sensor data, but not setpoints and alerts.
- Added T/H sensor data, setpoints, and traps to SNMP. Data is presented in the SNMP standard table of entPhySensorTable. Setpoints and other Marway-specific details are in custom tables. Note that regardless of the PDU's configuration for degrees F or C for web and CLI, the SNMP values are always in degrees C.
- Added on-demand CRC check of bootloader and application binaryin FLASH. It's viewable in the web System > Firmware Versions panel, via CLI using the command `getSystem crc`, and via RESTful API via `GET /system/1/crc`.
- Added new CLI command syntax for outlet switching: #> setOutlet 1 on|off|cycle
- Added new aliases to many CLI command parameter names.
- Updated SNMP entPhysicalTable.entPhysicalContainedIn to more accurately show the lineage of outlets to their source phase.
- Updated output of `viewLog` CLI command to include a DateTime column. (Wewere trying to keep the width minimized, but yeah, who doesn't want to see the date and time?)
- Improved handling of `setProfile|setMy` command errors.
- Fixed a bug in SNMP which did not allow -1 data entry to disable a power object setpoint.
- Fixed a bug in SNMP where setpoints could fail to change from normal to disabled when setpoint settings were cleared.
- Fixed a bug with setpoint validation which could allow certain illogical scenarios to validate.
Updates and Fixes in 2.2.1
- Fixed bug in web Network page which could erase IP settings when enabling SNMP for the first time.
- Fixed bug which prevent outlet labels from being editable in the web UI in certain specific configurations.
- Fixed bug with CLI command `getLog` which did not list all attributes as expected.
- Removed getStartupLog from CLI help which mistakenly listed it as a command.
- NOTE: IPv6 configuration is deprecated. Not all services are capable of running on IPv6, so IPv6 configuration will be removed.
Updates and Fixes in 2.2.0
- Updates key_exchange for SSL/TLS to SHA256.
- Adds the ability to use Private Signed Certificates for HTTPS.
- Some CLI commands for HTTP and HTTPS have been changed relative to how HTTP and/or HTTPS are enabled. The "port" alias has been reassigned to the https port (rather than the http port) to favor the short commands being used for https settings.
Updates and Fixes in 2.1.4
- Includes updates to aid in Marway's manufacturing. No user-feature changes.
Updates and Fixes in 2.1.3
- Includes updates to aid in Marway's manufacturing. No user-feature changes.
Updates and Fixes in 2.1.2
- Fixed bug which could cause FTP to start even when the Enabled setting was set to false.
- Fixed bug which could prevent T/H sensors from being read.
Updates and Fixes in 2.1.1
- Fixed bug which may create two false Alarm listings.
- Fixed bug which could limit the maximum value of a voltage alarm to the maximum inlet rating (but which should have allowed a greater value).
- Fixed bug which could cause errors in the display of CLI command `getPhases`.
- Fixed bug which could prevent setpoint alarm events from being logged.
Updates and Fixes in 2.1.0
- 3-phase Wye units with integrated power monitoring will now show Total power values for current, watts, voltamps, and voltamps reactive for inlet power.
- Telnet may now be configured to run on a user-defined port.
- Telnet may now be disabled or enabled to run.
- SSH may now be configured to run on a user-defined port.
- SSH may now be disabled or enabled to run.
- Temperature and humidity data is now available on the LED display. (Data is not yet available on SNMP, and does not yet have setpoint management.)
- Prior to 2.1.x, any user allowed to use Telnet/SSH was automatically given all user privileges. As of 2.1.0, privileges may be individually assigned for users with access to Telnet/SSH.
- Logging of user actions is now more precise in showing who and through which protocol the action was performed. (Prior to 2.1.0, actions performed via SSH could not log the exact user name.)
- The RESTful API includes new commands to retreive the setpoint status of phase objects.
- `GET /phases/1/setpoint_status_amps`
- `GET /phases/1/setpoint_status_volts`
- The alert acknowledgement web page is now better formatted for mobile devices.
- Most web interface buttons have been changed from images to HTML/CSS which provides better UI interactivity, and reduces demands on the PDU processor when serving HTTPS by eliminating enctyption of images. As a result, HTTPS should feel a little more responsive.
- A number of content improvements to built-in help files, and field tooltips.