Virtual objects allow another object’s reliability code (or fault code) to be treated as a data value, or allow device error counts to be treated as a data value.
Virtual object numbers are as follows:
| 2001-2100 | Object reliability code (Modbus fault code) for objects 1..100 |
| 2200 | Internal modem temperature, degrees Celsius |
| 2201 | Internal modem temperature, degrees Fahrenheit |
| 3001-3247 | Modbus no-response count by RTU slave ID when VP3-MTM is master |
| 4001-4020 | Modbus no-response count by TCP device number |
Only the no-response counts will be provided as object links. Exceptions will be reported via object reliability code and reflect a configuration error that must be corrected. The no-response count can indicate a latent problem in the field with a device becoming disconnected or non-functional after some period of correct operation. Therefore, monitoring no-response counts as a data point is a valid means of determining equipment failure.
Virtual objects allow another object’s reliability code to be treated as a data value, or allow device error counts to be treated as a data value.
Virtual object numbers are as follows:
| 2001-2100 | Object reliability code (BACnet reliability) for objects 1..100 |
| 2200 | Internal modem temperature, degrees Celsius |
| 2201 | Internal modem temperature, degrees Fahrenheit |
Copyright © 2019 Control Solutions Minnesota, Inc.