Reliance electric AutoMax 57C328 User manual
Copyright Reliance Electric Industrial Company 1996.
IBMĆXT,ĆATare trademarks of International Business Machines,Inc.
Multibusis a trademark of Intel Corporation.
Bussis a registered trademark of Bussman, Cooper Industries
AMPis a trademark of AMP, Inc.
Amphenolis a trademark of Amphenol, Inc.
Beldenis a trademark of Belden, Inc.
Kermitis a trademark of the trustees of Columbia University.
ReSource, and Sharkare trademarks of Reliance Electric Company
or its subsidiaries.
Reliance, AutoMaxand AutoMateare registered trademarks of Reliance Electric
Company or its subsidiaries.
The information in this manual is sub ect to change without notice.
DANGER
ONLY QUALIFIED ELECTRICAL PERSONNEL FAMILIAR WITH THE
CONSTRUCTION AND OPERATION OF THIS EQUIPMENT AND THE HAZARDS
INVOLVED SHOULD INSTALL, ADJUST, OPERATE, OR SERVICE THIS
EQUIPMENT. READ AND UNDERSTAND THIS MANUAL AND OTHER
APPLICABLE MANUALS IN THEIR ENTIRETY BEFORE PROCEEDING. FAILURE
TO OBSERVE THIS PRECAUTION COULD RESULT IN SEVERE BODILY INJURY
OR LOSS OF LIFE.
DANGER
THE USER IS RESPONSIBLE FOR CONFORMING WITH ALL APPLICABLE
LOCAL, NATIONAL, AND INTERNATIONAL CODES. WIRING PRACTICES,
GROUNDING, DISCONNECTS, AND OVERCURRENT PROTECTION ARE OF
PARTICULAR IMPORTANCE. FAILURE TO OBSERVE THIS PRECAUTION
COULD RESULT IN SEVERE BODILY INJURY OR LOSS OF LIFE.
WARNING
THE USER MUST PROVIDE AN EXTERNAL, HARDWIRED EMERGENCY STOP
CIRCUIT OUTSIDE OF THE CONTROLLER CIRCUITRY. THIS CIRCUIT MUST
DISABLE THE SYSTEM IN CASE OF IMPROPER OPERATION. UNCONTROLLED
MACHINE OPERATION MAY RESULT IF THIS PROCEDURE IS NOT FOLLOWED.
FAILURE TO OBSERVE THIS PRECAUTION COULD RESULT IN BODILY INJURY.
WARNING
INSERTING OR REMOVING A MODULE MAY RESULT IN UNEXPECTED MACHINE
MOTION. POWER TO THE MACHINE SHOULD BE TURNED OFF BEFORE
INSERTING OR REMOVING THE MODULE. FAILURE TO OBSERVE THESE
PRECAUTIONS COULD RESULT IN BODILY INJURY.
CAUTION: This module contains staticĆsensitive components. Do not touch the
connectors on the back of the module. When not in use, the module should be stored in
an antiĆstatic bag. The plastic cover should not be removed. Failure to observe this
precaution could result in damage to, or destruction of, the equipment.
I
Table of Contents
1.0 Introduction 1Ć1...............................................
1.1 Related Publications 1Ć4.....................................
1.2 Related Hardware and Software 1Ć5...........................
1.3 Terms and Conventions sed in This Manual 1Ć5................
2.0 Mechanical/Electrical Description 2Ć1...........................
2.1 Mechanical Description 2Ć1...................................
2.1.1 Remote I/O Module (M/N 57C416) 2Ć1...................
2.1.2 Shark Interface Module (M/N 57C554) 2Ć3................
2.1.3 Remote I/O Head (M/N 57C328) 2Ć4.....................
2.1.4 Remote I/O Head (M/N 57C330) 2Ć5.....................
2.1.5 Remote Drive Interface Head (M/N 57C329) 2Ć7...........
2.2 Electrical Description 2Ć8.....................................
2.2.1 Remote I/O Module (M/N 57C416) 2Ć8...................
2.2.2 Shark Interface Module (M/N 57C554) 2Ć9................
2.2.3 Remote I/O Head (M/N 57C328) 2Ć9.....................
2.2.4 Remote I/O Head (M/N 57C330) 2Ć10.....................
2.2.5 Remote Drive Interface Head (M/N 57C329) 2Ć10...........
2.3 Drop Numbers 2Ć11..........................................
2.4 Remote I/O Drop Hardware 2Ć12...............................
3.0 Installation 3Ć1................................................
3.1 AutoMax Remote I/O Coaxial Cable System Components 3Ć2.....
3.1.1 Drop Cable and Communications Passive Tap 3Ć4.........
3.1.2 Coaxial Cable 3Ć4.....................................
3.1.3 BNC Plug Connector 3Ć5...............................
3.1.4 BNC Tee Adapter 3Ć5..................................
3.1.5 75 Ohm Terminating Load 3Ć6...........................
3.1.6 BNC JackĆtoĆJack Adapter 3Ć6..........................
3.2 Installation Planning 3Ć7......................................
3.2.1 Installation Planning Procedure 3Ć7......................
3.3 Cable System Protection and Isolation Recommendations 3Ć8....
3.3.1 Coaxial Cable Protection 3Ć8............................
3.3.2 Electrical Isolation 3Ć8..................................
3.3.3 Chemical and Thermal Isolation 3Ć9......................
3.3.4 Physical Isolation 3Ć9..................................
3.4 Cable System Construction 3Ć9...............................
3.4.1 Cable Inspection and Testing 3Ć9........................
3.4.2 Cable Pulling 3Ć10......................................
3.4.3 Cable Termination 3Ć10..................................
3.4.4 Cable Segment Testing 3Ć13.............................
3.4.5 Constructing Long Cable Segments 3Ć14..................
3.5 Module Installation 3Ć15.......................................
3.5.1 Installing the Remote I/O Module (M/N 57C416) 3Ć15........
3.5.2 Installing the Shark Interface Module 3Ć17.................
3.5.3 Installing the Remote I/O Head (M/N 57C328 and
M/N 57C330) 3Ć18......................................
II
3.5.4 Installing the Remote Drive Interface Head
(M/N 57C329) 3Ć25.....................................
3.5.5 Remote I/O Network EmergencyĆStop Considerations 3Ć27..
3.6 Module Replacement 3Ć28.....................................
3.6.1 Replacing the Remote I/O Module (M/N 57C416) 3Ć28.......
3.6.2 Replacing the Shark Interface Module (M/N 57C554) 3Ć29...
3.6.3 Replacing the Remote I/O Head (M/N 57C328 and
M/N 57C330) 3Ć30......................................
3.6.4 Replacing the Remote Drive Interface Head
(M/N 57C329) 3Ć31.....................................
3.7 Adding a Slave Drop to the Remote I/O Network 3Ć32.............
3.8 Disconnecting a Slave Drop from the Remote I/O Network 3Ć34....
3.9 Remote I/O Network Coaxial Cable Maintenance 3Ć36.............
3.9.1 Remote I/O Cable Documentation Maintenance 3Ć36........
3.9.2 Remote I/O Cable Design Maintenance 3Ć36...............
3.9.3 Remote I/O Cable Inspection 3Ć36........................
4.0 Programming 4Ć1..............................................
4.1 Master Remote I/O Module Dual Port Memory 4Ć1...............
4.2 Register Organization 4Ć1....................................
4.3 Data Access 4Ć2............................................
4.4 Data Transmission 4Ć3.......................................
4.5 Data pdate Rate 4Ć3........................................
4.6 Configuration 4Ć4...........................................
4.6.1 Shark Configuration 4Ć5................................
4.6.2 Rail I/O Configuration (M/N 57C328) 4Ć5..................
4.6.3 Rail I/O Configuration (M/N 57C330) 4Ć6..................
4.6.4 Remote Drive Interface Head Configuration 4Ć7............
4.7 Application Programming 4Ć8.................................
4.7.1 Multibus and Remote I/O Programming Examples 4Ć9......
4.7.1.1 Configuration Task Example 4Ć10..................
4.7.1.2 Ladder Logic Task Example 4Ć10..................
4.7.1.3 BASIC Task Example 4Ć11........................
4.7.2 Shark Programming Examples 4Ć12.......................
4.7.2.1 Configuration Task Example 4Ć13..................
4.7.2.2 Ladder Logic Task Example 4Ć13..................
4.7.2.3 BASIC Task Example 4Ć14........................
5.0 Programming Terminal Communications 5Ć1.....................
5.1 Remote I/O Module (M/N 57C416) 5Ć1.........................
5.1.1 Self Test (T) 5Ć1.......................................
5.1.2 Status (S) 5Ć2.........................................
5.1.3 Read Slot (R) 5Ć3......................................
5.1.4 Write Slot (W) 5Ć3......................................
5.2 Remote Heads (M/N 57C328, M/N 57C329, and M/N 57C330) 5Ć4.
5.2.1 Self Test (T) 5Ć4.......................................
5.2.2 Status (S) 5Ć4.........................................
5.2.3 Clear (C) 5Ć6..........................................
5.2.4 Read Port (R) 5Ć6......................................
5.2.5 Write Port (W) 5Ć6.....................................
III
6.0 Diagnostics And Troubleshooting 6Ć1...........................
6.1 The Remote I/O Module's OK LED is Off 6Ć1....................
6.2 Error Code A is on the Remote I/O Module's
7ĆSegment Displ y 6Ć1.......................................
6.3 Remote I/O Network F ilures 6Ć1..............................
6.4 The Sh rk Interf ce Module's CPU OK LED is Off 6Ć3............
6.5 The Sh rk Interf ce Module's COM OK LED is Blinking 6Ć3.......
6.6 All LEDs on the Remote I/O He d or Remote Drive
Interf ce He d re Off 6Ć4....................................
6.7 Error Code A is on the Remote I/O He d or
Remote Drive Interf ce He d 7ĆSegment Displ y 6Ć5............
6.8 The Remote I/O He d's R il F ult LED is On 6Ć5................
6.9 Error Code 31 is on the Processor Module's LED Displ y 6Ć6.....
V
Figure 1.1 Ć A Typical Coaxial Cable Remote I/O Network 1Ć1.............
Figure 1.2 Ć A Typical FiberĆOptic Cable Remote I/O Network 1Ć2..........
Figure 1.3 Ć Multiple Remote I/O Network Connections (Coax) 1Ć3.........
Figure 2.1 Ć Remote I/O Module Faceplate 2Ć2..........................
Figure 2.2 Ć AutoMax Remote I/O hark Interface Module Faceplate 2Ć3....
Figure 2.3 Ć AutoMax Remote I/O Head Faceplate (M/N 57C328 and
M/N 57330) 2Ć5..........................................
Figure 2.4 Ć AutoMax Remote Drive Interface Head Faceplate 2Ć8.........
Figure 2.5 Ć Remote I/O Network Drop Numbers 2Ć11.....................
Figure 2.6 Ć Mutually Exclusive Drop Numbers 2Ć12.......................
Figure 3.1 Ć Remote I/O Network Coaxial Cable ystem 3Ć3..............
Figure 3.2 Ć Communications Passive Tap 3Ć4...........................
Figure 3.3 Ć Coaxial Cable 3Ć4........................................
Figure 3.4 Ć Dual Crimp BNC Plug Connector 3Ć5.......................
Figure 3.5 Ć BNC Tee Adapter 3Ć5.....................................
Figure 3.6 Ć 75 Ohm Terminating Load 3Ć6..............................
Figure 3.7 Ć BNC JackĆtoĆJack Adapter 3Ć6.............................
Figure 3.8 Ć Ferrule on the RGĆ59/U Cable 3Ć10..........................
Figure 3.9 Ć RGĆ59/U (Belden 9259) Cable tripping Dimensions 3Ć10.......
Figure 3.10 Ć Connector Installation tep 3 for RGĆ59/U Cable 3Ć11..........
Figure 3.11 Ć Connector Installation tep 6 for RGĆ59/U Cable 3Ć12..........
Figure 3.12 Ć Connector Installation tep 7 for RGĆ59/U 3Ć12................
Figure 3.13 Ć Connector Installation tep 8 for RGĆ59/U Cable 3Ć12..........
Figure 3.14 Ć Connector Installation tep 9 for RGĆ59/U Cable 3Ć13..........
Figure 3.15 Ć Connector Attached to RGĆ59/U Cable 3Ć13...................
Figure 3.16 Ć Cable plicing 3Ć14........................................
Figure 3.17 Ć Mounting Dimensions 3Ć19.................................
Figure 3.18 Ć Mounting Examples 3Ć20...................................
Figure 3.19 Ć Grounding tud Location 3Ć21..............................
Figure 3.20 Ć Grounding the Remote Head 3Ć22...........................
Figure 3.21 Ć 120 VAC or 240 VAC Input Power Connections 3Ć23...........
Figure 3.22 Ć Connecting the Remote I/O Head to the FiberĆ
Optic Network 3Ć24........................................
Figure 3.23 Ć Connecting the Remote Drive Interface Head to the
FiberĆOptic Network 3Ć26...................................
Figure 3.24 Ć Ready Relay 3Ć28.........................................
Figure 3.25 Ć Typical EĆ top Circuit Using Ready Contacts 3Ć28.............
Figure 3.26 Ć Adding a New Rack Drop to the End of the Remote I/O
Network (Coax) 3Ć33.......................................
Figure 3.27 Ć Adding an Intermediate Rack Drop to the Remote I/O
Network (Coax) 3Ć34.......................................
Figure 3.28 Ć Disconnecting an End Rack Drop from the Remote I/O
Network (Coax) 3Ć35.......................................
Figure 3.29 Ć Disconnecting an Intermediate Rack Drop from the
Remote I/O Network (Coax) 3Ć35............................
Figure 4.1 Ć Drop 0 tatus Register Assignments 4Ć2.....................
Figure 4.2 Ć hark I/O Module Configuration Word 4Ć5...................
Figure 4.3 Ć ample Coaxial Cable Remote I/O Network With Multibus
Rack and Remote I/O Head Drops 4Ć9......................
Figure 4.4 Ć ample Coaxial Cable Remote I/O Network With hark
Rack Drops 4Ć12..........................................
VI
Figure 5.1 Ć Drop Status Monitoring 5Ć1................................
Figure 6.1 Ć AutoMax Rail Fault LED Codes 6Ć5.........................
Appendices
Appendix A
*/* "'#% )# #,#('+ 1
Appendix B
%($ #!*&+ 1
Appendix C
1 (*, #'(-, 1
Appendix D
&(, **(* (+ 1
Appendix E
"&,#+ 1
Appendix F
,/(*$ % )# #,#('+ 1
Appendix G
% 0+,& (&)('', #+, 1
Appendix H
&(, ,/(*$ )# #,#('+ 1
Appendix I
&(, &(*0 ))#'! 1
Appendix J
%(++*0 ( *&+ 1
Appendix K
#*1),# &(, ,/(*$ .*.#/ 1
1Ć1
The products described in this manual are manufactured or
distributed by eliance Electric Industrial Company.
The AutoMaxremote I/O network interconnects an AutoMax or
DCS 5000 Processor with remote AutoMax racks, emote I/O Heads,
or remote Sharktracks. The AutoMax emote I/O Communications
module (M/N 57C416) is the interface between the AutoMax or DCS
5000 Processor and the remote I/O on the network.
The AutoMax emote I/O network is designed for master/slave
operation. The network is composed of two main parts: a number of
nodes (drops) and a transmission medium (coaxial or fiberĆoptic
cable).
There are two types of drops: master and slave. The master drop is a
Multibustrack that contains at least one AutoMax or DCS 5000
Processor module and a emote I/O Communications module.
Slave drops can be:
Demote I/O Heads (M/N 57C328 and M/N 57C330)
Demote Drive Interface Heads (M/N 57C329)
DShark racks containing I/O modules and an AutoMax emote I/O
Shark Interface module (M/N 57C554)
DAutoMax racks containing AutoMax I/O modules and a emote
I/O Communications module
DIBMĆcompatible personal computers containing the AutoMax PC
Link Interface module (M/N 57C445). efer to the AutoMax PC
Link instruction manual (J2Ć3011) for more information.
An AutoMax emote I/O network can have a maximum of seven slave
drops. All five types can be mixed on the same network.
The drops are connected using coaxial cable or, when noise
immunity and total electrical isolation is required, fiberĆoptic cable.
The coaxial cable network is structured in a bus configuration. This
type of topology is characterized by a main trunkline in which
individual nodes are connected in a multidrop fashion as shown in
figure 1.1.
Master
Drop
Coaxial Cable
Slave Drop Slave Drop Slave Drop
Figure 1.1ĆATypical Coaxial Cable emote I/O Network
The black bar shown on the rightĆhand margin of this page will be
used throughout this instruction manual to signify new or revised
text or figures.
1Ć2
The fiberĆoptic cable network is or anized in an active star
confi uration. With this type of topolo y, each node is connected to a
multiĆport central point, also referred to as a hub," containin active
reĆtransmittin devices as shown in fi ure 1.2.
Master
Drop
Slave Drop
Slave Drop
Slave Drop
Hub FiberĆOptic
Cable
Fi ure1.2ĆATypical FiberĆOptic Cable Remote I/O Network
The type of cable used (whether coaxial or fiberĆoptic) does not affect
the operation of the Remote I/O network protocols, application
software, or the operation of the Remote I/O Communications
module, Shark Interface module, Remote I/O Head, or Remote Drive
Interface Head.
The Remote I/O Communications module in the master drop (drop 0)
rack functions as the network's Remote I/O master. Master or slave
Remote I/O Communications modules may be installed in any slot in
the rack. Any number of Remote I/O Communications modules can
be installed in a master rack, each controllin a separate Remote I/O
network. See fi ure 1.3.
1Ć3
Slave Drop Slave Drop Slave Drop
Master Drop
Remote I/O
Network B
R
I
O
R
I
O
P
Remote I/O
Network A
P Ć Processor Module
RIO Ć Remote I/O Communications Module
Figure 1.3 Ć Multiple Remote I/O Network Connections (Coax)
The master initiates and controls all data transmissions on the
network y polling every slave drop in a roundĆro in sequence. A
slave drop's Remote I/O Communication module, Remote I/O Head,
or AutoMax Remote I/O Shark Interface module functions as an I/O
scanner: it reads data in from the input modules and writes data out
to the output modules. The data sent from the master drop to the
slave updates the status of the slave's outputs. The slave drop sends
the current status of its inputs ack to the master.
Each Remote I/O Communications module contains a 4K word
dualĆport memory for storing the data that is transmitted over the
network. DualĆport memory is accessi le to oth the module and the
AutoMax Processor in the rack. In the master module, the dualĆport
memory contains an image of the status of all the inputs and outputs
of the I/O modules in the slave drops. The application task that
controls the I/O associated with these I/O modules actually examines
the inputs and controls the outputs in the image area.
The Remote I/O Communications module provides an RSĆ232
compati le serial port and the associated software needed to monitor
the status of the drops. An ASCII terminal or a personal computer
running terminalĆemulation software are also required. For more
information, refer to section 5.0.
The remainder of this manual descri es the functions and
specifications of the Remote I/O Communications module, Remote
I/O Head, Remote Drive Interface Head, and the AutoMax Remote I/O
Shark Interface module. It also includes installation and
trou leshooting procedures, as well as configuration and
programming information.
1Ć4
Related publications that may be of interest:
JĆ3012 AutoMate/AutoMax Digital I/O Rail and Modules Manual
JĆ3650 AutoMax Processor Module Instruction Manual
JĆ3675 AutoMax Enhanced Basic Language Instruction Manual
JĆ3676 AutoMax Control Block Language Instruction Manual
J2Ć3094 AutoMax Enhanced Ladder Language Instruction
Manual
JĆ3809 hark XL II Programmable Controller Instruction Manual
J2Ć3018 hark XL I/O ystem Instruction Manual
D2Ć3170 Rail Interface Card Instruction Manual
Various AutoMax Programming Executive instruction manuals
IEEE 518 Guide for the Installation of Electrical Equipment to
Minimize Electrical Noise Inputs to Controllers From
External ources
Your personal computer and DO operating system manual(s).
Other instruction manuals applicable to your hardware
configuration.
1Ć5
1.2 Related Hardware and Software
Model number (M/N) 57C416 cont ins one Remote I/O
Communic tions module.
M/N 57C554 cont ins one AutoM x Remote I/O Sh rk Interf ce
module.
M/N 57C328 nd M/N 57C330 e ch cont in one AutoM x Remote I/O
He d.
M/N 57C329 cont ins one AutoM x Remote Drive Interf ce He d.
The Remote I/O Communic tions module, the AutoM x Remote I/O
He d, the AutoM x Remote Drive Interf ce He d, nd the AutoM x
Remote I/O Sh rk Interf ce module c n be used with ll versions of
the AutoM x nd DCS 5000 Processor.
Remote I/O communic tions is supported by ll versions of the
AutoM x Progr mming Executive softw re.
1.3 Term and Convention U ed in Thi
Manual
Throughout this instruction m nu l, cert in terms will be used for
brevity nd cl rity.
A Remote I/O Communic tions module (M/N 57C416) will be referred
to s Remote I/O module.
A remotelyĆloc ted AutoM x/DCS 5000 r ck cont ining I/O modules
nd Remote I/O Communic tions module will be referred to s
Multibu drop.
An AutoM x Remote I/O He d (M/N 57C328 or M/N 57C330 with
AutoM te digit l nd n log I/O R ils nd Loc l I/O He ds
connected will be referred to s Remote I/O Head drop.
An AutoM x Remote Drive Interf ce He d (M/N 57C329) with drive
connected will be referred to s Remote Drive Interface Head
drop.
A Sh rk r ck cont ining I/O modules nd n AutoM x Remote I/O
Sh rk Interf ce module (M/N 57C554) will be referred to s
Shark drop.
An AutoM x Remote I/O Sh rk Interf ce module will be referred to s
Shark Interface module.
Unless otherwise st ted, the m teri l presented in this instruction
m nu l pplies to the Remote I/O module, Remote I/O He d, Remote
Drive Interf ce He d, nd the Sh rk Interf ce module. Any
differences between these products will be pointed out explicitly
fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa
afdfdsfdsfdfdsfdsfsadfda
asfdfaddfdd
4
2.0 MECHANICAL/ELECTRICAL
DESCRIPTION
#$- - .$*) -,$ - .# ( #)$' ) ' .,$' #,. ,$-.$- *!
.# (*. (*/' (*. (*. ,$0 ). ,!
) .# #,& ). ,! (*/'
2.1 Mechan cal Descr pt on
#$- - .$*) -,$ - .# ! +'. - *)) .*,- $)$.*,- )
-1$.# - *! .# (*. (*/' (*. (*. ,$0
). ,! ) .# #,& ). ,! (*/'
2.1.1 Remote I/O Module (M/N 57C416)
# (*. (*/' $- +,$). $,/$. -- ('3 .#. +'/"- $).*
.# &+') *! .# /.*2 & # (*/' *)-$-.-
*! +,$). $,/$. *, ! +'. ) +,*. .$0 )'*-/, #
! +'. *).$)- % .*, .- . .# .*+ ) *..*( .* -$(+'$!3
, (*0$)" .# (*/' !,*( .# ,& !$"/, !*, ) $''/-.,.$*)
*! .# (*/' ! +'.
# 4+$) 4-# '' *)) .*, *) .# ! +'. -/++*,.- .# 4
*(+.$' - ,$' +*,. -,$ $) - .$*) # 4+$) 4-# ''
*)) .*, *) .# ! +'. $- /- .* *)) . .# (*/' .* .#
) .1*,&
# .1* .#/(1# ' -1$.# - *) .# ! +'. , /- .* - . .#
, (*. ) .1*,& ,*+ )/( , # /++ , .#/(1# ' -1$.#
, +, - ).- .# (*-. -$")$!$). $"$. .# '*1 , .#/(1# ' -1$.#
, +, - ).- .# ' -. -$")$!$). $"$. # .#/(1# ' -1$.# - ,
, *)'3 *) +*1 ,4/+ ! $. $- ) --,3 .* #)" .# ,*+ )/( ,
3*/ (/-. #)" .# - ..$)" ) .# ) 3' +*1 , ) .# & *!
.# (*/' , .1* " *)) .*,- .#. ..# .* .# -3-. (
&+')
*, $")*-.$ +/,+*- - .# ! +'. *).$)- - 0 )4- "( ).
.#. $-+'3- ,,*, * - # ,,*, * - , !$) $)
++ )$2 ", ) -../- *) .# ! +'. $)$. - 1# ) .#
(*/' $- *+ ,.$*)' *, -#*/' , +'
'
$%
&# ' !% !& "%
2Ć3
2.1.2 Shark Interface Module (M/N 57C554)
The Shark Interface module is a printed circuit board assembly that
plugs into the backplane of a Shark rack in the first slot to the right of
the power supply.
It consists of a printed circuit board and a faceplate. The faceplate
contains tabs at the top and bottom to simplify removing the module
from the rack. On the back of the module are two connectors that
attach to the system backplane. Module dimensions are given in
Appendix A.
The faceplate of the module contains one 9Ćpin female DĆshell
connector labeled NET ORK." See figure 2.2. This connector
allows the module to connect to the Remote I/O network.
The module faceplate contains two green status LEDs. hen lit, the
top LED, labeled CPU OK," indicates that the module has passed its
powerĆup diagnostics and is operating properly. hen lit, the bottom
LED, labeled COM OK," indicates that the module is communicating
on the Remote I/O network. hen the LED is flashing, it indicates that
an invalid drop number has been selected on the rotary switch,
which is described below .
The 16Ćposition rotary switch is used to select the Shark rack's
Remote I/O drop number (1 to 7 or 9 to F). This switch is read only on
powerĆup. If it is necessary to change the rack's drop number, you
must change the setting of the rotary switch and then cycle power.
.
.
.
.
.
.
.
NET ORK
DROP NUMBER
COM OK
CPU OK
57C554
AUTOMAX
REMOTE I/O
INTERFACE
.
Figure 2.2 Ć AutoMax Remote I/O Shark Interface Module Faceplate
2Ć4
2.1.3 Remote I/O Head (M/N 57C328)
The Remote I/O Head can be used as an interface between the
AutoMax Remote I/O network and the AutoMate rail I/O system,
which consists of Local Heads, digital or analog rails, LED modules,
or Thumbwheel Switch Modules. Note that although the Remote I/O
Head can be used as an interface to drives with railĆtype interface
ports (such as the Reliance G Ć2000/VTAC V controller), it is
recommended that only the Remote Drive Interface Head
(M/N 57C329) be used for interfacing with drives over an AutoMax
Remote I/O network. See section 2.1.5 for more information.
The M/N 57C328 Remote I/ O Head is identical to the M/N 57C330
Remote I/O Head, except that you can mix input and outputs in the
same rail. Each port on the Remote I/O head contains separate
address spaces for inputs and outputs. Like the M/N 57C330 Remote
I/O Head, it can control up to 4 digital rails, analog I/O rails, or Local
Heads. Each Local Head can in turn control up to 4 AutoMate digital
rails. Therefore, a Remote I/O Head with 4 Local Heads connected to
it can control a maximum 16 digital rails.
The AutoMax Remote I/O Head consists of a power supply, two
printed circuit boards (a processor board and a remote I/O
communications board), a faceplate, and a protective metal
enclosure. See figure 2.3 for an illustration of the both Remote I/O
Heads.
The 25Ćpin DĆshell connector on the faceplate supports the
RSĆ232Ćcompatible serial port described in section 5.0. The BNC
connector on the faceplate is used to connect the Remote I/O Head
to the Remote I/O network. The four I/O connectors are used for Rail
and/or Local Head communications.
The thumbwheel switch on the faceplate is used to set the Remote
I/O network drop number. Drop numbers 1 through 7 inclusive
indicate valid Remote I/O drop numbers.
The terminal strip on the faceplate provides connections for incoming
power as well as a set of normally open contacts from the Ready
Relay. The contacts are closed when the Remote I/O Head is
operating properly and open if a problem is detected in the onĆboard
microprocessor. These contacts can be used to take remedial action
in the event of a problem with the onĆboard microprocessor.
For diagnostic purposes, the faceplate contains a sevenĆsegment
LED that displays error codes (see Appendix D). The faceplate also
contains six status LEDs, which are labeled as follows:
RUN (amber): Normally on; if off, indicates that the C U watchdog
has timed out.
OWER (green): When on, indicates power is being supplied to the
C U and internal voltages are within range.
C U READY (amber): Will turn on after the powerĆup diagnostics
have been completed successfully and the C U watchdog has not
timed out. Also indicates the state of the Ready Relay contacts. When
on, the Ready Relay contacts are closed.
FAULT MSB/FAULT LSB (amber): Normally off. When on, these LEDs
indicate the particular rail that has experienced a fault. These LEDs
are valid while the Rail Fault LED is lit. See section 6.8 for more
information.
RAIL FAULT (red): When on, indicates that a rail fault has occurred.
2Ć5
Note that during powerĆup diagnostics, the bottom four LEDs (CPU,
READY, FAUL MSB, FAUL LSB, and RAIL FAUL ) will stay on long
enough to allow verification that they will light.
0
1
2
3
L1
L2
120
240
FUSE YPE
250V
AGC 2 AMP
RUN
POWER
FAUL MSB
FAUL LSB
CPU READY
RAIL FAUL
REMO E
I/O HEAD
AutoMax
Figure 2.3 Ć AutoMax Remote I/O Head Faceplate (M/N 57C328 and M/N 57330)
2.1.4 Remote I/O Head (M/N 57C330)
he Remote I/O Head can be used as an interface between the
AutoMax Remote I/O network and the AutoMate rail I/O system,
which consists of Local Heads, digital or analog rails, LED modules,
or humbwheel Switch modules. Note that although the Remote I/O
Head can be used as an interface to drives with railĆtype interface
ports (such as the RelianceGPĆ2000/V AC V controller), it is
recommended that only the Remote Drive Interface Head
(M/N 57C329) be used for interfacing with drives over an AutoMax
Remote I/O network. See section 2.1.5 for more information.
2Ć6
The Remote I/O Head can control up to 4 digital rails, analog I/O rails,
or Local Heads. Each Local Head can in turn control up to 4
AutoMate digital rails. Therefore, a Remote I/O Head with 4 Local
Heads connected to it can control a maximum of 16 digital rails. The
digital rails must be all inputs or all outputs.
The AutoMax Remote I/O Head consists of a power supply, two
printed circuit boards (a processor board and a remote I/O
communications board), a faceplate, and a protective metal
enclosure. ee figure 2.3 for an illustration of the Remote I/O Head.
The 25Ćpin DĆshell connector on the faceplate supports the
R Ć232Ćcompatible serial port described in section 5.0. The BNC
connector on the faceplate is used to connect the Remote Head to
the Remote I/O network. The four I/O connectors are used for Rail
and/or Local Head communications.
The thumbwheel switch on the faceplate is used to set the Remote
I/O network drop number. Drop numbers 1 through 7 inclusive
indicate valid Remote I/O drop numbers.
The terminal strip on the faceplate provides connections for incoming
power as well as a set of normally open contacts from the Ready
Relay. The contacts are closed when the Remote I/O Head is
operating properly and open if a problem is detected in the onĆboard
microprocessor. These contacts can be used to take remedial action
in the event of a problem with the onĆboard microprocessor.
For diagnostic purposes, the faceplate contains a sevenĆsegment
LED that displays error codes (see Appendix D). The faceplate also
contains six status LEDs, which are labeled as follows:
RUN (amber): Normally on; if off, indicates that the CPU watchdog
has timed out.
POWER (green): When on, indicates power is being supplied to the
CPU and internal voltages are within range.
CPU READY (amber): Will turn on after the powerĆup diagnostics
have been completed successfully and the CPU watchdog has
not timed out. Also indicates the state of the Ready Relay
contacts. When on, the Ready Relay contacts are closed.
FAULT M B / FAULT L B (amber): Normally off. When on, these
LEDs indicate the particular rail that has experienced a fault.
These LEDs are valid while the Rail Fault LED is lit. ee section
6.8 for more information.
RAIL FAULT (red): When on, indicates that a rail fault has occurred.
Note that during powerĆup diagnostics, the bottom four LEDs (CPU
READY, FAULT M B, FAULT L B, and RAIL FAULT) will stay on long
enough to allow verification that they will light.
This manual suits for next models
4
Table of contents
