Table of Contents
Advertisement
H OW IS BAT T ERY LI FE CACH ED IN TH E GAT EWAY?
9.6
How is Battery Life Cached in the Gateway?
The battery life of a device reported in the gateway webpage and on Modbus connection is
populated as follows:
– Gateway checks for response to Command 778.
– Gateway checks for device variable code 243 ("battery life") in Command 9.
– Gateway checks for variable units code of 53 ("days") in Command 3.
If a valid message is received, then battery life is set.
9.7
What Happens When Multiple Devices Have Same Tag
Name?
If same tag name is used by multiple devices in the same WirelessHART network, then they
will still join the network but will not operate as desired on Modbus connection. Modbus map
is assigned based on Device's tag name. Therefore, every device should have a unique tag
name, else Modbus exception will occur.
9.8
What Value is Displayed on Modbus Registers when a
Device Goes Offline?
– When a device goes offline the PVStale, SVStale, TVStale and QVStale reports zero value.
– Communication status register also shows device disconnection. However, this does not
happen immediately.
– Trying to read data from Modbus registers of a disconnected device will result in Modbus
exception.
9.9
What Value is Displayed on the Gateway Webpage
when a Device Goes Offline?
– When a device goes offline the Devices page (in admin account) marks the device as dis-
connected with a red color row entry.
– When a device goes offline the Devices page (in monitor account) marks the device as
idle.
– The last recorded device values are displayed on the webpages.
5 8
Battery life will be displayed as 65535.000 until battery life value is reported by de-
vice in burst message. Initially, it may take some time to populate.
Battery life of 65535.000 is also displayed for loop powered devices.
G OO D T O KNOW
3B NP 10299 2 B
Advertisement
Table of Contents
Troubleshooting
