Burkert Type 8640 - Manual (Page 91)

91
Configurationandparameter
settingsforEtherNet/IP
17. CONFIGURATION AND PARAMETER
SETTINGS FOR ETHERNET/IP
The data exchange between the EtherNet/IP master and the valve terminal is object-oriented. Each node in the
network is represented as a collection of objects.
The Assembly object defines the object assembly for data transfer. The Assembly object can be used to map
data (such as I/O data) into blocks and transmit it via a single message connection. This mapping means fewer
network access operations are needed.
A distinction is made between input and output assemblies. An input assembly reads data from the application
over the network and produces data on the network.
An output assembly writes data to the application over the network and consumes data from the network.
Various assembly instances are preprogrammed in the field bus coupler/controller (static assembly). After power-
up the assembly object maps data from the process image. As soon as a connection has been made, the master
is able to address the data with "Class", "Instance" and "Attribute" and access it, and read and/or write it via I/O
connections.
The data mapping depends on the selected assembly instance of the static assembly.
17.1. Addressing
The IP address is assigned – as usual for Ethernet IP – via a DHCP server. If no assignment occurs within
1 minute via DHCP, the device uses the Fallback IP address 192.168.0.100.
17.2. EDS file
The Electronic Data Sheets (EDS) file contains the identifying data of the field bus coupler/controller and details
of its communications capabilities.
The EDS file needed for EtherNet/IP operation is installed from the project configuration software.
Downloading the EDS file
You will find the EDS file on the Internet, Type 8640 (Search by Type: 8640), at: www.buerkert.com
For information on installing the EDS file refer to your configuration software documentation.
17.3. Object model
For network communications EtherNet/IP uses an object model in which all the functions and data of a device are
described. Each node in the network is represented as a collection of objects.
The object model includes terms which are defined as follows:
Object:
An object is an abstract representation of individual linked components within a device. It is identified by its data
or attributes, by its externally provided functions or services, and by its defined behavior.
Class:
A class describes a series of objects which all represent the same kind of system component. A class is a gener-
alization of an object. All objects in a class are identical in terms of form and behavior, though they may comprise
differing attribute values.
english
Type 8640