GE Power Management
469 Motor Management Relay
4-1
4 SETPOINT PROGRAMMING
4.1 OVERVIEW
4
4 SETPOINT PROGRAMMING 4.1 OVERVIEW
4.1.1 TRIPS/ALARMS/BLOCKS DEFINED
The 469 Motor Management Relay has three basic categories of protection elements. They are TRIPS,
ALARMS, and BLOCKS.
a) TRIPS
An 469 trip feature may be assigned to any combination of the two Auxiliary relays, R2 and R3, in addition to
the R1 Trip Relay. If a Trip becomes active, the appropriate LED (indicator) on the 469 faceplate will illuminate
to show which of the output relays has operated. In addition to the Trip relay(s), a trip will always operate the
Block Start relay. Trip features are may be programmed as latched or unlatched. Once a relay has been oper-
ated by a latched trip, a reset must be performed to clear the trip when the condition is no longer present. If
there is a lockout time, the Block Start relay will not reset until the lockout time has expired. If an unlatched trip
feature becomes active, that trip will reset itself (and associated output relays) as soon as the condition that
caused the trip ceases. Immediately prior to issuing a trip, the 469 takes a snapshot of motor parameters and
stores them as pre-trip values which will allow for troubleshooting after the trip occurs. The cause of last trip
message is updated with the current trip and the 469 display defaults to that message. All trip features are
automatically logged and date and time stamped as they occur. In addition, all trips are counted and logged as
statistics such that any long term trends may be identified.
b) ALARMS
An 469 alarm feature may be assigned to operate any combination of three output relays, R4 Alarm, R3 Auxil-
iary, and R2 Auxiliary. When an Alarm becomes active, the appropriate LED (indicator) on the 469 faceplate
will illuminate when an output relay(s) has operated. Each alarm feature may be programmed as latched or
unlatched. Once a latched alarm feature becomes active, the reset key must be pressed to reset that alarm. If
the condition that has caused the alarm is still present (e.g. hot RTD) the Alarm relay(s) will not reset until the
condition is no longer present. If on the other hand, an unlatched alarm feature becomes active, that alarm will
reset itself (and associated output relay(s)) as soon as the condition that caused the alarm ceases. As soon as
an alarm occurs, the alarms messages are updated to reflect the alarm and the 469 display defaults to that
message. Since it may not be desirable to log all alarms as events, each alarm feature may be programmed to
log as an event or not. If an alarm is programmed to log as an event, when it becomes active, it is automatically
logged as a date and time stamped event.
c) BLOCK START
An 469 Block Start is a feature that prevents or inhibits the start of the motor based on some logic or algorithm.
An 469 Block Start feature is always assigned to the Block Start relay. In addition to the Trip relay(s), a trip will
always operate Block Start relay. If the condition that has caused the trip is still present (e.g. hot RTD), or there
is a lockout time when the Reset key is pressed, the Block Start relay will not reset until the condition is no
longer present or the lockout time has expired. All blocking features are always unlatched and reset immedi-
ately when conditions that caused the block cease. In addition to becoming active in conjunction with trips, a
block may become active once the motor stops. There are several features that operate as such: Starts/Hour,
Time Between Starts, Start Inhibit, Restart Block, and 469 Not Programmed. When a block becomes active,
the block messages are updated to reflect the block (complete with lockout time if required) and the screen
defaults to that message. Blocks are normally not logged as events. If however, a motor start or start attempt is
detected when a block is active, it is automatically logged as a date and time stamped event. This scenario
might occur if someone shorts across the block terminals and overrides the 469 protection to start the motor.
