Table of Contents
Advertisement
Installation and User Guide
DS6x00 EtherNet/IP Scanner
Rev 1.02
APPLICATION OBJECTS
Application objects are the objects that define the data encapsulated by the device. These objects
are specific to the device type and function. For example, a Motor object on a Drive System has
attributes describing the frequency, current rating and motor size. An Analog Input object on an
I/O device has attributes that define the type, resolution and current value for the analog input.
These application layer objects are predefined for a large number of common device types. All
CIP devices with the same device type (Drive Systems, Motion Control, Valve Transducer...etc)
must contain the identical series of application objects. The series of application objects for a
particular device type is known as the device profile. A large number of profiles for many device
types have been defined. Supporting a device profile allows a user to easily understand and
switch from a vendor of one device type to another vendor with that same device type.
A device vendor can also group Application Layer Objects into assembly objects. These super
objects contain attributes of one or more Application Layer Objects. Assembly objects form a
convenient package for transporting data between devices. For example, a vendor of a
Temperature Controller with multiple temperature loops may define assemblies for each of the
temperature loops and an assembly with data from both temperature loops. The user can than
pick the assembly that is most suited for the application and how often to access each assembly.
For example, one temperature assembly may be configured to report every time it changes state
while the second may be configured to report every one-second regardless of a change in state.
Assemblies are usually predefined by the vendor but CIP also defines a mechanism in which the
user can dynamically create an assembly from application layer object attributes.
VENDOR SPECIFIC OBJECTS
Objects not found in the profile for a device class are termed Vendor Specific. These objects are
included by the vendor as additional features of the device. The CIP protocol provides access to
these vendor extension objects in exactly the same method as either application or required
objects. This data is strictly of the vendors choosing and is organized in whatever method makes
sense to the device vendor.
In addition to specifying how device data is represented to the network, the CIP protocol
specifies a number of different ways in which that data can be accessed such as cyclic, polled
and change-of-state.
ADVANTAGES TO EIP
The advantages of the CIP protocol layer over EIP are numerous. The consistent device access
means that a single configuration tool can configure CIP devices on different networks from a
single access point without using vendor specific software. The classification of all devices as
objects decreases the training and startup required when new devices are brought online. EIP
provides improved response time and greater data throughput than DeviceNet and ControlNet.
EIP links devices from the sensor bus level to the control level to the enterprise level with a
consistent application layer interface.
© 2004 Datalogic S.p.A. – All Right Reserved
Page 8 of 54
Advertisement
Table of Contents
