beautypg.com

Discrete output point object special requirements – Rockwell Automation 294E ArmorStart LT EtherNet/IP Version - User Manual User Manual

Page 207

background image

Rockwell Automation Publication 290E-UM001B-EN-P - June 2012

207

CIP Information

Appendix B

Eight instances of the Discrete Output Point Object are supported for DOL/
Reverser (Bulletin 290E/291E) units. Ten instances are supported for Drive
(Bulletin 294E) units. The following table summarizes the DOP (Bulletin 290E/
291E) instances:

All instances contain the following attribute:

The following common services will be implemented for the Discrete Output
Point Object:

Discrete Output Point Object Special Requirements

There are many sources that can affect an output point's value: an I/O message,
an explicit message, local logic, network fault and idle conditions, and protection
fault conditions. An output point must know how to select which source of data
to use to drive its value attribute.

Instance Name

Alternate

Mapping

Description

1

Run Fwd Output

0029-01-03

Run Forward output.

2

Run Rev Output

0029-01-04

Run Reverse output.

3

User Output A

None

These are the six ArmorStart LT user outputs for all starter types. Their fault/
idle behavior is defined in DOP Instance 3.

4

User Output B

None

5

User Output C

None

6

User Output D

None

7

User Output E

None

8

User Output F

None

9

Drive Jog Fwd

None

This instances exists for Inverter (Bulletin 294E) units only.

10

Drive Jog Rev

None

Attribute ID

Access Rule

Name

Data Type

Value

3

Get

Value

BOOL

0 = OFF, 1 = ON

Service Code

Implemented for:

Service Name

Class Instance

0x0E

Yes

Yes

Get_Attribute_Single

0x10

No

Yes

Set_Attribute_Single