Tweet
When updating a wireless RMS-MLOG Rotronic recommend the following:
1) Only update the RMS-MLOG devices with the RMS software.
2) Do not update the RMS-MLOG devices with the RMS-CONFIG software. The process doesn't work correctly and the wireless device many remain blocked and is no longer usable. In the RMS-CONFIG V1.1.2, the firmware update feature is no longer available.
3) Ensure that no wireless devices are connected to RMS-CONFIG. If a wireless device is connected to RMS-CONFIG, it is using the service channel, the firmware update will also run on the service channel. Conflict during communication could mean that the wireless device getting a firmware update may remain blocked and is no longer usable.
4) Make sure that only one version of the RMS software (different version, cloud or on-premise, different servers or companies) is running in the building/area. Parallel software's running at the same time carrying out firmware updates will lead to wireless conflicts. Should wireless conflicts occur, the device may remain blocked and is no longer usable.
The recommended steps to carry out a firmware update:
1) Use the RMS software.
2) Ensure that no other RMS software's are running.
- Cloud and on-premise running within the same company.
- Two companies running in the same cloud.
- If various versions of the software are running, ensure that firmware updates are not happening at the same time.
3) Should the device log interval be >1min, then update the data logger to a 1 min log interval.
4) Ensure that the devices have a good signal reception:
- The recommendation from Rotronic's side is >-70dBm.
- Make sure that the device is close to the gateway.
- Make sure that the line of sight between the device and the gateway is clear during the update process.
5) Do not use RMS-CONFIG.
Let us know if you have any questions!
1) Only update the RMS-MLOG devices with the RMS software.
2) Do not update the RMS-MLOG devices with the RMS-CONFIG software. The process doesn't work correctly and the wireless device many remain blocked and is no longer usable. In the RMS-CONFIG V1.1.2, the firmware update feature is no longer available.
3) Ensure that no wireless devices are connected to RMS-CONFIG. If a wireless device is connected to RMS-CONFIG, it is using the service channel, the firmware update will also run on the service channel. Conflict during communication could mean that the wireless device getting a firmware update may remain blocked and is no longer usable.
4) Make sure that only one version of the RMS software (different version, cloud or on-premise, different servers or companies) is running in the building/area. Parallel software's running at the same time carrying out firmware updates will lead to wireless conflicts. Should wireless conflicts occur, the device may remain blocked and is no longer usable.
The recommended steps to carry out a firmware update:
1) Use the RMS software.
2) Ensure that no other RMS software's are running.
- Cloud and on-premise running within the same company.
- Two companies running in the same cloud.
- If various versions of the software are running, ensure that firmware updates are not happening at the same time.
3) Should the device log interval be >1min, then update the data logger to a 1 min log interval.
4) Ensure that the devices have a good signal reception:
- The recommendation from Rotronic's side is >-70dBm.
- Make sure that the device is close to the gateway.
- Make sure that the line of sight between the device and the gateway is clear during the update process.
5) Do not use RMS-CONFIG.
Let us know if you have any questions!
Comment