Emerson AVENTICS - Setting the Bus Coupler Parameters; Setting Parameters for the Modules

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)
1)
Byte
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
OB1 Valve 4
Sol. 12
Valve 4
Sol. 14
Valve 3
Sol. 12
Valve 3
Sol. 14
Valve 2
Sol. 12
Valve 2
Sol. 14
Valve 1
Sol. 12
Valve 1
Sol. 14
OB2 – – – – Valve 6
Sol. 12
Valve 6
Sol. 14
Valve 5
Sol. 12
Valve 5
Sol. 14
OB3 – – Valve 9
Sol. 12
Valve 9
Sol. 14
Valve 8
Sol. 12
Valve 8
Sol. 14
Valve 7
Sol. 12
Valve 7
Sol. 14
OB4 Valve 13
Sol. 12
Valve 13
Sol. 14
Valve 12
Sol. 12
Valve 12
Sol. 14
Valve 11
Sol. 12
Valve 11
Sol. 14
Valve 10
Sol. 12
Valve 10
Sol. 14
OB5 First pressure regulator byte
OB6 Second pressure regulator byte
OB7 Valve 17
Sol. 12
Valve 17
Sol. 14
Valve 16
Sol. 12
Valve 16
Sol. 14
Valve 15
Sol. 12
Valve 15
Sol. 14
Valve 14
Sol. 12
Valve 14
Sol. 14
OB8 Valve 21
Sol. 12
Valve 21
Sol. 14
Valve 20
Sol. 12
Valve 20
Sol. 14
Valve 19
Sol. 12
Valve 19
Sol. 14
Valve 18
Sol. 12
Valve 18
Sol. 14
OB9 – – Valve 24
Sol. 12
Valve 24
Sol. 14
Valve 23
Sol. 12
Valve 23
Sol. 14
Valve 22
Sol. 12
Valve 22
Sol. 14
OB10 8DO8M8
(module
11)
X2O8
8DO8M8
(module
11)
X2O7
8DO8M8
(module
11)
X2O6
8DO8M8
(module
11)
X2O5
8DO8M8
(module
11)
X2O4
8DO8M8
(module
11)
X2O3
8DO8M8
(module
11)
X2O2
8DO8M8
(module
11)
X2O1
OB11 Bus coupler parameter byte
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)
Byte
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
IB1 First pressure regulator byte
IB2 Second pressure regulator byte
IB3 8DI8M8
(module
9)
X2I8
8DI8M8
(module
9)
X2I7
8DI8M8
(module
9)
X2I6
8DI8M8
(module
9)
X2I5
8DI8M8
(module
9)
X2I4
8DI8M8
(module
9)
X2I3
8DI8M8
(module
9)
X2I2
8DI8M8
(module
9)
X2I1
IB4 8DI8M8
(module
10)
X2I8
8DI8M8
(module
10)
X2I7
8DI8M8
(module
10)
X2I6
8DI8M8
(module
10)
X2I5
8DI8M8
(module
10)
X2I4
8DI8M8
(module
10)
X2I3
8DI8M8
(module
10)
X2I2
8DI8M8
(module
10)
X2I1
IB5 Diagnostic byte (bus coupler)
IB6 Diagnostic byte (bus coupler)
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 Diagnostic byte (not assigned)
IB10 Diagnostic byte (not assigned)
IB11 Diagnostic byte (not assigned)
IB12 Diagnostic byte (not assigned)
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
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0 is not assigned.
The response to an EtherNet/IP communication problem is defined in bit1 of the
parameter byte.
• Bit 1 = 0: If the connection is interrupted, the outputs are set to zero.
• Bit 1 = 1: If the connection is interrupted, the outputs are maintained in the
current state.
The response to an error in the backplane is defined in bit2 of the parameter
byte.
• Bit 2 = 0: g5.5.2.Error-response parametersSee error response option1
• Bit 2 = 1: See error response option2
The byte sequence of modules with 16-bit values is defined in bit3 of the param-
eter byte (SWAP)
• Bit3 = 0: 16-bit values are sent in big-endian format.
• Bit3 = 1: 16-bit values are sent in little-endian format.
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
not exchanging cyclical data, since the parameters in cyclical operation are im-
mediately replaced by the cyclically transferred parameters.
You can write the bus coupler parameters acyclically with the following uncon-
nected message.
u Enter the following values in the PLC configuration software in the corre-
sponding input field.
Table10: Writing bus coupler parameters
Field name in the software window Value in input field to write parameter
Service code 0x10
Class 0xC7
Instance 0x01
Attribute 0x01
5.5.1 Setting parameters for the modules
You can write and read out the parameters of the modules using the settings in
Table13. The module parameters are not appended to the user data, they can
only be written acyclically via unconnected messages.
u Note that the entire data length of a module parameter has to be transferred
for the parameter to be taken over. The parameter data length for the module
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.
u Thus, execute the query “Parameter lesen” (read parameters) twice in 1s in-
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
Value in input field to write
parameter
Value in input field to read
out parameter
Service code 0x10 0x0E
Class 0x64 0x64
Instance Module number in hexadeci-
mal coding
(e.g. module no.15= 0x0F)
Module number in hexadeci-
mal coding
(e.g. module no. 18 = 0x12)
Attribute 0x01 0x02
Parameter data record Volume of module parameter
data to be written
Volume of module parameter
data to be read
AVENTICS™ EtherNet/IP | R412018139-BAL-001-AG | English 33