Extended Diagnostic Data Of The I/O Modules; Transferring The Configuration To The Controller; Structure Of The Valve Driver Data; Process Data - Emerson AES Serie Systembeschreibung

Object Sub-ob- Contents
no. ject no.
1 Bus coupler diagnostic bytes
(string)
(Length 2 bytes)
For the description of the diagnostic data for the valve zone, see sec-
tions g 6.2 Diagnostic Data
tion of the diagnostic data for AV-EP pressure regulators can be found
in the operating instructions for AV-EP pressure regulators. The diag-
nostic data for the I/O zone is described in the system descriptions of
the individual I/O modules.

5.7 Extended Diagnostic Data of the I/O Modules

In addition to group diagnosis, some I/O modules can send extended diagnostic
data with a length of up to 4 bytes to the controller. The total data length can
thus be up to 5 bytes:
Byte 1 of the diagnostic data contains the group diagnosis information:
• Byte 1 = 0x00: No error has occurred.
• Byte 1 = 0x80: An error has occurred.
Bytes 2 to 5 contain the extended diagnostic data of the I/O modules. The ex-
tended diagnostic data can only be accessed acyclically with SDOs.
You can read out the diagnostic data of the I/O modules byte by byte or as a
string.
To read out the diagnostic data of the I/O modules byte by byte:
Enter the following object data in the "Read SDO" field of the PLC configura-
u
tion software in object 0x23nn.
Table 15: Reading out the diagnostic data of the I/O modules byte by byte with
object 0x23nn
Object Sub-ob- Contents
no. ject no.
2
0x23nn 0 Highest sub-object no.
)
1 Group diagnosis
2 Extended diagnosis, byte 1
(optional)
3 Extended diagnosis, byte 2
(optional)
4 Extended diagnosis, byte 3
(optional)
5 Extended diagnosis, byte 4
(optional)
1)
Bytes that are not used receive the value "0".
2)
nn = module no. 00 to 2A (hexadecimal), corresponds to 00 to 42 (decimal)
To read out the diagnostic data of the I/O modules as a string:
Enter the following object data in the "Read SDO" field of the PLC configura-
u
tion software in object 0x33nn.
Table 16: Reading out the diagnostic data of the I/O modules as a string with ob-
ject 0x33nn
Object Sub-ob- Contents
no. ject no.
1
0x33nn 0 Highest sub-object no.
)
1 Diagnosis of the module
(string)
Length between 1 and
5 bytes depending on mod-
ule type
1)
When a sub-object without a diagnostic byte is accessed, the value 0 is re-
turned.
Acyclic access to the diagnostic data is performed identically for all modules. For
a description using valve driver boards as an example, see
nostic data of the valve drivers via

5.8 Transferring the Configuration to the Controller

Data may be transferred to the controller once the system is completely and cor-
rectly configured.
1. Check whether the number of objects that are mapped to the input and out-
put PDO match those of the valve system.
2. Establish a connection to the controller.
AVENTICS™ Ethernet POWERLINK | R412018143-BAL-001-AH | English
Default value
and g 7.2 Diagnostic Data. The descrip-
1)
Default value
5
The minimum length is 1 byte (group di-
agnosis)
Additional bytes possible depending on
module type.
Default value
1
g 6.2.2 Acyclic diag-
SDO.
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 and bytes 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 four bytes. 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. Only the least
significant byte is used for these three modules; the remaining three bytes are
not used on any of the three modules.
The figure below shows how valve positions are assigned on 2x, 3x, and 4x valve
driver boards. See g Fig. 8.
22
20
    
Fig. 8: 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
The symbols for the valve zone components are explained in
g 12.2 Valve Zone.
The assignment of valve solenoid coils to the bits of the least significant byte is as
follows:
1)
Table 17: Valve driver board, 2x
Bit 7 Bit 6
Least significant
output byte
Valve designa- – –
tion
Solenoid desig- – –
nation
1)
nn = module no. 00 to 2A (hexadecimal), corresponds to 00 to 42 (decimal)
1)
Table 18: Valve driver board, 3x
Bit 7 Bit 6
Least significant
output byte
Valve designa- – –
tion
Solenoid desig- – –
nation
1)
nn = module no. 00 to 2A (hexadecimal), corresponds to 00 to 42 (decimal)
Table 19: Valve driver board, 4x
Bit 7 Bit 6
Least significant
output byte
Valve designa- Valve 4 Valve 4 Valve 3 Valve 3 Valve 2 Valve 2 Valve 1 Valve 1
tion
Solenoid desig- Sol. 12 Sol. 14
nation
WARNING
23 24
21
   
(2) Valve position 2
(4) Valve position 4
21 Base plate, 3x
23 Valve driver board, 3x
Bit 5 Bit 4 Bit 3 Bit 2
– – Valve 2 Valve 2 Valve 1 Valve 1
– – Sol. 12 Sol. 14
Bit 5 Bit 4 Bit 3 Bit 2
Valve 3 Valve 3 Valve 2 Valve 2 Valve 1 Valve 1
Sol. 12 Sol. 14 Sol. 12 Sol. 14
Bit 5 Bit 4 Bit 3 Bit 2
Sol. 12 Sol. 14 Sol. 12 Sol. 14
20
Bit 1 Bit 0
Sol. 12 Sol. 14
Bit 1 Bit 0
Sol. 12 Sol. 14
Bit 1 Bit 0
Sol. 12 Sol. 14
40