Behavior – Rockwell Automation 294D ArmorStart LT Distributed Motor Controller DeviceNet Version - User Manual User Manual

Page 242

Advertising
background image

242

Rockwell Automation Publication 290D-UM001A-EN-P - June 2012

Appendix B

CIP Information

101) MAC ID -

This attribute is used so that MAC ID can be entered for a

consuming instance instead of Zone Connection ID in a EDS file. When this
attribute is changed, the Zone Connection ID attribute value is updated to
reflect the new Connection ID.

103) Point Mask -

This attribute is used so that a mask value of type DWORD

can be used in an EDS file parameter for the Zone Point Mask since arrays are not
supported in EDS parameters. When this attribute is changed, the Zone Point
Mask attribute value is updated to reflect the new mask value.

114) Zone Control -

This attribute is used to choose the IO Connection type

that is consumed, whether security is enabled and whether the consumed data is
fragmented. See parameters 134-137 for the bit enumerations.

116) Analog Mask -

This attribute is used so that a mask value of type WORD

can be used in an EDS file parameter for the Zone Analog Mask since arrays are
not supported in EDS parameters. When this attribute is changed, the Zone
Analog Mask attribute value is updated to reflect the new mask value.

The following common services will be implemented for the ZIP Object.

Behavior

The ZIP object provides a means for devices on a network to share I/O data
directly without hard wiring them together, with, or without the use of a network
scanner. A single ZIP enabled device can consume data directly from multiple
devices on a network. A ZIP enabled device can also auto-allocate and configure
producing I/O connections. In initial DeviceNet ZIP implementations, devices
will be capable of auto-allocating and configuring unacknowledged COS
connections, but the object definition does not preclude the use of other types of
I/O connections for data production.

Instances of the ZIP object represent connection endpoints on a network. Two
types of ZIP object instances are defined:

ZIP Producers

ZIP Consumers

Multiple instances of each instance type can exist, but in initial DeviceNet
implementations, a single ZIP Producer will be used to allow for the automatic
allocation and configuration of an unacknowledged COS connection. The
automatic allocation of producing I/O connections only occurs if the Auto Run
ZIP attribute for the ZIP Producer is enabled.

Service Code

Implemented for:

Service Name

Class Instance

0x0E

No

Yes

Get_Attribute_Single

0x10

No

Yes

Set_Attribute_Single

Advertising