EtherNet/IP - Products - Source Stacks
    Industrial Networking
 

EtherNet/IP™ Overview

 

An Application Layer Protocol for Industrial Automation

Page 4 of 5 | first page | « previous page | next page » | last page | home
 

2. 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.


3. 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.

Solutions:

 
EtherNet/IP Solutions Directory
(click [+] to expand the menu)

»Instant EtherNet/IP
»Altivar31 EtherNet/IP
»EtherNet/IP On A Chip
»Instant EtherNet/IP Enabler
»EtherNet/IP PCB Enabler
»ASCII To PLC Gateway
»Core Module
»EtherNet/IP DeviceNet Master Gateway
»EtherNet/IP Modbus RTU Master Gateway
»TCP to ControlLogix PLC Gateway
»Serial to PLC Gateway
»Ethernet/IP Frequently Asked Questions

 


More Information
     
  » I need to Ethernet/IP-enable
My Product
  » I have a Networking Question
  » I want this file in PDF Format
  » I need to Find an Ethernet/IP Product
     
For Your Immediate Needs Call:

John Rinaldi
Networking Project Manager
1-800-249-1612
1-414-453-5100
     
 
Page 4 of 5 | first page | « previous page | next page » | last page | home
top of page
 
By John Rinaldi
Real Time Automation, Inc.
2825 N. Mayfair Rd. Suite 11
Wauwatosa WI 53222

(414) 453-5100 (V)
(414) 453-5125 (F)
www.rtaautomation.com
© Real Time Auomation, Inc. All Rights Reserved. | http://www.rtaautomation.com