
The parameters and configuration data are not saved locally by the bus
coupler. They must be sent from the PLC to the bus coupler and the in-
stalled modules on startup.
5.5.2 Error-response parameters
Response to an interruption in EtherNet/IP communication
This parameter describes the response of the bus coupler in the absence of Ether-
Net/IP communication. You can set the following responses:
• Switch off all outputs (bit 1 of the parameter byte = 0)
• Maintain all outputs (bit 1 of the parameter byte = 1)
Response to a backplane malfunction
This parameter describes the response of the bus coupler in the event of a back-
plane malfunction. You can set the following responses:
Option 1 (bit 2 of the parameter byte = 0):
• If there is a temporary backplane malfunction (triggered, e.g., by a spike in
the power supply), the IO/DIAG LED flashes red and the bus coupler sends a
warning to the controller. As soon as the communication via the backplane is
reinstated, the bus coupler returns to normal mode and the warnings are can-
celed.
• In the event of a sustained backplane malfunction (e.g. due to the removal of
an end plate), the IO/DIAG LED flashes red and the bus coupler sends an error
message to the controller. The bus coupler simultaneously resets all valves
and outputs. The bus coupler tries to re-initialize the system. It sends the di-
agnostic message that the backplane is attempting re-initialization.
– If the initialization is successful, the bus coupler resumes its normal opera-
tion. The error message is canceled and the IO/DIAG LED is illuminated in
green.
– If the initialization is not successful (e.g. due to the connection of new
modules to the backplane or a defective backplane), the bus coupler con-
tinues to send the diagnostic message to the controller that the backplane
is attempting re-initialization, and the initialization is restarted. LED IO/
DIAG continues to flash red.
Option 2 (bit 2 of the parameter byte = 1)
• For temporary backplane malfunctions, the response is identical to option1.
• In the event of a sustained backplane malfunction, the bus coupler sends an
error message to the controller and the IO/DIAG LED flashes red. The bus cou-
pler simultaneously resets all valves and outputs. An initialization of the sys-
tem is not started. The bus coupler must be restarted manually (power reset)
in order to return it to normal mode.
5.6 Bus Coupler Diagnostic Data
5.6.1 Structure of the diagnostic data
The bus coupler sends 8 bytes of diagnostic data which is appended to the mod-
ule input data. A valve system consisting of a bus coupler and a module with
2bytes of input data thus has a total of 10bytes of input data. A valve system
consisting of a bus coupler and a module without input data has a total of 8bytes
of input data.
The 8bytes of diagnostic data contain
• 2 bytes of diagnostic data for the bus coupler and
• 6 bytes of group diagnostic data for the modules.
The diagnostic data is organized as shown in Table14.
Table12: Diagnostic data appended to input data
Byte no. Bit no. Meaning Diagnostic type and de-
vice
Byte 0 Bit 0 Actuator voltage UA < 21.6 V Bus coupler diagnosis
Bit 1 Actuator voltage UA < UA-OFF
Bit 2 Electronics power supply UL<18V
Bit 3 Electronics power supply UL<10V
Bit 4 Hardware error
Bit 5 Reserved
Bit 6 Reserved
Bit 7 Reserved
Byte 1 Bit 0 The backplane of the valve zone issues a
warning.
Bus coupler diagnosis
Bit 1 The backplane of the valve zone issues an
error.
Byte no. Bit no. Meaning Diagnostic type and de-
vice
Bit 2 The backplane of the valve zone attempts a
re-initialization.
Bit 3 Reserved
Bit 4 The backplane of the I/O zone issues a
warning.
Bit 5 The backplane of the I/O zone issues an er-
ror.
Bit 6 The backplane of the I/O zone attempts a
re-initialization.
Bit 7 Reserved
Byte 2 Bit 0 Group diagnosis, module1 Group diagnoses of mod-
ules
Bit 1 Group diagnosis, module2
Bit 2 Group diagnosis, module3
Bit 3 Group diagnosis, module4
Bit 4 Group diagnosis, module5
Bit 5 Group diagnosis, module6
Bit 6 Group diagnosis, module7
Bit 7 Group diagnosis, module8
Byte 3 Bit 0 Group diagnosis, module9 Group diagnoses of mod-
ules
Bit 1 Group diagnosis, module10
Bit 2 Group diagnosis, module11
Bit 3 Group diagnosis, module12
Bit 4 Group diagnosis, module13
Bit 5 Group diagnosis, module14
Bit 6 Group diagnosis, module15
Bit 7 Group diagnosis, module16
Byte 4 Bit 0 Group diagnosis, module17 Group diagnoses of mod-
ules
Bit 1 Group diagnosis, module18
Bit 2 Group diagnosis, module19
Bit 3 Group diagnosis, module20
Bit 4 Group diagnosis, module21
Bit 5 Group diagnosis, module22
Bit 6 Group diagnosis, module23
Bit 7 Group diagnosis, module24
Byte 5 Bit 0 Group diagnosis, module25 Group diagnoses of mod-
ules
Bit 1 Group diagnosis, module26
Bit 2 Group diagnosis, module27
Bit 3 Group diagnosis, module28
Bit 4 Group diagnosis, module29
Bit 5 Group diagnosis, module30
Bit 6 Group diagnosis, module31
Bit 7 Group diagnosis, module32
Byte 6 Bit 0 Group diagnosis, module33 Group diagnoses of mod-
ules
Bit 1 Group diagnosis, module34
Bit 2 Group diagnosis, module35
Bit 3 Group diagnosis, module36
Bit 4 Group diagnosis, module37
Bit 5 Group diagnosis, module38
Bit 6 Group diagnosis, module39
Bit 7 Group diagnosis, module40
Byte 7 Bit 0 Group diagnosis, module41 Group diagnoses of mod-
ules
Bit 1 Group diagnosis, module42
Bit 2 Reserved
Bit 3 Reserved
Bit 4 Reserved
Bit 5 Reserved
Bit 6 Reserved
Bit 7 Reserved
The group diagnostic data of the modules can also be accessed acycli-
cally.
5.6.2 Reading out the bus coupler diagnostic data
The diagnostic data of the bus coupler can be read out as follows:
AVENTICS™ EtherNet/IP | R412018139-BAL-001-AG | English 34