Setting The Bus Coupler Parameters; Setting Parameters For The Modules - Emerson AVENTICS EtherNet/IP Systembeschreibung

The total length of the input data in the example configuration is 12 bytes. This
consists of 4 bytes of module input data and 8 bytes of module diagnostic data.
The valve system always sends and receives the input and output data bytes in
the same physical sequence. This cannot be changed. In most masters, however,
alias names can be assigned to the data, making it possible for users to select any
desired names for the data.
After the PLC configuration, the output bytes are assigned as shown in Table 10.
The bus coupler parameter byte is appended to the output bytes of the modules.
Table 8: Example assignment of output bytes (OB)
Bit 7 Bit 6 Bit 5
Byte
OB1 Valve 4 Valve 4 Valve 3
Sol. 12 Sol. 14 Sol. 12
OB2 – – –
OB3 – – Valve 9
Sol. 12
OB4 Valve 13 Valve 13 Valve 12
Sol. 12 Sol. 14 Sol. 12
OB5
OB6 Second pressure regulator byte
OB7 Valve 17 Valve 17 Valve 16
Sol. 12 Sol. 14 Sol. 12
OB8 Valve 21 Valve 21 Valve 20
Sol. 12 Sol. 14 Sol. 12
OB9 – – Valve 24
Sol. 12
OB10 8DO8M8 8DO8M8 8DO8M8
(module (module (module
11) 11) 11)
X2O8 X2O7 X2O6
OB11
1)
Bits marked with "–" are filler bits. They may not be used and are assigned the
value "0".
The input bytes are assigned as shown in Table 11. The diagnostic data are ap-
pended to the input data and are always 8 bytes in length.
Table 9: Example assignment of input bytes (IB)
Bit 7 Bit 6 Bit 5
Byte
IB1
IB2 Second pressure regulator byte
IB3 8DI8M8 8DI8M8 8DI8M8
(module (module (module
9) 9) 9)
X2I8 X2I7 X2I6
IB4 8DI8M8 8DI8M8 8DI8M8
(module (module (module
10) 10) 10)
X2I8 X2I7 X2I6
IB5
IB6
IB7 Diagnostic byte (modules 1 to 8)
IB8 Diagnostic byte (bits 0 to 3: modules 9 to 12, bits 4 to 7 not assigned)
IB9
IB10
IB11
IB12
The length of the process data in the valve zone depends on the in-
stalled valve driver g 6. Structure of the Valve Driver Data. The length
of the process data in the I/O zone depends on the selected I/O mod-
ule (see the system description of the respective I/O modules).

5.5 Setting the Bus Coupler Parameters

The characteristics of the valve system are influenced by the different parameters
that you set in the controller. You can use these parameters to determine the re-
sponses of the bus coupler and the I/O modules.
This section only describes the parameters for the bus coupler. The parameters of
the I/O zone and the pressure regulators are explained in the system description
AVENTICS™ EtherNet/IP | R412018139-BAL-001-AG | English
1)
Bit 4 Bit 3 Bit 2
Valve 3 Valve 2 Valve 2
Sol. 14 Sol. 12 Sol. 14
– Valve 6 Valve 6
Sol. 12 Sol. 14
Valve 9 Valve 8 Valve 8
Sol. 14 Sol. 12 Sol. 14
Valve 12 Valve 11 Valve 11
Sol. 14 Sol. 12 Sol. 14
First pressure regulator byte
Valve 16 Valve 15 Valve 15
Sol. 14 Sol. 12 Sol. 14
Valve 20 Valve 19 Valve 19
Sol. 14 Sol. 12 Sol. 14
Valve 24 Valve 23 Valve 23
Sol. 14 Sol. 12 Sol. 14
8DO8M8 8DO8M8 8DO8M8
(module (module (module
11) 11) 11)
X2O5 X2O4 X2O3
Bus coupler parameter byte
Bit 4 Bit 3 Bit 2
First pressure regulator byte
8DI8M8 8DI8M8 8DI8M8
(module (module (module
9) 9) 9)
X2I5 X2I4 X2I3
8DI8M8 8DI8M8 8DI8M8
(module (module (module
10) 10) 10)
X2I5 X2I4 X2I3
Diagnostic byte (bus coupler)
Diagnostic byte (bus coupler)
Diagnostic byte (not assigned)
Diagnostic byte (not assigned)
Diagnostic byte (not assigned)
Diagnostic byte (not assigned)
of the individual I/O modules or in the operating instructions for the AV-EP pres-
sure regulators. The system description of the bus coupler explains the parame-
ters for the valve driver boards.
The following parameters can be set for the bus coupler:
• Response to an interruption in EtherNet/IP communication
• Response to an error (backplane failure)
• Sequence of the bytes
During cyclical operation, the parameters are set with the help of the parameter
byte, which is appended to the output data.
Bit 1 Bit 0
Bit 0 is not assigned.
Valve 1 Valve 1
Sol. 12 Sol. 14
Valve 5 Valve 5 The response to an EtherNet/IP communication problem is defined in bit 1 of the
parameter byte.
Sol. 12 Sol. 14
• Bit 1 = 0: If the connection is interrupted, the outputs are set to zero.
Valve 7 Valve 7
Sol. 12 Sol. 14
• Bit 1 = 1: If the connection is interrupted, the outputs are maintained in the
current state.
Valve 10 Valve 10
The response to an error in the backplane is defined in bit 2 of the parameter
Sol. 12 Sol. 14
byte.
• Bit 2 = 0: g 5.5.2. Error-response parametersSee error response option 1
• Bit 2 = 1: See error response option 2
Valve 14 Valve 14
Sol. 12 Sol. 14 The byte sequence of modules with 16-bit values is defined in bit 3 of the param-
eter byte (SWAP)
Valve 18 Valve 18
Sol. 12 Sol. 14 • Bit 3 = 0: 16-bit values are sent in big-endian format.
Valve 22 Valve 22 • Bit 3 = 1: 16-bit values are sent in little-endian format.
Sol. 12 Sol. 14
You can also write and read out the parameters during acyclic operation (uncon-
nected messages). However, acyclic writing is only advisable when the module is
8DO8M8 8DO8M8
(module (module
not exchanging cyclical data, since the parameters in cyclical operation are im-
11) 11)
mediately replaced by the cyclically transferred parameters.
X2O2 X2O1
You can write the bus coupler parameters acyclically with the following uncon-
nected message.
Enter the following values in the PLC configuration software in the corre-
u
sponding input field.
Table 10: Writing bus coupler parameters
Field name in the software window
Service code
Bit 1 Bit 0
Class
Instance
Attribute
8DI8M8 8DI8M8

5.5.1 Setting parameters for the modules

(module (module
9) 9)
You can write and read out the parameters of the modules using the settings in
X2I2 X2I1
Table 13. The module parameters are not appended to the user data, they can
only be written acyclically via unconnected messages.
8DI8M8 8DI8M8
(module (module
Note that the entire data length of a module parameter has to be transferred
u
10) 10)
for the parameter to be taken over. The parameter data length for the module
X2I2 X2I1
can be found in the documentation for the respective module.
The query "Parameter lesen" (read parameters) takes a few milliseconds since
this process triggers the internal call "Parameter vom Modul neu einlesen" (read
in parameters from module again). The most recently read-out data is trans-
ferred.
Thus, execute the query "Parameter lesen" (read parameters) twice in 1 s in-
u
tervals to read out the current parameter data from the module.
If you only execute the query "Parameter lesen" once, in the worst case, the pa-
rameters that were read in the last time the device was restarted will be returned.
Table 11: Writing and reading out module parameters
Field name in the software
window
Service code
Class
Instance
Attribute
Parameter data record
Value in input field to write parameter
0x10
0xC7
0x01
0x01
Value in input field to write Value in input field to read
parameter out parameter
0x10 0x0E
0x64 0x64
Module number in hexadeci- Module number in hexadeci-
mal coding mal coding
(e.g. module no. 18 = 0x12)
(e.g. module no. 15 = 0x0F)
0x01 0x02
Volume of module parameter Volume of module parameter
data to be written data to be read
33