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 Serie Systembeschreibung

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

Incorrect data assignment!
Danger caused by uncontrolled movement of the system.
Always set the unused bits to the value "0".
u
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.
Fig. 4 shows how valve positions are assigned on 2x, 3x, and 4x valve driver
boards:
AVENTICS™ AES PROFINET IO | R412018140-BAL-001-AH | English
WARNING
22
20
    
Fig. 4: Valve position assignment
1 Valve position 1
3 Valve position 3
20 Base plate, 2x
22 Valve driver board, 2x
24 Valve driver board, 4x
For an explanation of the symbols for the valve zone components (see
"Valve zone").
The assignment of valve solenoid coils to bits is as follows:
1)
Table 10: Valve driver board, 2x
Bit 7 Bit 6 Bit 5
Output
byte
Valve desig- – –
nation
Solenoid – –
designation
1)
Bits that are marked with a "–" may not be used and are assigned the value "0".
1)
Table 11: Valve driver board, 3x
Bit 7 Bit 6 Bit 5
Output
byte
Valve desig- – – Valve 3
nation
Solenoid – – Sol. 12
designation
1)
Bits that are marked with a "–" may not be used and are assigned the value "0".
Table 12: Valve driver board, 4x
Bit 7 Bit 6 Bit 5
Output
byte
Valve desig- Valve 4 Valve 4 Valve 3
nation
Solenoid Sol. 12 Sol. 14 Sol. 12
designation
Tables 10-12 refer to double solenoid valves. With a single solenoid
valve, only solenoid 14 is used (bits 0, 2, 4, and 6).

6.2 Diagnostic data

If an error occurs in a valve zone module, the valve driver sends a manufacturer-
specific diagnostic message to the bus coupler. It shows the number of the slot
where the error occurred. The diagnosis is structured as follows:
In the User Structure Identifier (USI) (first 16-bit value), the slot number is coded
and 0x0040 is sent in the diagnostic data (second 16-bit value). This corresponds
to a group diagnosis.
If several diagnoses are available, for example if a short circuit is detected in sev-
eral modules, each diagnosis is set and also reset individually.

6.3 Parameter data

The valve driver board does not contain any parameters.
23 24
21
   
2 Valve position 2
4 Valve position 4
21 Base plate, 3x
23 Valve driver board, 3x
Bit 4 Bit 3 Bit 2
– – Valve 2 Valve 2
– – Sol. 12 Sol. 14
Bit 4 Bit 3 Bit 2
Valve 3 Valve 2 Valve 2
Sol. 14 Sol. 12 Sol. 14
Bit 4 Bit 3 Bit 2
Valve 3 Valve 2 Valve 2
Sol. 14 Sol. 12 Sol. 14
20
Bit 1 Bit 0
Valve 1 Valve 1
Sol. 12 Sol. 14
Bit 1 Bit 0
Valve 1 Valve 1
Sol. 12 Sol. 14
Bit 1 Bit 0
Valve 1 Valve 1
Sol. 12 Sol. 14
33