1 how the system reacts to drive faults, 2 mcr output control – Rockwell Automation SA3100 Diag,Troublesht,Startup,Guide User Manual

Page 19

Advertising
background image

Diagnostics and Troubleshooting

2-5

than 2% of the rated motor current, the PMI Regulator will turn off the MCR output.
Note that the PMI Regulator will always turn off the MCR output within 300 msec of
the fault occurrence even if the 2% current level has not been reached.

If any of the following faults are detected by the PMI Regulator, it will disable the gates
immediately and set the corresponding bit in the Drive Fault register (202/1202):

DC Bus Overvoltage Fault (Bit 0)

DC Bus Overcurrent Fault (Bit 1)

Ground Current Fault (Bit 2)

Instantaneous Overcurrent Fault (Bit 3)

Power Supply Fault (Bit 4)

Charge Bus Time-Out Fault (Bit 6)

Over Temperature Fault (Bit 7)

Resolver Broken Wire Fault (Bit 8)

Resolver Fault (Bit 9)

Overspeed Fault (Bit 10)

Power Technology Fault (Bit 11)

PMI Regulator Bus Fault (Bit 13)

UDC Run Fault (Bit 14)

Communications Lost Fault (15)

The PMI operating system will then take over turning off the MCR output as described
above.

2.4.1.2 MCR Output Control

The MCR output on the PMI Regulator’s Resolver & Drive I/O board is used to control
an optional M-contactor to turn off power to the motor. This option is selected during
UDC module parameter configuration. If the programmer chooses to connect the
MCR output to an M-contactor, contacts from this device must be wired to the AUX
IN1/MFDBK input as feedback. The PMI operating system will wait for AUX
IN1/MFDBK to turn on before executing any operating mode.

The Run Permissive input (RPI) on the Resolver & Drive I/O board and the MCR
output are interlocked in hardware. The MCR output can be turned on only when the
RPI is asserted. The MCR output itself is under the control of the PMI Regulator.
Application tasks have no direct control of the MCR output. RPI is controlled by the
user. When RPI is off, MCR cannot be activated.

!

ATTENTION: The UDC task is not stopped automatically when a drive
fault occurs. The user must ensure that the application tasks test the
Drive Fault register (202/1202) and take the appropriate action if a fault
is detected.

Advertising