YASKAWA MicroTrac Gateway User manual

MicroTrac Gateway - Remote I/O
Part No. 46S03196-0010
02/01/01 RD 3196-10
Warranty. Standard products manufactured by the Company are warranted to be free from defects in workmanship and
material for a period of one year from date of shipment and any products which are defective in workmanship or material will
be repaired or replaced, at the Company's option, at no charge to the Buyer. Final determination as to whether a product is
actually defective rests with the Company. The obligation of the Company hereunder shall be limited solely to repair or replace,
at the Company's discretion, products that fall within the foregoing limitations, and shall be conditioned upon receipt by the
Company or written notice of any alleged defects or deficiency promptly after discovery and within the warranty period, and in
the case of components or units purchased by the Company, the obligations of the Company shall not exceed the settlement that
the Company is able to obtain from the supplier thereof. No products shall be returned to the Company without its prior
consent. Products which the Company consents to have returned shall be shipped prepaid f.o.b. the Company's factory. The
Company cannot assume responsibility or accept invoices for unauthorized repairs to its components, even though defective.
The life of the products of the Company depends, to a large extent, upon the usage thereof, and THE COMPANY MAKES NO
WARRANTY AS TO FITNESS OF ITS PRODUCTS FOR THE SPECIFIC APPLICATIONS BY THE BUYER NOR AS
TO PERIOD OF SERVICE UNLESS THE COMPANY SPECIFICALLY AGREES OTHERWISE IN WRITING AFTER
THE PROPOSED USAGE HAS BEEN MADE KNOWN TO IT.
This warranty does not apply to experimental or developmental products for which NO warranty is made or given and Buyer
waives any claim thereto.
THE FOREGOING WARRANTY IS EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF MERCHANTABILITY OR OF FITNESS FOR
A PARTICULAR PURPOSE AND BUYER HEREBY WAIVES ANY AND ALL CLAIMS THEREFORE.
Limitation Of Liability. IN NO EVENT SHALL THE COMPANY BE LIABLE FOR LOSS OF PROFIT, INDIRECT,
CONSEQUENTIAL OR INCIDENTAL DAMAGES WHETHER ARISING OUT OF WARRANTY, BREACH OF
CONTRACT OR TORT.
MicroTrac Gateway
to
Allen-Bradley PLC-5™and PLC-3®
For use on MicroTrac®Local Area Network

Table of Contents
i
Table of Contents
12/22/94
Page
INTRODUCTION ............................................................................................. 1
HARDWARE ..................................................................................................... 1
JARC Board Setup ........................................................................................ 3
JARC Board Jumper Selections .................................................................... 3
JARC Board DIP Switch .............................................................................. 3
JARC Board LED Operation ........................................................................ 5
SmartMUX™ Board Setup ........................................................................... 6
SmartMUX™ Board Baud Rate / Last State ................................................ 6
SmartMUX™ Board Rack Address ............................................................. 7
SmartMUX™ Board LED Operation ........................................................... 8
Local I/O Racks ............................................................................................. 8
Terminating the Remote I/O Link ................................................................. 9
GENERAL OPERATION .............................................................................. 10
MicroTrac to PLC (LOGO) ........................................................................ 11
PLC to MicroTrac (LOGI) .......................................................................... 12
MicroTrac to PLC (NUMO) ....................................................................... 13
PLC to MicroTrac (NUMI) ......................................................................... 14
PLC©Access to Drive Setup Parameters ................................................... 16
PLC Block Trasfer ...................................................................................... 17
PAC Considerations .................................................................................... 20
TROUBESHOOTING – JARC BOARD ..................................................... 22
TROUBLESHOOTING – SmartMUX™ BOARD .................................... 23
TROUBLESHOOTING – A-B PLC-5™ or PLC-3®.................................. 23
PCDU TERMINAL OPERATION ............................................................... 24
Block 0 – Gateway Set-Up ......................................................................... 25
Information Block 1 – Digital Read ........................................................... 25
Information Block 2 – Digital Read ........................................................... 25
Information Block 3 – Digital Write ........................................................... 26
Information Block 4 – Digital Write ........................................................... 26
Information Block 5 – PLC Block Read .................................................... 26
Information Block 6 – PLC Block Read .................................................... 27
Information Block 7 – PLC Block Write .................................................... 27
Information Block 8 – PLC Block Write .................................................... 27
Information Block 9 – MicroTrac Logic Input Allocation ......................... 28
Information Block 10 – MicroTrac Logic Output Allocation .................... 28
Information Block 11 – MicroTrac Numeric Input Allocation .................. 28
Information Block 12 – MicroTrac Numeric Output Configuration ......... 29

List of Illustrations
Figure
Number Title Page
1 JARC Interface Board ............................................................................... 1
2 SmartMUX Board ....................................................................................... 2
3 Local I/O Interface Board ........................................................................... 9
3a Local I/O Interface "Plug-In" Modules ...................................................... 9
4 PAC Logic Output to PLC ....................................................................... 11
5 PAC Logic Input from PLC ..................................................................... 12
6 PAC Numeric Output to PLC ................................................................... 13
7 PLC to PAC Numeric Input ..................................................................... 14
8 PLC Initialization Hardware and Signal Flow ..........................................15
9 Sample PAC Diagram .............................................................................. 16
10 Sample PLC Ladder Diagram .................................................................. 19
11 Sample PAC Diagram .............................................................................. 20
List of Tables
Table
Number Title Page
1 JARC Jumper Selection .............................................................................. 3
2 JARC Board SW1 DIP Switch, Positions 1-8 ........................................... 4
3 JARC Board SW1 DIP Switch, Positions 9-11 ......................................... 4
4 JARC Board SW1 DIP Switch, Position 12 ............................................... 5
5 JARC Board LED Operation ...................................................................... 5
6 SmartMUX Board Baud Rate Switch ........................................................ 6
7 SmartMUX Board Last I/O Group Switch ................................................ 6
8 SmartMUX Board Last State Switch ......................................................... 7
9 SmartMUX Board Watchdog Switch ........................................................ 7
10 SmartMUX Board Rack Adddress Selection ............................................. 7
11 SmartMUX Board LED Operation ............................................................ 8
12 Troubleshooting the JARC Board ............................................................ 20
13 Troubleshooting the SmartMUX Board ................................................... 21
14 Troubleshooting the PLC ......................................................................... 21
Table of Contents
ii Table of Contents 12/22/94

INTRODUCTION
1
INTRODUCTION
2/17/95
INTRODUCTION
HARDWARE
The Allen-Bradley Programmable Logic Controller (PLC) Remote I/O
Gateway allows any drive on the MicroTrac®LAN to communicate with an
Allen-Bradley PLC-5 or PLC-3 through the 1771 I/O Network. Both logic
and numeric information can be transferred.
CAUTION
The gateway must be properly grounded. Use star washers that
will cut into the metal of the gateway box when mounting to
ensure proper earth ground.
The Allen-Bradley PLC gateway is a self-contained unit with one JARC
interface board, one SmartMUX interface board, one eight-point local I/O
interface board, and a power supply. The NEMA 1 enclosure contains the
electronics with internal connections for AC power, digital I/O points, and
external connections for the MicroTrac LAN. The initial setup is factory
configured, but depending on the application, the following electronic boards
may require setup.
1. The JARC board is the interface board which provides the LAN
connection and communicates with the SmartMUX board through dual port
memory contained on the JARC board. A 12-position DIP switch on the
JARC board, labeled SW1, sets the LAN node address (default = 200) and the
rack address (default = 1). Refer to Figure 1.
Figure 1. JARC Interface Board
J5
J6
EPROM
J7
+5 V
Ground
–5 V
PE
J1
• 128K
• 512K
Jumper
J9
XMIT LED D3 (Red)
RECON LED D4 (Yellow)
J3
PCDU
Connection
Fuse
PGM
LED
SW1
1
12
PWR
LED
F1
LAN
Connection
J8
CTS • • • GRD
Jumper
•

HARDWARE
2HARDWARE 12/22/94- RD 3196-10
2. One SmartMUX board is attached to the JARC board using screws and a
pluggable 17-pin header. Two 6-position DIP switches on the SmartMUX
board, labeled SW1 and SW2, set the rack address and the baud rate for the
communications. Refer to Figure 2.
Figure 2. SmartMUX Board
J1
EPROM
I/O Rack Connector
J2
PWR LED (Red – for Power)
LED (Green – for Communications)
Connector
to
JARC J5 or JARC J6
SW1
SW2
1
10
RST
ALE
CLR
SHD
BLUE
GND
CCL
CGD
+5V
Connections to
A-B 1771 I/O
Network

HARDWARE
3
JARC Board Setup
12/22/94- RD 3196-10
The JARC board has jumpers and one 12-position DIP switch that are user
configurable.
NOTE: The JARC board only reads the DIP switch settings on
power-up.
The proper version of EPROM must be placed in the EPROM socket.
The jumpers located on the JARC board are described in Table 1, with the
defaults shown.
NOTE: On revision "C" and later JARC boards, J1 is an ARCNET
BNC connector and J2 does not exist.
NOTE: If the hand held Portable Command/Display Unit (PCDU)
does not operate properly after plugging into the JARC board J3
RS-232 connector, check the F1 fuse. This fuse protects the +5V
power to the PCDU.
Positions 1 through 8 of DIP switch SW1 determine the LAN node address.
Usually this address is set for 200, when the system has only one PLC gateway.
The address of the second PLC gateway is typically set to 201. Enter the node
ID in binary notation, choosing either a "0" or a"1" for each bit. The least
significant bit is position 1, and the most significant bit is position 8. The
standard gateway addresses are listed in Table 2. The JARC board switches use
pull-down logic, so a closed switch is a logic 0.
JARC Board
Setup
JARC Board
DIP Switch
JARC Board
Jumper
Selections
Table 1. JARC Jumper Selection
JUMPER DEFAULT DESCRIPTION
J8 Center - GND 1-2 CTS (Clear to Send for RS-232)
J9 128K - Center 1-2 RAM_CE2 (Internal selection for
128k static RAM chip)

HARDWARE
412/22/94- RD 3196-10
JARC Board DIP Switch
Positions 9, 10, and 11 of DIP switch SW1 determine the starting rack number
for the JARC board to accept on the network (see Table 3). This rack number
must match the lowest rack number selected on the SmartMUX board. The
SmartMUX board is usually wired to JARC board connector J5. Rack 0 is only
valid for a PLC-3.
Table 2. JARC Board SW1 DIP Switch, Positions 1-8
MICROTRAC SW1 DIP Switch Position
LAN
LSB MSB
ADDRESS 1 2 3 4 5 6 7 8
200 X X X O X X O O
201 O X X O X X O O
202 X O X O X X O O
203 O O X O X X O O
204 X X O O X X O O
205 O X O O X X O O
206 X O O O X X O O
207 O O O O X X O O
X = Closed = Logical 0 = Switch ON
O = Open = Logical 1 = Switch OFF
Table 3. JARC Board SW1 DIP Switch, Positions 9 - 11
RACK
SW1 DIP Switch Position
J5 J6 9 10 11
0 1 X X X
1 2 O X X
2 3 X O X
3 4 O O X
4 5 X X O
5 6 O X O
6 7 X O O
7 N/A O O O
X = Closed = Logical 0 = Switch ON
O = Open = Logical 1 = Switch OFF

HARDWARE
5
12/22/94- RD 3196-10 JARC Board LED Operation
Position 12 of DIP switch SW1 enables or disables the hardware watchdog (see
Table 4). The hardware watchdog resets the JARC board if a hardware or
software failure occurs. This feature should be enabled for all installations.
There are four LEDs on the JARC interface board; one power LED and three
user indication LEDs. The placement of the LEDs is shown in Figure 1.
Table 4. JARC Board SW1 DIP Switch, Position 12
WATCHDOG Position 12 DESCRIPTION
ON O Enable Watchdog (DEFAULT)
OFF X Disable Watchdog
X = Closed = Logical 0 = Switch ON
O = Open = Logical 1 = Switch OFF
Table 5. JARC Board LED Operation
LED COLOR DESCRIPTION
PWR RED ON when the JARC board has proper +5V power from the
power supply. The power LED should always be ON.
RECON YELLOW ON when a LAN reconfiguration occurs. Each time a node
enters or leaves the network, a reconfiguration occurs. If the
reconfiguration completes and the network is stable, the
RECON LED will turn OFF after about 1-2 seconds. If this
LED is ON constantly or blinks frequently, a network problem
is likely.
XMIT RED ON when the JARC board is communicating on the network.
This LED is normally on all the time.
PGM RED The PGM LED is used to indicate hardware error conditions.
If this LED is ON, turn off the power to the PLC gateway and
then turn the power back on. If this LED remains ON, then a
hardware problem has been detected with the JARC board.
JARC Board
LED Operation

HARDWARE
6SmartMUX Board Setup 12/22/94- RD 3196-10
SmartMUX
Board Setup
SmartMUX
Board Baud
Rate / Last
State
The SmartMUX board resides on top of the JARC board and is screwed in
place. The SmartMUX board requires four screws to attach it to the JARC
board.
There are two jumper positions on the SmartMUX board, labeled J1 and J2.
These jumpers are used for EPROM functions which are not required by this
implementation of the SmartMUX board, so these jumpers are not installed.
The SmartMUX board has two 6-position DIP switches, labeled SW1 and
SW2, to select the rack address and baud rate. The rack address must be
consecutive between zero and seven (inclusive), and must match the rack
address set on the JARC board.
The first DIP switch, SW1, controls the baud rate, last I/O group, last state,
and watchdog (see Tables 6-9), and one bit of the rack address. The "Baud
Rate" and "Last State" should be the only switches that require modification.
Table 6. SmartMUX Board Baud Rate Switch
DIP Switch SW1
BAUD RATE Position 1 Position 2
57.6K X X
(DEFAULT)
115.2K O X
230.4K X O
230.4K O O
X = Closed switch = Switch ON
O = Open switch = Switch OFF
Table 7. SmartMUX Board Last I/O Group Switch
DIP Switch SW1
LAST I/O GROUP Position 3
NOT LAST X
LAST O
(DEFAULT)
X = Closed switch = Switch ON
O = Open switch = Switch OFF

HARDWARE
7
SmartMUX Board Rack Address
12/22/94- RD 3196-10
SmartMUX
Board Rack
Address
The following DIP switch settings represent the SmartMUX board connected
to the JARC board via the J5 connector.
Table 8. SmartMUX Board Last State Switch
DIP Switch SW1
LAST STATE Position 4
RESET ALL X
(DEFAULT)
HOLD ALL O
X = Closed switch = Switch ON
O = Open switch = Switch OFF
Table 9. SmartMUX Board Watchdog Switch
DIP Switch SW1
WATCHDOG Position 5
DISABLE WATCHDOG X
ENABLE WATCHDOG O
(DEFAULT)
X = Closed switch = Switch ON
O = Open switch = Switch OFF
Table 10. SmartMUX Board Rack Address Selection
DIP Switch / Position
RACK ADDRESS
SW1-6 SW2-1 SW2-2 SW2-3 SW2-4 SW2-5 SW2-6
00 X X X X X X X
01 X X X X O X X
(DEFAULT)
02 X X X O X X X
03 X X X O O X X
04 X X O X X X X
05 X X O X O X X
06 X X O O X X X
07 X X O O O X X
X = Closed switch = Switch ON
O = Open switch = Switch OFF

8
HARDWARE
SmartMUX Board LED Operation 12/22/94- RD 3196-10
SmartMUX
Board LED
Operation
There are two LEDs on the SmartMUX board; one status LED and one
communications LED. The function of these LEDs is listed in Table 11.
The placement of the LEDs is shown in Figure 2.
The PLC gateway has local I/O connection points. The SmartMUX board connects
to a local I/O interface board which has 8 logic inputs or logic outputs that can be
either AC or DC. The local interface I/O are always assigned to module group 0,
slot 1 of the rack being simulated by the SmartMUX board. These I/O can be
accessed by the PLC directly, but not by devices on the drive network.
The addresses of the 8 I/O points range from: I:XX0/10 to I:XX0/17 for inputs,
and O:XX0/10 to O:XX0/17 for outputs, where XX is the Gateway rack number
(octal). These I/O must be all inputs or all outputs.
Table 11. SmartMUX Board LED Operation
LED COLOR DESCRIPTION
STATUS RED When the SmartMUX board has proper +5V power from the
(PWR) power supply, this LED will flash once or twice and then turn
OFF. If the LED flashes once, then this node is an odd rack
address. If the LED flashes twice, then this node is an even
rack address.
COMM GREEN When the Allen-Bradley PLC establishes communications with
(LED1) the SmartMUX board, this LED will flash or be ON. A flashing
LED means the PLC is in program mode. A solid or ON LED
means the PLC is in run mode and information is being
transferred. Proper operation with the PLC in run mode
results in this LED being ON.
Local I/O Racks

HARDWARE
9
Terminating the Remote I/O Link
12/22/94- RD 3196-10
MagneTek Part Description
Number
05P00090-0327 AC Output Module
05P00090-0328 AC/DC Input Module
05P00090-0329 DC Output Module
05P00090-0330 DC Input Module
05P00090-0331 SPST Relay Output Module
The SmartMUX board is an Allen-Bradley Pyramid Solution product.
Therefore, it must meet Allen-Bradley wiring and communication
specifications. Terminating the remote I/O link is part of the specification the
SmartMUX board must meet. A user must place a terminating resistor on both
physical ends of a remote I/O link to ensure proper operation.
NOTE: Refer to Allen Bradley’s 1785 PLC-5 Family Programmable
Controllers, Hardware Installation Manual, Publication 1785-6.6.6
June 1993 or later, page 7-10 for proper terminating resistor
installation instructions.
Figure 3. Local I/O Interface Board
Figure 3a. Local I/O Interface "Plug-In" Modules
8 LEDs (0 - 7)
+ –
1A Fuse
0
1
2
3
4
5
6
7
1
16
Fuse
5A
Spare
5A Fuse
Terminals
Terminals
for power
Input or Output (AC or DC) modules
SmartMUX
Edge
Connector
Terminating the
Remote I/O Link

GENERAL OPERATION
10 GENERAL OPERATION 2/17/95- RD 3196-10
GENERAL
OPERATION
The PLC gateway is normally mounted and wired on a Yaskawa drive panel.
The gateway, however, can be mounted remotely by the customer. In this case,
special consideration must be given to the 120 VAC power source for the
gateway power supply. DO NOT connect the gateway power cord directly into
a wall outlet. Instead, use an isolation transformer and tie one side of the
secondary to the nearest earth ground (the steel structure of the building is
usually a good choice). The ground studs on the MicroTrac drive panels or
cabinets must also be connected directly to a solid earth ground in order to
assure that the gateway enclosure and the drive panels are at the same potential.
Improper grounding may cause erratic operation of the LAN.
The PLC gateway, when connected to the A-B 1771 remote I/O cable, is treated
as a remote I/O rack by the PLC. From a PLC-5 the selected rack number can
be between 1 and 7 (inclusive). From a PLC-3 the rack number can be between
0 and 7. Note that the PLC gateway is configured as a rack on the remote I/O
link, and cannot be the same rack number as any other rack on the remote I/O
link. If local racks are to be used, the rack number assigned to the PLC
gateway must be greater than the last local rack number.
The baud rate of the A-B 1771 remote I/O link is determined by the PLC. A
DIP switch on the SmartMUX board selects the A-B 1771 link speed. The
acceptable baud rates are 57.6K, 115.2K, and 230.4K.
A gateway uses one entire remote rack with the following capacity:
— 64 numerics PLC to MicroTrac in group 0, slot 0.
— 64 numerics MicroTrac to PLC in group 0, slot 0.
— 8 local logics (8 inputs or 8 outputs) in group 0, slot 1.
— 112 logics PLC to MicroTrac in groups 1-7.
— 112 logics MicroTrac to PLC in groups 1-7.
CAUTION
The gateway must be properly grounded. When mounting, use star washers
that will cut into the metal of the gateway box to ensure proper earth ground.
.

GENERAL OPERATION
11
MicroTrac to PLC
12/22/94- RD 3196-10
MicroTrac to
PLC (LOGO)
Logic outputs from a PAC schematic to a PLC can be visualized as shown in
Figure 4. Logic output (LOGO) PAC blocks send a logic value from the drive
to the remote device specified by the node, channel, and sub channel defined
for that block. The node number for a single PLC gateway is typically 200.
These logics utilize groups 1-7 for a maximum total of 112 (7 x 16) MicroTrac
to PLC logic bits.
The LAN channel number is in octal notation and corresponds directly with
the A-B PLC rack and group number for the associated simulated A-B input.
In addition, the number will have a 100's prefix digit of 1 that can be
associated with the A-B PLC input "I" notation. Thus:
LAN CHANNEL 124 = INPUT RACK 2, GROUP 4 or I:24
LAN CHANNEL 127 = INPUT RACK 2, GROUP 7 or I:27
The sub channel number will also be in octal, and will directly correspond to
the bit number of the simulated output. Thus, the 16 possible bits are:
LAN SUB CHANNEL 00 = BIT 00
: : :
LAN SUB CHANNEL 07 = BIT 07
LAN SUB CHANNEL 10 = BIT 10
: : :
LAN SUB CHANNEL 17 = BIT 17
Each PLC logic input bit can be addressed by no more than one drive. If more
than one drive attempts to initialize the same bit (sub channel) in a given
group, a “Logic Output Allocation Error” message will be sent to the drive
over the LAN.
NOTE: LAN traffic throughput may significantly improved if all logic
values for a particular drive are grouped together and not needlessly
divided between multiple PLC groups.
Figure 4. PAC Logic Output to PLC
TYPICAL LOGO
103-D
LOGO
Node Chan. Sub
200 136 3
LAN Cable
Logic Bits
PLC Gateway
Remote
I/O Cable
PLC Ladder
Logic
I:36/03

GENERAL OPERATION
12 PLC to MicroTrac 12/22/94- RD 3196-10
PLC to
MicroTrac
(LOGI)
Logic inputs to a PAC schematic from a PLC can be visualized as shown in
Figure 5. Logic input (LOGI) PAC blocks receive a logic value sent to the
drive from the remote device specified by the node, channel, and sub channel
defined for that block. The node number for a single PLC gateway is typically
200. These logics utilize groups 1-7 for a maximum of 112 (7 x 16) PLC to
MicroTrac logic bits.
The channel number is in octal notation. The first digit is a 0, and can be
associated with the A-B PLC output "O" notation. The 2nd and 3rd digits
represent the rack number and the group number. Thus:
LAN CHANNEL 015 = OUTPUT RACK 1, GROUP 5 or O:15
The sub channel number will also be in octal, and will directly correspond to
the bit number of the simulated input. Thus, the 16 possible bits are:
LAN SUB CHANNEL 00 = BIT 00
: : :
LAN SUB CHANNEL 07 = BIT 07
LAN SUB CHANNEL 10 = BIT 10
: : :
LAN SUB CHANNEL 17 = BIT 17
Any drive can request logic inputs from any rack and group of the PLC that
has outputs defined for that location. The Drive Kernel software will select the
appropriate bit and send it to the appropriate LOGI block.
NOTE: LAN traffic throughput may significantly improved if all logic
values for a particular drive are grouped together and not needlessly
divided between multiple PLC groups.
Figure 5. PAC Logic Input from PLC
TYPICAL LOGI
101-D
LOGI
Node Chan. Sub
200 015 2
LAN Cable
Logic Bit
PLC Gateway
Remote
I/O Cable
PLC Ladder
Logic
O:015/02

GENERAL OPERATION
13
MicroTrac to PLC
5/2/95- RD 3196-10
MicroTrac to
PLC (NUMO)
Numeric outputs from a PAC schematic to a PLC can be visualized as shown in
Figure 6. Numeric output (NUMO) PAC blocks send a numeric value from the
drive to the remote device specified by the node, channel, and sub channel defined
for that block. The node number for a single PLC gateway is typically 200.
The channel number here has a similar meaning to that discussed above for the
logic function, except that the leading digit must be a 1. The SmartMUX board
only supports Numeric block transfers to slot 0 and group 0. Thus:
LAN CHANNEL 130 = RACK 3, GROUP 0
The PAC block’s sub channel number will be in decimal, and will normally range
from 0 through 63. This number represents the location of the numeric output data
in the Block Transfer Read data file. Up to 64 values may be processed in one
Block Transfer operation.
Every numeric value exchanged between the drive system and the PLC must have
a unique value for channel and subchannel.
Figure 6. PAC Numeric Output to PLC
TYPICAL NUMO
104-D
NUMO
Node Chan. Sub.
200 110 19
LAN Cable
DATA
PLC Gateway
Remote
I/O Cable
PLC Ladder
Logic
FF
Block
Transfer
Read

GENERAL OPERATION
14 PLC to MicroTrac 12/22/94- RD 3196-10
PLC to
MicroTrac
(NUMI)
Numeric inputs to a PAC schematic from a PLC can be visualized as shown in
Figure 7. Numeric input (NUMI) PAC blocks receive a numeric value sent to
the drive from the remote device specified by the node, channel, and sub
channel defined for that block. The node number for a single PLC gateway is
typically 200.
The channel number here has the same meaning as the numeric outputs, except
that the leading digit is always 0. The SmartMUX board only supports
Numeric block transfers to slot 0 and group 0. Thus:
LAN CHANNEL 030= RACK 3, GROUP 0
The PAC block’s sub channel number will be in decimal, and will normally be
between 0 and 63. This number represents the location of the numeric input
data in the Block Transfer Write data file. Up to 64 values may be processed
in one Block Transfer operation. Only one BTW can be used for each
Gateway.
Figure 7. PLC to PAC Numeric Input
TYPICAL NUMI
102-D
NUMI
Node Chan. Sub.
200 010 39
LAN Cable
DATA
PLC Gateway
Remote
I/O Cable
PLC Ladder
Logic
FF
Block
Transfer
Write

GENERAL OPERATION
15
PLC Access to Drive Setup Parameters
12/22/94- RD 3196-10
PLC Access to
Drive Setup
Parameters
The PLC can be used to change the value of drive setup parameters. In the
example illustrated in Figures 8 & 9, the PLC can modify a parameter called
“Master Line Speed”. This parameter is also accessible from the Standard
Control Display Unit (SCDU), the Portable Control Display Unit (PCDU), and
potentially from a Remote Display Unit (RDU) or a personal computer
TracView display. The subsequent programming techniques make sure that a
change from one device is reflected at the other device and establish when one
device takes precedence over the other.
Within the PAC program, the PLC initialization commands coordinate the
multiple source parameter exchange. The PLC software must also help
coordinate this multiple source exchange.
Figure 8. PLC Initialization Hardware and Signal Flow
PLC
1771 Remote I/O Cable
PLC Gateway
(Node 200)
RS232
PCDU
MicroTrac SCDU
(Node 1)
Remote Display
Controller
(Node 103)
RDU
RDU
RDU
RS485
PAC Initialization
Definitions
MicroTrac
LAN Cable

GENERAL OPERATION
16 PLC Access to Drive Setup Parameters 12/22/94- RD 3196-10
There are two types of PAC blocks which can be used with the PLC
initialization command. These are the GETN and RDCI blocks which allow
the programmer to define drive setup parameters, each of which has a unique
"function" number. The vaules of these setup functions can be changed from
the drive, and can also be accessed by devices on the drive network such as the
PLC gateway.
Figure 9 shows the relationship between an RDCI PAC block and the PLC
initialization table. A GETN block would be handled the same way. The PLC
initialization table refers to this RDCI by its function number (115).
Figure 9. Sample PAC Diagram
300-E
TO OTHER CIRCUITS IN THIS
DRIVE'S PAC DIAGRAM
F# 115 MASTER LINE SPD
RDCI
FCTN
115
0 0
DESC
UNIT
MAX
MIN
DFLT
TYPE
BLCK
SCAN
DP
P
S
REMOTE DISPLAY LIST
Node Chan Menu
No. No. Item
103 5 6 115 MASTER LINE SPD 0 RDCI
FCTN DESCRIPTION DP
Block
Type
PLC INITIALIZATION
PLC PLC In PLC In PLC Out PLC Out FCTN DP DESCRIPTION
Node Chan Item Chan Item
200 120 1 020 1 115 0 MASTER LINE SPD
HEADER
PAC SOURCE HEADER
LAN ID:
DRIVE NAME:
PRODUCT CLASS
SCAN A RATE
1
LEAD DRIVE
312_V9_R1
0.0
Greeting1:
THIS MAGNETEK DSD (DIGITAL SYSTEMS DRIVE) IS POWERED UP AND READY
Greeting2:
THERE ARE NO FAULTS TO REPORT AT THIS TIME
MASTER_LINE_SPD
FPM
10000
0
1000
RDCI
300
E

GENERAL OPERATION
17
PLC Block Transfer
12/22/94- RD 3196-10
PLC Block
Transfer
The PLC INITIALIZATION table can be described as follows:
1. The PLC INITIALIZATION channel number establishes the rack and
word of the block transfer. The channel designation follows the same
conventions as the NUMI and NUMO channel conventions described above.
The "PLC IN" and "PLC OUT" headings on the PLC Table are from the PLC
Viewpoint. The "PLC OUT" column corresponds to the BTW and the "PLC
IN" corresponds to the BTR.
2. The PLC INITIALIZATION item number designates the position of
the parameter in the PLC block transfer data file.
3. The PLC INITIALIZATION table requires both input and output
channel and item numbers. Sensible PLC programming technique dictates that
the input and output channel and item numbers be grouped consecutively, and
that the input and output item numbers be equal. The programmer can then
take full advantage of the high level data manipulation techniques.
4. When the PLC gateway detects a change in data from the PLC, the
appropriate drive is updated with the new data. The data transition initiates
this exchange. This new value is returned to the PLC as confirmation of a
successful update. When this parameter is changed from the drive, the
gateway updates the PLC with the new value and expects the new value to be
returned as confirmation of the exchange.
Power-up presents a special condition. There are two locations of nonvolatile
memory for the same parameter, the drive and the PLC. The drive memory is
chosen as the default on a power-up condition. To insure proper initialization
of the RDCI or GETN blocks during power-up, the PLC gateway will inhibit
transfers from the PLC until the drive data confirmation is returned from the
PLC on power-up.
A sample ladder diagram is shown in Figure 10. It illustrates the technique
used to satisfy the above requirements. The first rung moves data from the
PLC into the write transfer buffer. The second rung moves data from the read
transfer buffer into the write transfer buffer. This is conditioned by a transition
of data from the last PLC scan. The third rung executes the write to the PLC