User`s manual

Western Reserve Controls 1782-JDM User’s Manual

PUB 24.0 PRELIMINARY

5 DeviceNet I/O Assembly Formats

The following tables define the format of the DeviceNet data sent to and received from the JDM. The

exact format of the output and input data that is sent from and received at your DeviceNet master is

defined by the ModBus command used. The following tables provide the general format and illustrate the

differences between the ASCII and RTU modes. Review the ModBus spec or your ModBus device’s

user’s manual for more details.

5.1 Output Data, ModBus Command

There are two types of output command assembly formats. The output command format depends upon

whether or not the command data length is less than or equal to 7 bytes or is 8 or more bytes.

If the command length is 8 bytes or more, then a “fragmented message” is created by the host and is sent

to the JDM. This will be the more common format for your ModBus command strings and the format that

the JDM expects to receive. See Table 5-1.

Table 5-1 I/O Assembly Object Instance 2 Data Format – Fragmented Command

Byte

(Offset value)

Data

0 Record number

1 Length

2 Address

3 Command

4 Data www – LSB

5 Data www – MSB

6 Data xxx – LSB

7 Data xxx – MSB

…

N Last data – LSB

N + 1 Last data – MSB

If the ModBus command string data is 7 bytes or less, then use the command format shown in Table 5-2.

This will generate a “non-fragmented DeviceNet message”. The 3F (hex) leading byte value indicates to

the JDM that this message is a short string that was not fragmented by the sender.