Datalogic PowerScan PBT9500 Software Reference Manual

Also see for PowerScan PBT9500: Quick reference guide Product reference guide Product reference guide Product reference guide Product reference guide

Datalogic PowerScan PBT9500 Software Reference Manual Manual pdf 33 page image

CIP OVERVIEWEthernet Software Reference Guide 29CIP OVERVIEWThe Communications and Information Protocol (CIP) is a communicationsprotocol for transferring automation data between two devices. In the CIPProtocol, every network device represents itself as a series of objects.Each object is simply a grouping of the related data values in a device.For example, every CIP device is required to make an Identity objectavailable to the network. The identity object contains related identitydata values called attributes. Attributes for the identity object include thevendor ID, date of manufacture, device serial number and other identitydata. CIP does not specify at all how this object data is implemented, onlywhat data values or attributes must be supported and that these attri-butes must be available to other CIP devices.The Identity object is an example of a required object. There are threetypes of objects defined by the CIP protocol:REQUIRED OBJECTSRequired objects are required by the specification to be included in everyCIP device. These objects include the Identity object, a Message Routerobject and a Network object.The identity object contains related identity data values called attributes.Attributes for the identity object include the vendor ID, date of manufac-turer, device serial number and other identity data.A Network object contains the physical connection data for the object.For a CIP device on DeviceNet the network object contains the MacID andother data describing the interface to the CAN network. For EIP devices,the network object contains the IP address and other data describing theinterface to the Ethernet port on the device.APPLICATION OBJECTSApplication objects are the objects that define the data encapsulated bythe device. These objects are specific to the device type and function. Forexample, a Motor object on a Drive System has attributes describing thefrequency, current rating and motor size. An Analog Input object on an I/O device has attributes that define the type, resolution and current valuefor the analog input.These application layer objects are predefined for a large number ofcommon device types. All CIP devices with the same device type (DriveSystems, Motion Control, Valve Transducer…etc.) must contain the iden-tical series of application objects. The series of application objects for aparticular device type is known as the device profile. A large number ofprofiles for many device types have been defined. Supporting a deviceprofile allows a user to easily understand and switch from a vendor ofone device type to another vendor with that same device type.A device vendor can also group Application Layer Objects into assemblyobjects. These super objects contain attributes of one or more Applica-tion Layer Objects. Assembly objects form a convenient package fortransporting data between devices. For example, a vendor of a Tempera-ture Controller with multiple temperature loops may define assembliesfor each of the temperature loops and an assembly with data from bothtemperature loops. The user can than pick the assembly that is mostsuited for the application and how often to access each assembly.