This page lists customer questions about the WattNode® Modbus® meter and how they were answered or resolved.
The most common customer problems with the Modbus WattNode result from configuration problems with the Modbus master.
- Registers are sometimes documented with leading “3”s or “4”s to indicate holding or input registers. This results in register numbers like “41221”. But the leading “4” is not actually part of the register number and isn’t included in the Modbus packet. To avoid confusion, we do not include a leading “4” in front of our register numbers, but some tools expect or will display a leading “4” anyway.
- Some WattNode values are 32 bits long and must be transferred as two 16-bit registers. Most Modbus master devices support two register orderings (one sometimes called “reversed”) for long integers and floating point numbers. If this isn’t configured correctly, the values will be nonsense.
- The Modbus specification calls for registers to be documented as one-based, but communicated as zero-based, so register 1221 appears as 1220 in the Modbus packet.
A good starting point is to read the WattNode meter’s integer frequency register (at the one-based address of 1221), since it uses the simplest number format (a single 16-bit integer register) and it is unaffected by installation problems like a CT installed backwards or CT connected to the wrong phase.
Frequently Asked Questions (FAQs)
- What software and hardware do you recommend to enable me to gather data from your WattNode® Modbus® and to configure its CT amps ratings?
- Why does the integer frequency register not read 600 (i.e. 10 x 60 hz.)?
- Why do the WattNode integer energy registers sometimes read negative values?
- Why do the WattNode integer energy registers show huge, sudden jumps in energy?
- What is the largest positive number that a 32-bit floating point register can represent?
- Internally, the WattNode use a 64 bit energy accumulator and then outputs that as a 32 bit IEEE-754 floating point number, which supports only six or seven decimal digits of resolution. See the last entry in the table BACnet and Modbus Energy Resolution #Output Resolution.
- Why do the floating point registers read bizzare or invalid values?
- My Modbus Master reports a CRC/checksum error or invalid response even though the WattNode’s Comm LED flashes green.
- The WattNode’s Comm LED flashes green when my Modbus Master software sends it a command message but I don’t get the expected response from the WattNode.
- How do I use a B&B 485LPRJ RS-232-to-RS-485 adapter with Modscan32 to communicate with a WattNode?
- Why does the Wattnode report code 249 (duplicate slave address) and/or 242 (message collision) even though I know the slaves on my bus all have unique addresses?
- The WattNode Modbus meter has never responded to Modbus messages. The COM LED blinks red or yellow, regardless of which address we try.
- My PLC requires a “six-digit” register address but the WattNode manual only documents “five-digit” register addresses.
- I’m writing software to communicate with the WattNode. How do I interpret the float registers?
- Why does the second register of the two registers that make up a 32-bit energy always read zero?