The values of data registers contained within this device are displayed on this page, and optionally changed. Check the Update box if the value should be updated, and enter a new value. Check the Hex box if you wish to view or enter values in hexadecimal (not recommended for floating point).

Click Update to view the most recent data values. Click "Prev" or "Next" to scroll through the list of registers. You may also enter a number in the "Showing" box to jump directly to a given register when Update is clicked.

The default data will be stored into the local register when the server times out if the server timeout is set to a non-zero value. A server timeout occurs when this amount of time has elapsed without this register being written by a remote device. The server timeout is reset by any of (a) remote Modbus TCP client (master) writes to this register; (b) remote SNMP manager writes to this object; (c) remote LonWorks network variable output data is received by this register.

Registers are either 16-bit integer or 32-bit floating point "double" registers. Integer register numbers start at #1. Floating point registers start at #1001 and are all referenced as odd numbers. A special set of registers begin at #9001. These are error code registers generated automatically by the system.

Error code registers are automatically named -Sys Error, Fn #n for system errors, -TCP error, device #n for TCP device errors, and -RTU error, device #n for Modbus RTU errors or BACnet device errors. In each instance of "device", the "n" is device number as referenced on other pages.

Error encoding for devices: ABCCC where A=exception codes 1..3 (4), B=error code as follows, and CCC=rule number:

Error code B indicates the following errors:
1 = Transaction ID out of sync
2 = Exception code returned by remote device
3 = Function code mismatch (bad packet)
4 = Inusfficient data (bad packet)
5 = No response from remote device, timed out
6 = CRC error in received packet
9 = Socket error (CCC=error code, see below)

Error code A indicates the following exception codes only when B is code 2 indicating an exception code was returned:
1 = Illegal function code
2 = Illegal data address (the requested register does not exist in the device)
3 = Illegal data value
4 = other/out of range code

Some example error codes that are common: 5001 (05001) means no response from device at map rule #1.  Example 2: 22005 means exception code 2 occurred on map rule #5. This generally means the register you attempted to access is not available at that remote device. Example 3: 6039 means a CRC error was received at map rule #39, and generally indicates a transmission error due to noise on the line.

Special case of socket error: Code will be >9000, and 9xxx will indicate socket error code xxx. Common socket codes include the following:
104 - Connection reset by peer
105 - No buffer space available
111 - Connection refused
112 - Address already in use
113 - Connection aborted
114 - Network unreachable
116 - Connection timed out
117 - Host is down
118 - Host is unreachable401 - General socket error
516 - Timeout, no response from remote device