Operating Instructions 49
If you see any other error codes of 3000 or higher, contact technical support for assistance.
Severe Errors: 4000 - 4999
Severe errors may cause a processor reset, briefly interrupting communications to the affected
meter, incrementing the
PowerFailCount
, and resetting the
UptimeSecs
to zero.
If you see any error codes of 4000 or higher, contact technical support for assistance.
Communication Errors
The WattNode BACnet keeps a count of several distinct communications errors. Generally these
errors are not serious. The following conditions may cause transient communication errors.
●
Hot-plugging devices into an RS-485 bus.
●
Power cycling some of the devices on a bus.
●
Wiring the RS-485 bus with power applied.
●
Changing the MAC (DIP switch) address of baud rate of a meter while powered on.
The bus should recover quickly when the disruption ends. These errors will be indicated on the
BACnet
Com
LED, which will flash red (see
BACnet Communication Diagnostics (p. 27)
).
If you are seeing one or more of the communication error counts continuously increasing then
there may be more serious problems:
●
Poor RS-485 wiring, biasing, or termination.
●
Excessive noise on the bus.
●
Collisions due to more than one device configured with the same MAC address.
●
Not all devices configured with the same baud rate.
●
BACnet protocol violations: bad timing, invalid MS/TP frame, etc.
The WattNode provides one analog value object for each of the counted communication errors.
The
Present_Value
property reports the count of errors. This count is reset to zero whenever the
WattNode meter is power cycled, reset, or the
Rs485CollisionCount
This meter detected bus activity or corrupted output bytes when this meter was trying to transmit.
This generally indicates two devices with the same MAC (DIP switch) address, a device transmit-
ting at the wrong time, a short-circuit on the RS-485 wiring, or high levels of noise.
Rs485FramingErrorCount
A framing error indicates a corrupted RS-485 data byte (octet). This may be caused by an incor-
rect baud rate, noise, collisions, or an incomplete byte (due to power failure or disconnection).
FrameSizeErrorCount
The specified application data size is longer than the maximum supported by the WattNode meter
(
Max_APDU_Length_Accepted
).
HeaderCRCErrorCount
The MS/TP frame header cyclic redundancy check was invalid, indicating a corrupted frame.
DataCRCErrorCount
The cyclic redundancy check for the data portion of the frame was invalid.
IncompleteFrameCount
The received frame contained fewer bytes than expected.