Configuring The Bus Coupler In The Fieldbus System; Configuring The Valve System; Module Sequence - Aventics AES Serie Descripción De Sistema

Ocultar thumbs Ver también para AES Serie:
Tabla de contenido

Publicidad

Idiomas disponibles
  • MX

Idiomas disponibles

  • MEXICANO, página 255
80
AVENTICS | Bus Coupler AES/Valve Driver AV, EtherNet/IP | R412018139–BAL–001–AF
PLC Configuration of the Valve System
Operation without EDS file
The bus coupler's Ethernet/IP cycle time can be set in a range from 2 ms to 9999 ms.
Set the cycle time to the desired value.
You can also operate the system without an EDS file.
For this, calculate the incoming and outgoing data lengths as described in Table 9 on page 82.
Enter the following values in the PLC configuration program for a class 1 connection:
Connection:
Master → slave: point-to-point
Slave → master: multicast
Connection points:
Master → slave: "101" and as data length "output data length"
Slave → master: "102" and as data length "input data length"
Configuration: "1" and as data length "0"
5.3

Configuring the bus coupler in the fieldbus system

Before you can configure the individual components of the valve system, you need to assign an
IP address to the bus coupler using your PLC configuration software. In most cases, a DHCP server
assigns the address during commissioning and subsequently permanently assigns it to the device.
1. Assign the bus coupler a unique IP address using the configuration tool (see section 9.3
"Assigning IP address and subnet mask" on page 96).
2. Configure the bus coupler as a slave module.
5.4

Configuring the valve system

5.4.1

Module sequence

The input and output data used by the modules to communicate with the controller consist of a byte
string. The lengths of the valve system input and output data are calculated from the number of
modules and the data width of the individual module. The data is only counted in bytes. If a module
has less than 1 byte of input or output data, the left-over bits are "stuffed" to the byte boundary using
non-information bits.
Example: A valve driver board, 2x, with 4 bits of user data occupies 1 byte in the byte string, since
the remaining 4 bits are stuffed with non-information bits. The data of the next module therefore
starts after a byte boundary.
In the example (see Fig. 3), the modules are numbered to the right of the bus coupler (AES-D-BC-EIP)
in the valve zone, starting with the first valve driver board (module 1) and continuing to the last valve
driver board on the right end of the valve unit (module 9).
Bridge cards are not taken into account. Supply boards and UA-OFF monitoring boards occupy one
module (see module 7 in Fig. 3). The supply boards and UA-OFF monitoring boards do not add any
bytes to the input and output data. However, they are also counted, since they have diagnostic data,
which is transferred at the corresponding module position. The data length for pressure regulators
can be found in the operating instructions for AV-EP pressure regulators (R414007537).
The numbering is continued in the I/O zone (module 10 to module 12 in Fig. 3). There, numbering is
continued starting from the bus coupler to the left end.
The bus coupler's parameter data is annexed to the output data in the byte chain. The bit
assignments of the bus coupler are described in "5.5 Setting the bus coupler parameters" on
page 84.
The diagnostic data of the valve system is 8 bytes in length and is appended to the input data.
The structure of this diagnostic data is described in Table 14.

Publicidad

Tabla de contenido
loading

Este manual también es adecuado para:

Aes-d-bc-eip

Tabla de contenido