What is the data configuration in the DeviceNet Scanlist for the HI 200DNWM?

When I add the "HI 200DNWM" to my DeviceNet Scanlist it reserves 4 bytes of data on the input side, none on the output side. What exactly is the configuration of this data? (i.e. Status Bits and Gross Weight?)

In the new HI 200DNWM Series B there is a 4 byte output field in the scanner table, for reading/writing parameters. How are these used?

The 2 versions of the HI 200 DNWM are the Series A modules and the Series B modules. The Series B modules will be marked as Series B. The Series A modules are not marked. So if a module is not marked Series A or B, it is a Series A.

In the scanlist of the scanner, our HI 200DNWM Series A module will use 4 bytes of polled data to the input table. This data will be the NET weight from the scale. This will be a 32 bit integer value. There is an implied 3 decimal place resolution.

We do not use the output table for the Series A modules. Any other data being written to or read from the HI 200DNWM Series A would be through explicit messages.

The Series B HI 200 DNWM modules have 2 output words and 2 input words mapped into the scanners I/O tables   If the data in the 2 output words are left as zero, then the modules will work just like the Series A module. The input table will have Net weight, as integer with three decimal place resolution.

If you use the 2 output words, then the 2 input words will reflect data based on the 2 output words.

Example: If you request the Gross weight by designating a read of parameter #16 in the output table, then you will receive the Gross weight in the input table. This would continue until you change the data in the output table by either requesting a different parameter to read/write to, or set the output table back to zero (read Net weight).  The programmer would need to keep track of the data being written to the output table to insure he knows what is being sent to the input table at any given time.

Explanation of the COMMAND INTERFACE USE (Only in the Series B modules)
Referring to the manual on page 5-8.

You have two words (4 bytes) being sent to the module from the PLC.
As shown in the manual on page 5-8, bytes 0 and 1 are the data you will write to the module. (If you are not doing a write, this data is ignored.) Number of decimal points and Format of this data will depend on the Multiplier setting (parameter 37).
Byte 2 is the parameter number you want to read or write.
Byte 3 is used to tell the module if this is a read or a write command.

EXAMPLES OF USING COMMAND INTERFACE

To do a Tare Command.
You will need to write a one to the module in parameter number 18.
Write a value of "1" to byte 0 and a value of "0" to byte 1.
Write the parameter number ( number 18 for the tare command) in byte 2.
Write a value of "1" to byte 3 (tells the module you are doing a write).

Bit pattern for the four bytes of data would be:
Bytes 1 & 0: 0000 0000 0000 0001
Bytes 3 & 2: 0000 0001 0001 0010

The tells the module you are doing a write to parameter number 18 and the value you are writing is a 1.

Another example would be to do a calibration low command. This would be the same as above except the parameter number would be 20 instead of 18.

Bit pattern for the four bytes of data for the cal low command would be:
Bytes 1 & 0: 0000 0000 0000 0001
Bytes 3 & 2: 0000 0001 0001 0100

A calibration high command would be the same as the calibration low command except the parameter number (byte 2) would be 21 instead of 20.

NOTE:  After writing a 1 for a parameter to run a command, insure you write a 0 into the parameter to have it ready to run the command the next time.  Since the module will be looking for the value to go high, if you do not write a 0 into the parameter, it will not see a change and therefore cannot run the command again.