Rockwell Automation 2098 CompactLogix Indexing Motion Accelerator Toolkit Quick Start - Manual (Page 58)

58 Publication IASIMP-QS011B-EN-P — January 2009
Chapter 5 Motion Logix Integration
3. Scroll to the
bottom of the
tag editor
and locate
the tags created by the Tag Generator tool. The name of the tags will start with the name you
gave the DeviceNet scanner, ‘Scanner’ in our case.
4. You will need to associate
these tags to the existing axis
logic provided in the Logix
application file. In the ‘Alias For’ column next to the Scanner_N01_POL_I tag, click inside the
box to enable the tag browser.
5. Open the tag browser by clicking the
arrow.
6. The axes of motion provided
in the RSLogix 5000 sample file
are named ‘AXIS_01’
(’AXIS_02’ for the 2-axis
version and so on). Expand the
AXIS_01 entry and locate the Status tag. Double-click it to select it and close the tag browser.
This links the Status of the Ultra3000 drive at DeviceNet node 01 to the AXIS_01 programming
logic and controller tag in the RSLogix 5000 sample file.
7. Similarly, alias the
Scanner_N01_POL_O tag
to the ‘Commands’ tag of
AXIS_01.
8. If you have more than one servo drive, repeat this process to alias the remaining nodes to the
axis programming. Be sure to alias the ‘I’ input data to the Status tag and the ‘O’ output data
to the Commands tag for each device.
TIP
•
The ‘Nxx’ indicates the DeviceNet node address assigned to each component.
•
The ‘I’ or ‘O’ indicates whether the data is an Input or an Output in reference to
the DeviceNet scanner module.
•
Scanner Inputs are the status coming back from the DeviceNet components.
•
Scanner Outputs are the commands being issued to the DeviceNet components.