Main functionalities

•Integration of conventional Rotronic devices with a TCP connection

•7 days data logging.

•Audit trail

•Maximum 2000 measurement points can be covered by one RMS-CONVERTSW-100

Communication

OPC UA

•The RMS-CONVERTSW-100 offers the functionality to integrate measurement data, red out via a OPC UA interface. Here the RMS-CONVERTSW-100 acts as a OPC UA client that read out data from a OPC UA server every measurement interval.

•For a successful OPC UA communication, the OPC UA server and the RMS-CONVERTSW-100 must be in range for TCP communication within a network.

More detailed

•The RMS-CONVERTSW-100 software sends the measurement data plus time stamp for each measurement of each OPC-UA-measurement point to the RMS.

•The RMS-CONVERTSW-100 software stores the measurement data plus time stamp for each measurement of each OPC-UA-measurement, that the data are not getting lost in case of network interruption. This data is stored for 7 days.

•If a network interrupt to the RMS happens, the RMS-CONVERTSW-100 software sends the stored data to the RMS-SW automatically to fill the gap in RMS – SW database after the interrupt ends.  

Request OPC UA data

The RMS-CONVERTSW-100 software requests the measurement data for each configured measurement point / OPC UA. The OPC UA Server answers with measurement data. The RMS-CONVERTSW-100 software stores the measured data with the actual time stamp (using the system time of the RMS server as master. Local time of the host where converter software runs is ignored. The converter time stamp is synchronized each RMS interval.). The interval is defined inside RMS and is minimal 60 seconds.

Communication to RMS

•For the communication to the RMS, the RMS-CONVERTSW-100 acts as an standard RMS IOT device, sending data to the RMS server and getting answer.

MODBUS TCP

•Not part of the RMS-CONVERTSW-100, but comming with the next version

Time synchronization

The time (given by the RMS server) synchronizes the system time to the RMS-CONVERTSW-100 every interval. The master of the system time is the RMS-Server. Local time of the host where Converter software runs is ignored.

Installation

•Software runs as console application (.exe) or can be installed as windows service

•To install as windows service, run "RoCollector.exe install" as admin.

•To uninstall the windows service, run "RoCollector.exe uninstall" as admin.

Update

A software update or downgrade can be done only manually. A new software file can be developed and supplied on demand.

•Update (to newer version) or downgrade (to older version) by file (extract .zip file with executables)

License

Please note : A RMS License key for this license is working only with RMS V2.9.0+ !  

Configuration

OPC UA

RMS-Converter (Software version, not Beaglebone version) can monitor (read) values from OPC nodes.

•Configuration in CSV file in the filesystem where the converter software is, format is like that

oFilename can be any filename, needs to be set in settings.json (see below)

oContent is separated by ";".

oLines starting with # will be removed

oColumns

▪Host -> OPC Host + Path

▪NodeId -> OPC Node Id

•If node contains a ";", replace it with a "¦"

▪Type: Measurepoint Type in RMS

▪Serial: Serial in RMS

oFile needs to be saved as UTF-8 (no BOM)

oContent examle

#Host;NodeId;Type;Serial
localhost:53530/OPCUA/SimulationServer;ns=3¦s=true;Adc;99100000

•Additionall file with password, name like config file + host, expect special chars are replaced by '_'

oFile needs to be saved as UTF-8 (no BOM)

oFilename example:

▪config file is named "opcua.txt"

▪host entry is "localhost:53530/OPCUA/SimulationServer"

▪Password file needs to be named opcua.txt.localhost_53530_OPCUA_SimulationServer

oContent

▪Cleartext username:password

▪e.g. "user:password"

▪This content will be read by Converter software, and if it is cleartext it will be replaced with encrypted values which cant be read by a person anymore

•Entry in settings.json to point to the file. If only filename is specified, it will be roothed in the path where the .exe is

osettings.json content example

{
  "License": "xxxx",
  "WebServiceAddress": "ragdev03.rotronic.com",
  "WebServicePath": "wService/wService3.DeviceService.svc",
  "WebServiceHttps": true,
  "DeviceServiceGateway": true,
  "OpcUaConfigFile": "opcua.txt"
}

Pairing into RMS

Pairing the RMS-CONVERTSW-100

Every RMS-CONVERTSW-100 ordered has a serial number integrated (same as the RMS-CONVERTER-100 HW product).

When the software runs, the RMS-CONVERTSW-100 is to be integrated as a standard LAN device.

Integration of OPC UA measuring points into RMS-SW

To integrate the OPC UA measuring points, a csv file is to be created as follows:

GroupName;Typ;Name;ConverterSerial;ConverterMode;Serial;Timeout;Intervall;Mp1Typ;Mp1Name;Mp1AlarmTriggerName

TESTGROUP/TESTSUBGROUP;0;OPC_99100000;987789;23;99100000;240;60;62;OPC_99100000Val;OpcTestOpcTrigger

•GroupName: Name of RMS group, to be defined by the customer

•Typ: Device type -> 0 unknown device type, used for OPC node

•Name: Device name -> To be defined by the customer

•ConverterSerial: Serial number of RMS-CONVERTSW-100

•ConverterMode: 23 for OPC measurement point

•Serial: Serial number of OPC node -> Can be defined by the customer. It must have the form of 1234567890.

•Timeout: Timeout applied to the OPC node in seconds

•Interval: Interval applied to the OPC node in seconds

•Mp1Typ: 62 - Measurement type (62 - digital input; 0 - for ADC measurement point)

•Mp1Name: Name of the OPC measurement  of the OPC node, to be defined by the customer

•Mp1AlarmTriggerName: Name of the alarm scheme.

Example of a csv file:

GroupName;Typ;Name;ConverterSerial;ConverterMode;Serial;Timeout;Intervall;Mp1Typ;Mp1Name;Mp1AlarmTriggerName

NIB/NIB_TEST;0;OPC_99100000;987789;23;99100000;240;60;62;OPC_99100000Val;NibTestOpcTrigger

The csv file can be imported by clicking Tools>Setup>System>Common system settings

System requirements

Operating system

•Windows Sever Core 2012 (and R2)

•Windows Server 2012 or newer (2012 R2, 2016, 2019, 2022, 2025)

•Windows 10 (22H2 or newer)

•Windows 11 (22H2 or newer)

CPU

•Minimum = 1GHz/1Core + minimal requirement of the running operating system

RAM

•Minimum = 1GB + minimal requirement of the running operating system

Storage

•150   MB for installation

•1800 MB for local database (2000 measure points, 60s interval, 7 days keep time)