Advanced configuration
This chapter describes various additional features of the Modbus/TCP interface. Besides the function description, step-by-step guides on how to configure those features are also included.
Configure variable processdata
Determine the register addresses of the variable processdata registers, which adapt to the input/output processdata lengths configured per port. See Registers 11000…11257 - Variable Processdata Registers for the layout of the input and output processdata sections.
Before you begin
Make sure that:
The desired ports are configured as IO-Link. See Set port mode.
Steps
To determine the variable processdata register addresses:
Configure the input and output processdata length (in bytes) for each port by writing to registers
9n06(Input Processdata Length) and9n07(Output Processdata Length), wherenis the port number. See Registers 9100…9800 – Port Configuration.For example:
Port 1 Input: 3 bytes
Port 3 Input: 2 bytes
Port 4 Input: 5 bytes
Port 1 Output: 4 bytes
Port 3 Output: 1 byte
⇒ Starting at register
11002, the input processdata of ports 1…8 is listed first in ascending order, followed directly by the output processdata of ports 1…8, with a padding byte added after a port’s data whenever needed so that the next port’s data starts on a word boundary.For the example configuration, the resulting layout is:
Address
Section
Port
Data Length
Padding
Word Boundary
11002 + 0
Input Processdata
1
3 bytes
1 byte
2 words
11002 + 2
Input Processdata
3
2 bytes
0
1 word
11002 + 3
Input Processdata
4
5 bytes
1 byte
3 words
11002 + 6
Output Processdata
1
4 bytes
0
2 words
11002 + 8
Output Processdata
3
1 byte
1 byte
1 word
Ports which have zero length configured or are not in IO-Link mode do not reserve space in the register.
IO-Link ISDU data
Note
Please check whether IO-Link is supported by your module before using this function. For more information on product variants that support IO-Link, see Supported product variants.
Read and write acyclic IO-Link ISDU (Indexed Service Data Unit) data, e.g. to access parameters of a connected IO-Link device, via the Acyclic Command Channel registers, see Registers 100, 300 – Acyclic Command Channel (including ISDU Read/Write Request) for the register layout.
Before you begin
Make sure that:
The Modbus/TCP device has been added successfully. See Add the Network Module as Modbus/TCP device.
The port is configured as IO-Link. See Set port mode.
An IO-Link device is connected to the port.
Read ISDU data
To read ISDU data via Modbus:
Write the port number (
101), index (102) and subindex (103) of the desired IO-Link parameter to the Command Request registers.Write the command
1(read) to register100.⇒ The requested data is available in the Command Response registers
300…305(Data Length) and306…421(Data).
Write ISDU data
To write ISDU data via Modbus:
Write the port number (
101), index (102) and subindex (103) of the desired IO-Link parameter to the Command Request registers.Write the data to registers
105…220and the desired data length to register104.Write the command
2(write) to register100.⇒ The Command Response registers report whether the write request was successful, see Error codes.