Emerson AVENTICS EtherNet/IP AES Serie Description Du Système page 34

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 option 1.
• 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
2 bytes of input data thus has a total of 10 bytes of input data. A valve system
consisting of a bus coupler and a module without input data has a total of 8 bytes
of input data.
The 8 bytes 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 Table 14.
Table 12: Diagnostic data appended to input data
Byte no. Bit no. Meaning
Byte 0 Bit 0 Actuator voltage UA < 21.6 V
Bit 1 Actuator voltage UA < UA-OFF
Bit 2 Electronics power supply UL < 18 V
Bit 3 Electronics power supply UL < 10 V
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.
Bit 1 The backplane of the valve zone issues an
error.
AVENTICS™ EtherNet/IP | R412018139-BAL-001-AG | English
Byte no. Bit no. Meaning
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Diagnostic type and de-
vice
Bus coupler diagnosis
Bus coupler diagnosis
5.6.2 Reading out the bus coupler diagnostic data
The diagnostic data of the bus coupler can be read out as follows:
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
Bit 0 Group diagnosis, module 1
Bit 1 Group diagnosis, module 2
Bit 2 Group diagnosis, module 3
Bit 3 Group diagnosis, module 4
Bit 4 Group diagnosis, module 5
Bit 5 Group diagnosis, module 6
Bit 6 Group diagnosis, module 7
Bit 7 Group diagnosis, module 8
Bit 0 Group diagnosis, module 9
Bit 1 Group diagnosis, module 10
Bit 2 Group diagnosis, module 11
Bit 3 Group diagnosis, module 12
Bit 4 Group diagnosis, module 13
Bit 5 Group diagnosis, module 14
Bit 6 Group diagnosis, module 15
Bit 7 Group diagnosis, module 16
Bit 0 Group diagnosis, module 17
Bit 1 Group diagnosis, module 18
Bit 2 Group diagnosis, module 19
Bit 3 Group diagnosis, module 20
Bit 4 Group diagnosis, module 21
Bit 5 Group diagnosis, module 22
Bit 6 Group diagnosis, module 23
Bit 7 Group diagnosis, module 24
Bit 0 Group diagnosis, module 25
Bit 1 Group diagnosis, module 26
Bit 2 Group diagnosis, module 27
Bit 3 Group diagnosis, module 28
Bit 4 Group diagnosis, module 29
Bit 5 Group diagnosis, module 30
Bit 6 Group diagnosis, module 31
Bit 7 Group diagnosis, module 32
Bit 0 Group diagnosis, module 33
Bit 1 Group diagnosis, module 34
Bit 2 Group diagnosis, module 35
Bit 3 Group diagnosis, module 36
Bit 4 Group diagnosis, module 37
Bit 5 Group diagnosis, module 38
Bit 6 Group diagnosis, module 39
Bit 7 Group diagnosis, module 40
Bit 0 Group diagnosis, module 41
Bit 1 Group diagnosis, module 42
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.
Diagnostic type and de-
vice
Group diagnoses of mod-
ules
Group diagnoses of mod-
ules
Group diagnoses of mod-
ules
Group diagnoses of mod-
ules
Group diagnoses of mod-
ules
Group diagnoses of mod-
ules
34