Error-Response Parameters; Parameter For The Sequence Of The Bytes In The Data Word; Transferring The Configuration To The Controller; Structure Of The Valve Driver Data - Emerson AVENTICS AES PROFINET IO Serie Systembeschreibung

If you deactivate sending diagnostic messages via the parameters
when a diagnostic message is present, the slave must be restarted
(power reset) in order to reset the diagnostic message.
If you activate sending diagnostic messages via the parameters when
a diagnostic message is present, this diagnostic message will not be
sent to the controller. It will only be sent after a restart (power reset) of
the slave or if the diagnostic message appears again.
The bus coupler diagnostic message is structured as follows:
Each diagnosis that is reported consists of two 16-bit numbers. The first number
defines the diagnostic group (e.g. bus coupler or module number) and the sec-
ond number the reason for the diagnosis (e.g. actuator voltage < 21.6 V or group
diagnosis).
The diagnostic values are linked via the GSDML file to text messages that can be
displayed.
A separate diagnostic message is generated for each error, so that only one value
has to be transferred for the User Structure Identifier (USI) and one value for the
diagnostic data.
Table 9: Manufacturer-specific diagnosis
User Structure Identifier
(USI), 16 bits
1)
1-42 Module number 64
63 Bus coupler 1
2
3
4
5
9
10
11
13
14
15
64 Configuration error 64
65-1 Module configuration 1
2)
06 information
2
3
1)
1 = module 1, 2 = module 2, 3 = module 3, ...
2)
65 (0x41) = module 1, 66 (0x42) = module 2, 67 (0x43) = module 3, ...
Example:
Module 5 has an error.
User Structure Identifier (USI)
5
The power supply for the electronics has fallen below 18 V.
User Structure Identifier (USI)
63
If both errors occur at the same time, two error telegrams will be sent.
Telegram number User Structure Identifier (USI)
1st telegram
2nd telegram
If both the electronics and the actuator voltage fall below 18 V or 21.6 V, two er-
ror telegrams will be sent.
Telegram number User Structure Identifier (USI)
1st telegram
2nd telegram
For a description of the diagnostic data for the valve zone, see section
g 6. Structure of the Valve Driver Data. The diagnostic data for the I/
O zone is described in the system descriptions of the individual I/
O modules.
AVENTICS™ AES PROFINET IO | R412018140-BAL-001-AI | English
Diagnostic data (data), 16 bits
Group diagnosis
Actuator voltage UA < 21.6 V (UA-ON)
Actuator voltage UA < UA-OFF
Electronics power supply UL < 18 V
Electronics power supply UL < 10 V
Hardware error
The backplane of the valve zone outputs a warning.
The backplane of the valve zone outputs an error.
The backplane of the valve zone attempts a re-initial-
ization.
The backplane of the I/O zone outputs a warning.
The backplane of the I/O zone outputs an error.
The backplane of the I/O zone attempts a re-initializa-
tion.
The configuration for the master does not match the
configuration for the slave.
The connected module is not configured.
The configured module is not available.
A module different than the configured one has been
connected.
Diagnostic data (data)
64
Diagnostic data (data)
3
Diagnostic data (data)
5 64
63
Diagnostic data (data)
63
63

5.5.3 Error-response parameters

Response to an interruption in PROFINET IO communication
This parameter describes the response of the bus coupler in the absence of
PROFINET IO communication. You can set the following responses:
• Switch off all outputs (presetting)
• Maintain all outputs
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 (default setting):
• 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.
– 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 sends
the error message "Backplane initialization problem" to the controller and
the initialization is restarted. LED IO/DIAG continues to flash red.
Option 2
• 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.5.4 Parameter for the sequence of the bytes in the data word

This parameter determines the byte sequence for modules with 16-bit values.
To modify the sequence of the bytes in the data word, you must change the pa-
rameter.
• Big-endian (default setting) = 16-bit values are sent in big-endian format.
• Little endian = 16-bit values are sent in little-endian format.

5.6 Transferring the configuration to the controller

Data may be transferred to the controller once the system is completely and cor-
rectly configured.
1. Make sure that the controller parameter settings are compatible with those of
the valve system.
2. Establish a connection to the controller.
3. Transfer the valve system data to the controller. The precise process depends
on the PLC configuration program. Observe the respective documentation.

6 Structure of the Valve Driver Data

6.1 Process data

3
Incorrect data assignment!
Danger caused by uncontrolled movement of the system.
Always set the unused bits to the value "0".
u
3
1
The valve driver board receives output data from the controller with nominal val-
ues for the position of the valve solenoid coils. The valve driver translates this
data into the voltage required to actuate the valves. The length of the output
data is eight bits. Of these, 4 bits are used with a 2x valve driver board, 6 bits with
a 3x valve driver board, and 8 bits with a 4x valve driver board.
The figure below shows how valve positions are assigned on 2x, 3x, and 4x valve
driver boards.
WARNING
33