Issue:

All registers for a specific NetBotz slave address fail if sensor is disconnected.

Product Line:
NetBotz

Environment:
NetBotz
Modbus Polling

Cause:

When you set up a NetBotz appliance to be monitored via Modbus, each pod is considered a slave and each of the sensors associated with that pod and it's sensors will be seen as the individual registers. If one of the sensors is unplugged, all registers for that pod/slave will stop reporting values.

Resolution:

The obvious resolutions are to either reconnect the sensor or replace it with a working sensor if the disconnection is due to a failure. If replacement is not an option, deleting the sensor and it's register should resolve the issue.

This issue may be resolved in a future revision of Botzware.