4Ć2
Register Description
0Ć3
Not used
4
Status of drop 1Ć7 in bits 1Ć7
5Ć11
Not used
12
Drop number
13
Program mode (keyswitch position 1 = memory
protect, 2 = setup, 3 = program)
14
Messages received
15
Receive timeouts
16
CRC/parity errors
17
Overrun errors
18
Abort errors
19
Messages transmitted
20Ć511 Not used
Figure 4.1 Ć Drop 0 Status Register Assignments
Multibus, Shark, and Remote Head input registers are Read Only.
Multibus, Shark, and Remote Head output registers are Read/Write.
Registers in dual port memory will acknowledge Multibus accesses
just like the module does in the slave drop. A register on a particular
module in a slave drop that is Read Only will be Read Only in the
master drop dual port memory. A bus error will occur if a register in
the master dual port memory is referenced and that register does not
exist in the slave Multibus, Shark, or Remote Head drop.
Registers 0 through 7 on a Shark I/O module are always reserved for
input data. Registers 8 through 15 are always reserved for output
data. Registers 16 through 32 are not accessible. Note that in the
case of a digital module in a mixed (both digital and analog modules)
Shark rack, a bus error will NOT be reported if an invalid register is
referenced. An invalid register may be a register that is not valid for
the particular module in the slot, or that is not valid for Shark modules
at all, i.e., 16 through 32. See Appendix I for a listing of the individual
Shark module memory maps.
Registers 0Ć3 on an M/N 57C328 Remote I/O Head are always
reserved for input data, and registers 4Ć7 are always reserved for
output data. These registers are divided into four input/output pairs.
Each pair is reserved for a Rail; therefore, you can mix input and
output modules in a Rail. Registers 8Ć31 on an M/N 57C328 Remote
I/O Head are not accessible. Refer to Appendix I for more
information.
Registers 0 and 1 on a Remote Drive Interface Head are always
AutoMax outputs (information to the drive) and registers 2 and 3 are
always AutoMax inputs (information from the drive). See appendix I
for a memory map of the Remote Drive Interface Head.
NonĆReliance Multibus I/O modules (modules not manufactured by
Reliance Electric) that are Write Only will be Read/Write in the master
drop dual port memory. NonĆReliance modules used in slave drops
are subject to the following limitations:
The module base address must begin on a 64K boundary.
Summary of Contents for AutoMax 57C328
Page 1: ......
Page 7: ...VI Figure 5 1 Drop Status Monitoring 5 1 Figure 6 1 AutoMax Rail Fault LED Codes 6 5...
Page 14: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...
Page 16: ......
Page 47: ...4 0 4 0 0 2 0 0 0 0 0 0 2 2 0 0 0 0 0 1 0 0 3 0 0 4 1 2 0 0 0 2 1 2 2 0 4 0 0 0 0 0...
Page 70: ......
Page 84: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...
Page 97: ...Appendix B Block Diagrams Remote I O Communications Module M N 57C416 0 3...
Page 99: ...Appendix B Remote I O Head M N 57C328 and M N 57C330...
Page 100: ...Appendix B Remote Drive Interface Head M N 57C329...
Page 102: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...
Page 104: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...
Page 105: ...Appendix E Schematics Communications Passive Tap M N 57C380...
Page 106: ...Appendix E Continued Fiber Optic Rack Power Supply M N 57C368...
Page 110: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...
Page 114: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...
Page 118: ...0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0...
Page 142: ......
Page 143: ...fafadfdfdasfdsfdsdsdfdsfdsfdsfsdfdsa afdfdsfdsfdfdsfdsfsadfda asfdfaddfdd...