Announcement

Collapse
No announcement yet.

Case 320

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Case 320

    Question:
    The RMS-GW with firmware version V2.0 and V2.1 go into encrypted mode after a certain period, after that the RMS-GW and all attached devices into timeout.

    Possible Root Cause:
    1. RMS-GW V2.0 firmware bug: the upgrade of the RMS-GW firmware from V1.4/V1.5 to V2.0, after some time the gateway goes into encrypted mode.
    2. RMS-GW V2.1 firmware bug: the upgrade of the RMS-GW firmware from V1.4/V1.5 to V2.1, after some time the gateway goes into encryption mode.
    Solution:
    1. Upgrade to RMS software V2.1.0 or higher. This version enables encrypted communication.
    1. Update all gateways with RMS Software or RMS Config to the newest version V2.2. Unplug the device from the power supply/POE and Ethernet connection. Reset the DB, table "devices" in the SQL database. Update the devices with the RfAddress=254 with the query below:
    2. "Query"
    3. USE [RMS]
      GO
      UPDATE [dbo].[Devices]
      SET [Encrypted] = 0
      WHERE RfAddress = 254
      GO
    4. Recycle the Application Pool Net.4.5. Power up again the device with power supply/POE.
    1. Downgrade all Gateways with RMS Config to the latest version V1.5. Unplug the device from the power supply/POE and Ethernet connection. Reset the DB, table "devices" in the SQL. Update the devices with the RfAddress=254 with the query below:
    2. "Query"
    3. USE [RMS]
      GO
      UPDATE [dbo].[Devices]
      SET [Encrypted] = 0
      WHERE RfAddress = 254
      GO
    4. Recycle the Application Pool Net.4.5. Power up again the device with power supply/POE.
    5. Attention: Some of the newest devices as the RMS-LOG-T30-868/915 are not able to communicate with this Gateway version.
    Additional Information:
    This issue appears if the customer does a RMS-GW firmware update from the 1.4/1.5 to V2.0/V2.1. If an update is done directly from V1.4/V1.5 to V2.2, the issue doesn't occur. If the firmware is updated from V2.0/V2.1 to V2.2 then the issue can also occur. The firmware version V2.0/V2.1 has a bug that activates the encryption mode.

    This issue only occurs in the software V1.3.1/V1.3.2/V1.3.3.
Working...
X