Change Log/Release Notes

<< Click to Display Table of Contents >>

Navigation:  Hardware Overview > Gateway and Converters > RMS-CONVERTER-100 >

Change Log/Release Notes

1.Version Overview

Please find below the meaning of the version.

1: Major version number.

X.1: Minor version number.

X.X.1: Bug fix or specific update version number.

 

2.Rotronic Tracking System

Rotronic use a tracking system to monitor bugs, features, improvements and change requests. This tracking system is the basis for any software, hardware and firmware User Requirement Specification based upon the GAMP©5 validation model. Each point will be recognized with an ID (eg. RMS-XXX). A description and details are attributed to each point within the tracking system. All changes documented within the RMS Release Notes will have an ID number and a description.

 

3.Version V1.7.0

 

a.Release Details

The main target of this firmware version has been to adapt the RMS-CONVERTER-100 to work within an Azure environment including a traffic manager.

 

b.New Features

ID

Description

RMS-CONVERTER-569A

Under settings, a button to restart the converter has been added.

RMS-CONVERTER-571A

Comment field added for each line within the modbus map.

RMS-CONVERTER-575A/1295A

Addition of a secondary DNS server option.

RMS-CONVERTER-1221A

Adaptation of the converter to work with an Azure environment including a traffic manager. Including update of the device driver to improve communication stability and reliability.

 

c.Bug Fixes

ID

Description

RMS-CONVERTER-567A

When using a special character in a modbus map, the RMS-CONVERTER blocks.

RMS-CONVERTER-570A

When importing a modbus file, a failure message "Invalid file" appears.

Only 21 modbus lines are available instead of 22.

 

4.Version V1.6.0

 

a.Release Details

The main target of this firmware version has been to integrate the AirNet II Particle Counter into the Firmware.

 

b.New Features

ID

Description

RMS-CONVERTER-2924

In case of a first operation and integration into RMS via Converter, or in case of short power interrupt, the particle counter Airnet II need to be reinitiated by a modbus order, that enables/re-enables the particle counter. For that reason, a new command ‘Write single coil’ with starting address and switching status IS implemented into the Modbus editor of the Converter. Every interval this order is sent out from the converter to the particle counter. The modbus order cannot be linked to any RMS function. It works independent between particle counter and converter.

 

5.Version V1.5.0

 

a.Release Details

The main target of this firmware version has been to correct existing bugs that can occur when an RMS-CONVERTER-100 and a HygroLog NT/HL-NT are integrated into a system.

 

b.New Features

ID

Description

RMS-CONVERTER-2646

In protected IT infrastructures, the use of a CA certificate could be mandatory to identify that the RMS-CONVERTER-100 is a permitted network participant. For that reason such a CA certificate can be uploaded to the RMS-Converter.

 

c.Improvements

ID

Description

RMS-CONVERTER-2850

Modbus Editor – The Signed Integer as a further number format is added.

 

d.Bug Fixes

ID

Description

RMS-CONVERTER-2530 & 2545

HL-NT input 7 not transmitting probe serial number.

RMS-CONVERTER-2429

Validation issue with Battery test for HL-NT. The HL-NT units have PoE functionality. The battery levels shown on the HL-NT's are incorrect. The information about the battery level is not displayed anymore.

RMS-CONVERTER-2409, 2426, 2222

Within the audit trail, the event "Probe replaced" appears without any probes being replaced.

Important due to the range of HygroLog and HL devices as well as the range of docking stations, Rotronic cannot fully guaranty that this bug is corrected for the entire range of products.

RMS-CONVERTER-2425

Data gaps by HL-NT devices (only data gaps on RMS, data is available on memory card).

RMS-CONVERTER-2575

When the probe on a HL-NT is disconnected, it shows probe replaced (SNxxx -> 0) in the audit trail, whereas a sensor error should appear.

RMS-CONVERTER-2496

Data gaps when reading out digital inputs.

Note: Update to RMS Software V2.2 is necessary.

 

6.Version V1.4.0

 

a.Release Details

This firmware version has been programmed to implement the Modbus TCP Editor to allow for easy integration of 3rd party devices in the RMS environment.

 

b.New Features

ID

Description

RMS-2341

Modbus Editor to integrate Modbus TPC devices (only Ethernet devices) into the RMS.

 

c.Bug Fixes

ID

Description

RMS-2587

RMS-Converter causes a data gap after an RMS software restart, which is caused by an empty device list on first query (only visible as of the RMS V2.0.0).

 

7.Version V1.3.0

 

a.New Features

ID

Description

RMS-793

Encrypted communication between Webservice and Converter.

 

b.Improvements

ID

Description

RMS-1112

Adjustment for differential pressure devices implemented: PF4 first generation.

RMS-795

Adjustment for differential pressure devices implemented:        PF4/5 second generation, CRP5.

RMS-831

Implemented two new devices: RMS-8ADC-L-R, RMS-4RTD-L-R.

RMS-1012

Implemented a new device: RedLion E3-16ISOTC.

RMS-832

Login window integration. During the first 10min from the startup, the default password and user can be used.

 

c.Bug Fixes

ID

Description

RMS-787

Automatic restart function after system break down. Improved startup function for the OS.

RMS-740

HL NT audit trail message “Probe replaced SNxxxx to SN0 corrected”.

RMS-829

By configuration the RMS-8ADC-L-R unit is mv, it shall be mA.

Channel number from the RMS-8ADC-L-R is 0 to 7. In RMS Webservice was it 1 to 8. Corrected to 0 to 7 in RMS Webservice.

RMS-849

DNS address get reset to “8.8.8.8” after reboot.

RMS-1104

Converter deleted HL-NT log files that are older than 1 week.

RMS-939

PF5/4 reconnection after network issues.

 

Updated: 02.10.2023