Rockwell Automation 1336T ControlNet Frn1.02 Rev 1.5 - Manual (Page 141)

5–14 Understanding the Resources of Your Drive
Publication 1336 FORCE–5.18 ––March, 1999
The following figure shows an example of a 1336 FORCE drive with
a ControlNet Adapter Board. A function block control application is
also used.
351
352
353
354
355
356
357
358
Xmit Data #1
Xmit Data #2
Rec #1 Data #1
Rec #1 Data #2
Rec #2 Data #1
Rec #2 Data #2
Logic Command
Logic Status
CntNet Out #0
CntlNet Out #1
CntlNet Out #2
CntlNet Out #3
CntlNet Out #4
CntlNet Out #5
CntlNet Out #6
CntlNet Out #7
CntlNet In #0
CntlNet In #1
CntlNet In #2
CntlNet In #3
CntlNet In #4
CntlNet In #5
CntlNet In #6
CntlNet In #7
20
21
22
23
24
25
52
56
322
323
324
325
326
327
328
329
339
340
341
342
387
388
389
390
1A
2A
3A
4A
1B
2B
3B
4B
Function
block
control
application
Analog Inputs
and Outputs
A
Xmit Data #1
Xmit Data #2
Rec #1 Data #1
Rec #1 Data #2
Rec #2 Data #1
Rec #2 Data #2
Rec1 Indirect1
Rec1 Indirect2
Logic Status
Vel Feedback
Ch A Logic Cmd In
Ext Vel Ref
20
21
16
17
22
23
24
25
56
146
367
101
B
Drive–to–Drive
Communications
CntlNet IN#1
CntlNet OUT#1
CntlNet OUT#0 Programmable
Logic
Controller
In the previous figure:
•
Drive B is connected to Drive A using Drive-to-Drive
communications via a DeviceNet cable. You can use
Drive-to-Drive communications to connect any FORCE drive
witha Standard Adapter, a PLC Comm Adapter Board or a
ControlNet Adapter Board.
Using System Resources