Motor Control Functions

Overview

The LTMR can be configured for 1 control channel out of 3:

• Terminal strip: Input devices wired to the input terminals on the front face of the LTMR controller.

• HMI: An HMI device connected to the LTMR controller’s HMI port.

• Network: A network PLC connected to the controller network port.

Control Channel Selection

You can easily select between two control channels, assigning one channel to be the local control source and the second channel to be the remote control source.

The possible channel assignments are:

In local control, the control channel selection (Terminal strip or HMI) is determined by setting the Control local channel setting in the Control setting register.

In remote control, the control channel selection is always Network, unless an LTMCU is present. In this case, the control channel selection is determined by setting the Control remote channel setting in the Control setting register.

If an LTMCU is present, the logic input I.6 and the local/remote button on the LTMCU are used together to select between local and remote control source:

For a predefined operating mode, only one control source may be enabled to direct the outputs. You can use the custom logic editor to add one or more additional control sources.

Terminal Strip

In Terminal Strip control, the LTMR controller commands its outputs according to the state of its inputs. This is the control channel factory setting when logic input I.6 is inactive.

The following conditions apply to Terminal Strip control channel:

• Any terminal inputs assigned to start and stop commands control the outputs according to the motor operating mode.

• HMI and network start commands are ignored.

When using LTMCU, the parameter Stop Terminal Strip Disable is set in the Control Setting register.

HMI

In HMI control, the LTMR controller commands its outputs in response to start and stop commands received from an HMI device connected to the HMI port.

The following conditions apply to HMI control channel:

• Any HMI start and stop commands control the outputs according to the motor operating mode.

• Network start commands and terminal strip start commands are ignored.

When using LTMCU, the parameter Stop HMI Disable is set in the Control Setting register.

Network

In Network control, a remote PLC sends commands to the LTMR controller through the network communication port.

The following conditions apply to Network control channel:

• Any network start and stop commands control the outputs according to the motor operating mode.

• The HMI unit can read (but not write) the LTMR controller parameters.

Control Transfer Mode

Select the Control Transfer Mode parameter to enable bumpless transfer when changing the control channel; clear this parameter to enable bump transfer. The configuration setting for this parameter determines the behavior of logic outputs O.1 and O.2, as follows:

When you start the motor in Remote control mode with the PLC, the LTMR controller changes to Local control mode (I.6 = 1 to I.6 = 0) and the status of the motor changes depending on the control transfer mode, as follows:

When the LTMR controller changes from Local to Remote control mode (I.6 = 0 to I.6 = 1), the status of the motor in Local control mode, whether running or stopped, remains unchanged. The control transfer mode selected does not affect the status of the motor as the LTMR controller only takes account of the last control command (logic outputs O.1 or O.2) sent by the PLC.

CAUTION

FAILURE TO STOP AND RISK OF UNINTENDED OPERATION LTMR controller operation cannot be stopped from the terminals when the control channel is changed to Terminal Strip control channel if the LTMR controller is operating under all of the following conditions: Operating in Overload operating mode Configured in Bumpless Operated over a network using Network control channel Operating in Run state Configured for 3-wire (impulse) control Failure to follow these instructions can result in injury or equipment damage.

Whenever control channel is changed to Terminal Strip control channel, operation of the LTMR controller cannot be stopped from the terminals because no terminal input is assigned to a STOP command.

If this behavior is not intended, the control channel must be changed to either Network control channel or HMI control channel to command a STOP. To implement this change, take one of the following steps:

• The commissioner should configure the LTMR controller for either bump transfer of control channel or 2-wire control.

• The installer should provide the LTMR controller with a means of interrupting current to the contactor coil - for example, a push button station wired in series with the LTMR controller outputs.

• The controls engineer should assign a terminal input to disable the Run command using Custom Configuration Mode assignments.

Fallback Transitions

The LTMR controller enters a fallback state when communication with the control source is lost, and exits the fallback state when communication is restored. The transition into and out of the fallback state is as follows:

For information on how to configure communications fallback parameters, refer to Fallback Condition.

When using LTMCU, the parameters Control Transfer Mode and Control Direct Transition parameters are set in the Control Setting register.

Introduction

The LTMR controller responds to the state of the motor and provides control, monitoring and protection functions appropriate to each of the motor’s operating states. A motor can have many operating states. Some operating states are persistent while others are transitional.

A motor’s primary operating states are:

Operating State Chart

The operating states of the LTMR controller firmware, as the motor progresses from Off to Run state, are described below. The LTMR controller verifies current in each operating state. The LTMR controller can transition to an internal trip condition from any operating state.

Protection Monitoring by Operating States

The motor operating states, and the trip and alarm protections provided by the LTMR controller while the motor is in each operating state (denoted with an X), are described below. It can transition to an internal trip condition from any operating state.

Description

The start cycle is the time period allowed for the motor to reach its normal FLC level. The LTMR controller measures the start cycle in seconds, beginning when it detects On Level Current, defined as maximum phase current equal to 20% of FLC.

During the start cycle, the LTMR controller compares:

• Detected current against the configurable Long Start Trip Threshold parameter, and

• Elapsed start cycle time against the configurable Long Start Trip Timeout parameter.

There are three start cycle scenarios, each based on the number of times (0,1, or 2) maximum phase current crosses the Long Start Trip Threshold. A description of each scenario is described below.

For information on the statistics the LTMR controller retains describing motor starts, refer to Motor Starts Counters. For information about the long start protection function, refer to Long Start.

Start Cycle Operating States

During the start cycle, the LTMR controller transitions through the motor’s operating states as follows:

2 Threshold Crosses

In this start cycle scenario, the start cycle executes successfully:

• Current rises above, then drops below, the trip threshold.

• The LTMR controller reports the actual start cycle time, that is, the time elapsed from detection of On Level Current until the maximum phase current drops below the trip threshold.

Start cycle with 2 threshold crosses, single step:

Is Long start trip threshold

Start cycle with 2 threshold crosses, two steps:

1 Threshold Cross

In this start cycle scenario, the start cycle does not execute:

• Current rises above, but does not drop below, the Long Start Trip Threshold.

• If Long Start protection is enabled, the LTMR controller signals a trip when the Long Start Trip Timeout is reached

• If Long Start protection is disabled, the LTMR controller does not signal a trip and the run cycle begins after the Long Start Trip Timeout has expired.

• Other motor protection functions begin their respective duration times after the Long Start Trip Timeout.

• The LTMR controller reports start cycle time as 9999, indicating that current exceeded and remained above the trip threshold.

• The LTMR controller reports the maximum current detected during the start cycle.

Start cycle with 1 threshold cross:

0 Threshold Cross

In this start cycle scenario, the start cycle does not execute:

• Current never rises above the trip threshold.

• If Long Start protection is enabled, the LTMR controller signals a trip when the Long Start Trip Timeout is reached

• If Long Start protection is disabled, the LTMR controller does not signal a trip and the run cycle begins after the Long Start Trip Timeout has expired.

• Other motor protection functions begin their respective duration times after the Long Start Trip Timeout.

• The LTMR controller reports both the start cycle time and the maximum current detected during start cycle as 0000, indicating current never reached the trip threshold.

Start cycle with 0 threshold cross:

Is Long start trip threshold

Overview

The LTMR controller performs control and monitoring functions for single-phase and three-phase electric motors.

• These functions are predefined and fit the applications most frequently used. They are ready to use and are implemented by simple parameter setting after the LTMR controller has been commissioned.

• The predefined control and monitoring functions can be adapted for particular needs using the custom logic editor in the TeSys T DTM to:

  • Customize the use of results of protection functions

  • Change the operation of control and monitoring functions

  • Alter the predefined LTMR controller I/O logic

Operating Principle

The processing of control and monitoring functions has three parts:

• Acquisition of input data:

  • The output of protection function processing

  • External logic data from logic inputs

  • Telecommunication commands (TCC) received from the control source

• Logic processing by the control or monitoring function

• Utilization of the processing results:

  • Activation of logic outputs

  • Display of predefined messages

  • Activation of LEDs

  • Telecommunication signals (TCS) sent via a communications link.

The control and monitoring function process is shown in the following diagram:

Logic Inputs and Outputs

The LTMR controller provides six logic inputs and four logic outputs. By adding an LTME expansion module, you can add four more logic inputs.

Selecting a predefined operating mode automatically assigns the logic inputs to functions and defines the relationship between logic inputs and outputs. Using the custom logic editor, you can change these assignments.

Overview

The LTMR controller can be configured in one out of 10 predefined operating modes. Each operating mode is designed to meet the requirements of a common application configuration.

When you select an operating mode, you specify both the:

• Operating mode type, which determines the relationship between logic inputs and logic outputs, and

• Control circuit type, which determines logic input behavior, based on the control wiring design

Operating Mode Types

There are 10 types of operating modes:

Logic Input Behavior

When you select an operating mode, you also specify that logic inputs are wired for either 2-wire (maintained) or 3-wire (impulse) control. Your selection determines the valid start and stop commands from the various control sources, and sets the behavior of the input command following the return of power after an outage:

Control logic assignments for logic inputs I.1, I.2, I.3, and I.4 are described in each of the predefined motor operating modes.

In each predefined operating mode, logic inputs I.3, I.4, I.5, and I.6 behave as follows:

WARNING
LOSS OF MOTOR PROTECTION IN HMI CONTROL If the terminal strip Stop is disabled, the trip output (terminal NC 95-96) must be wired in series with the contactor coil. Failure to follow these instructions can result in death, serious injury, or equipment damage.

Logic Output Behavior

The behavior of logic outputs O.1 and O.2 is determined by the selected operating mode. See the topics that follow for a description of the 10 predefined operating mode types and the behavior of logic outputs O.1 and O.2.

When the LTMR controller has lost communication with either the network or the HMI, the LTMR controller enters a fallback condition. When it receives a stop command in a fallback condition, logic outputs O.1 and O.2 behave as follows:

For more information about configuring fallback parameters, refer to Fallback Condition.

In all operating mode types, the following logic outputs behave as described in the following table:

Overview

When Overload predefined operating mode is selected, the LTMR controller does not manage logic output O.1, O.2, and O.3.

For all other predefined operating modes (Independent, Reverser, 2-Step, and 2-Speed) the predefined control logic in the LTMR controller is designed to meet the objectives of many common motor starting applications. This includes managing motor behavior in response to:

• Start and stop actions, and

• Trip and reset actions

Because the LTMR controller can be used in special applications, such as fire pumps that require the motor to run despite a known external trip condition, the predefined control logic is designed so that the control circuit, and not the predefined control logic, determines how the LTMR controller interrupts current flow to the contactor coil.

Control Logic Action on Starts and Stops

Predefined control logic acts upon start and stop commands as follows:

• For all 3-wire (impulse) control wiring diagrams, when input 4 is configured as a stop command, the LTMR controller must detect input current at logic input I.4 in order to act on a start command.

• If logic input I.4 is active and a user start action initiates current at logic inputs I.1 or I.2, the LTMR controller detects the rising edge of the current and sets an internal (firmware) latch command that directs the appropriate relay output to close and remain closed until the latch command is disabled.

• A stop action that interrupts current at logic input I.4, causes the LTMR controller to disable the latch command. Disabling the firmware latch causes the output to open-and remain open-until the next valid start condition.

• For all 2-wire (maintained) control wiring diagrams, the LTMR controller detects the presence of current at logic inputs I.1 or I.2 as start commands, and the absence of current disables the start command.

Control Logic Action on Trips and Resets

Predefined control logic manages trips and reset commands as follows:

• Logic output O.4 opens in response to a trip condition.

• Logic output O.4 closes in response to a reset command.

Control Logic and Control Wiring Together Managing Trips

The control circuits, shown in the wiring diagrams in this chapter and in the Appendix, indicate how the LTMR controller’s control logic and the control circuit combine to stop a motor in response to a trip:

• For 3-wire (impulse) control circuits, the control strategy links the state of logic output O.4 to the state of the current at logic input I.4:

  • Control logic opens logic output O.4 in response to a trip.

  • Logic output O.4 opening interrupts current at logic input I.4, disabling the control logic latch command on logic output O.1.

  • Logic output O.1 opens, due to control logic described above, and stops the flow of current to the contactor coil.

  In order to restart the motor, the trip must be reset and a new start command must be issued.

• For 2-wire (maintained) control circuits, the control strategy links the state of logic output O.4 directly with the logic inputs I.1 or I.2.

  • Control logic opens logic output O.4 in response to a trip.

  • Logic output O.4 opening interrupts current to the logic inputs I.1 or I.2

  • Control logic disables the start commands opening logic outputs O.1 or O.2.

  In order to restart the motor, the trip must be reset and the state of Start/Stop operators determines the state of logic inputs I.1 or I.2.

The control circuits needed to run a motor, during a motor protection trip, are not shown in the wiring diagrams that follow. However, the control strategy is to not link the state of logic output O.4 to the state of the input commands. In this way, trip conditions may be annunciated while control logic continues to manage Start and Stop commands.

Description

Use Overload operating mode when motor load monitoring is required and motor load control (start/stop) is performed by a mechanism other than the LTMR controller.

Functional Characteristics

The Overload operating mode includes the following features:

• The LTMR controller overload operating mode does not manage logic outputs O.1, O.2, and O.3. The logic output O.1 and O.2 commands are accessible in Network control channel.

• Logic output O.4 opens in response to a detected diagnostic error.

  NOTE: In Overload operating mode, detected diagnostic error is disabled by default. You can enable it, if needed.

• The LTMR controller sets a bit in a status word when it detects an active signal:

  • On logic inputs I.1, I.2, I.3, or I.4, or

  • From the Aux 1, Aux 2, or Stop buttons on the HMI keypad.

Overload Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a 3-wire (impulse) terminal strip control overload application.

For additional examples of overload operating mode IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of overload operating mode NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

I/O Assignment

Overload operating mode provides the following logic inputs:

Overload operating mode provides the following logic outputs:

Overload operating mode uses the following HMI keys:

Parameters

Overload operating mode requires no associated parameter settings.

Description

Use Independent operating mode in single direct-on-line (across-the-line) full-voltage, non-reversing motor starting applications.

Functional Characteristics

This function includes the following features:

• Accessible in three control channels: Terminal Strip, HMI, and Network.

• The LTMR controller does not manage the relationship between logic outputs O.1 and O.2.

• In terminal strip control channel, logic input I.1 controls logic output O.1, and logic input I.2 controls logic output O.2.

• In network or HMI control channels, the Motor Run Forward Command parameter controls logic output O.1 and the Motor Run Reverse Command parameter controls logic output O.2.

• Logic input I.3 is not used in the control circuit, but can be configured to set a bit in memory.

• Logic outputs O.1 and O.2 deactivate (and the motor stops) when control voltage becomes too low.

• Logic outputs O.1 and O.4 deactivate (and the motor stops) in response to a detected diagnostic error.

Independent Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a 3-wire (impulse) terminal strip control independent application.

For additional examples of independent operating mode IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of independent operating mode NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

I/O Assignment

Independent operating mode provides the following logic inputs:

Independent operating mode provides the following logic outputs:

Independent operating mode uses the following HMI keys:

Timing Sequence

The following diagram is an example of the timing sequence for the Independent operating mode that shows the inputs and outputs for a 3-wire (impulse) configuration:

1 Normal operation

2 Start command ignored: stop command active

Parameters

Independent operating mode requires no associated parameters.

Description

Use Reverser operating mode in direct-on-line (across-the-line) full-voltage, reversing motor starting applications.

Functional Characteristics

This function includes the following features:

• Accessible in three control channels: Terminal Strip, HMI, and Network.

• Firmware interlocking prevents simultaneous activation of the O.1 (forward) and O.2 (reverse) logic outputs: in case of simultaneous forward and reverse commands, only the logic output O.1 (forward) is activated.

• The LTMR controller can change direction from forward to reverse and reverse to forward in one of two modes:

  • Standard Transition mode: The Control Direct Transition bit is Off. This mode requires a Stop command followed by count-down of the adjustable Motor Transition Timeout (anti-backspin) timer.

  • Direct Transition mode: The Control Direct Transition bit is On. This mode automatically transitions after the count-down of the adjustable Motor Transition Timeout (anti-backspin) timer.

• In terminal strip control channel, logic input I.1 controls logic output O.1, and logic input I.2 controls logic output O.2.

• In Network or HMI control channels, the Motor Run Forward Command parameter controls logic output O.1 and the Motor Run Reverse Command controls logic output O.2.

• Logic input I.3 is not used in the control circuit, but can be configured to set a bit in memory.

• Logic outputs O.1 and O.2 deactivate (and the motor stops) when control voltage becomes too low.

• Logic outputs O.1, O.2, and O.4 deactivate (and the motor stops) in response to a detected diagnostic error.

Reverser Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a 3-wire (impulse) terminal strip control reverser application.

Start FW Start forward

Start RV Start reverse

1 The N.C. interlock contacts KM1 and KM2 are not mandatory because the LTMR controller firmware interlocks O.1 and O.2.

For additional examples of reverser operating mode IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of reverser operating mode NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

I/O Assignment

Reverser operating mode provides the following logic inputs:

Reverser operating mode provides the following logic outputs:

Reverser operating mode uses the following HMI keys:

Timing Sequence

The following diagram is an example of the timing sequence for the Reverser operating mode that shows the inputs and outputs for a 3-wire (impulse) configuration when the control direct transition bit is On:

1 Normal operation with stop command

2 Normal operation without stop command

3 Forward run command ignored: transition timer active

4 Forward run command ignored: stop command active

Parameters

Reverser operating mode has the following parameters:

Description

Use Two-Step operating mode in reduced voltage starting motor applications such as:

• Wye-Delta

• Open Transition Primary Resistor

• Open Transition Autotransformer

Functional Characteristics

This function includes the following features:

• Accessible in three control channels: Terminal Strip, HMI, and Network.

• Two-Step operation settings include:

  • A Motor Step 1 To 2 Timeout that starts when current reaches 10% of FLC min.

  • A Motor Step 1 To 2 Threshold setting.

  • A Motor Transition Timeout setting that starts upon the earlier of the following events: expiration of the Motor Step 1 To 2 Timeout, or current falling below the Motor Step 1 To 2 Threshold.

• Firmware interlocking prevents simultaneous activation of O.1 (step 1) and O.2 (step 2) logic outputs.

• In terminal strip control channel, logic input I.1 controls logic outputs O.1 and O.2.

• In Network or HMI control channels, the Motor Run Forward Command parameter controls logic outputs O.1 and O.2. The Motor Run Reverse Command parameter is ignored.

• Logic outputs O.1 and O.2 deactivate, and the motor stops when control voltage becomes too low.

• Logic outputs O.1, O.2 and O.4 deactivate, and the motor stops, in response to a detected diagnostic error.

Two-Step Wye-Delta Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a two-step 3-wire (impulse) terminal strip control wye-delta application.

1 The N.C. interlock contacts KM1 and KM3 are not mandatory because the LTMR controller electronically interlocks O.1 and O.2.

For additional examples of two-step Wye-Delta IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of two-step Wye-Delta NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

Two-Step Primary Resistor Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a two-step 3-wire (impulse) terminal strip control primary resistance application.

For additional examples of two-step primary resistor IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of two-step primary resistor NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

Two-Step Autotransformer Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a two-step 3-wire (impulse) terminal strip control autotransformer application.

1 The N.C. interlock contacts KM1 and KM3 are not mandatory because the LTMR controller electronically interlocks O.1 and O.2.

For additional examples of two-step autotransformer IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of two-step autotransformer NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

I/O assignment

Two-step operating mode provides the following logic inputs:

Two-step operating mode provides the following logic outputs:

Two-step operating mode uses the following HMI keys:

Timing Sequence

The following diagram is an example of the timing sequence for the Two-Step operating mode that shows the inputs and outputs for a 3-wire (impulse) configuration:

1 Normal operation

2 Step 1 start

3 Step 2 start

4 Start command ignored: Stop command active

5 Current falling below the Motor Step 1 To 2 Threshold ignored: preceded by expiration of the Motor Step 1 To 2 Timeout.

Parameters

Two-step operating mode has the following parameters:

Description

Use Two-Speed operating mode in two-speed motor applications for motor types such as:

• Dahlander (consequent pole)

• Pole Changer

Functional Characteristics

This function includes the following features:

• Accessible in three control channels: Terminal Strip, HMI, and Network.

• Firmware interlocking prevents simultaneous activation of O.1 (low speed) and O.2 (high speed) logic outputs.

• Two measures of FLC:

  • FLC1 (Motor Full Load Current Ratio) at low speed

  • FLC2 (Motor High-Speed Full Load Current Ratio) at high speed

• The LTMR controller can change speed in two scenarios:

  • The Control Direct Transition bit is Off: requires a Stop command followed by expiration of the Motor Transition Timeout.

  • The Control Direct Transition bit is On: automatically transitions from high speed to low speed after a time-out of the adjustable Motor Transition Timeout.

• In terminal strip control channel, logic input I.1 controls logic output O.1, and logic input I.2 controls logic output O.2.

• In Network or HMI control channels, when the Motor Run Forward Command parameter is set to 1 and:

  • Motor Low Speed Command is set to 1, logic output O.1 is enabled.

  • Motor Low Speed Command is set to 0, logic output O.2 is enabled.

• Logic input I.3 is not used in the control circuit, but can be configured to set a bit in memory.

• Logic outputs O.1 and O.2 deactivate (and the motor stops) when control voltage becomes too low.

• Logic outputs O.1, O.2, and O.4 deactivate (and the motor stops) in response to a detected diagnostic error.

Two-Speed Dahlander Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a two-speed 3-wire (impulse) terminal strip control Dahlander consequent pole application.

LS Low speed

HS High speed

1 A Dahlander application requires two sets of wires passing through the CT windows. The LTMR controller can also be placed upstream of the contactors. If this is the case, and if the Dahlander motor is used in variable torque mode, all the wires downstream of the contactors must be the same size.

2 The N.C. interlock contacts KM1 and KM2 are not mandatory because the LTMR controller firmware interlocks O.1 and O.2.

For additional examples of two-speed Dahlander IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of two-speed Dahlander NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

Two-Speed Pole-Changing Application Diagram

The following wiring diagram represents a simplified example of the LTMR controller in a two-speed 3-wire (impulse) terminal strip control pole-changing application.

LS Low speed

HS High speed

1 A pole-changing application requires two sets of wires passing through the CT windows. The LTMR controller can also be placed upstream of the contactors. If this is the case, all the wires downstream of the contactors must be the same size.

2 The N.C. interlock contacts KM1 and KM2 are not mandatory because the LTMR controller firmware interlocks O.1 and O.2.

For additional examples of pole-changing IEC diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

For examples of pole-changing NEMA diagrams, refer to relevant diagrams in the TeSys T LTMR Motor Management Controller Installation Guide.

I/O Assignment

Two-Speed operating mode provides the following logic inputs:

Two-Speed operating mode provides the following logic outputs:

Two-speed operating mode uses the following HMI keys:

Timing Sequence

The following diagram is an example of the timing sequence for the two-speed operating mode that shows the inputs and outputs for a 3-wire (impulse) configuration when the Control Direct Transition bit is On:

1 Normal operation with stop command

2 Normal operation without stop command

3 Low-speed start command ignored: motor transition timeout active

4 Low-speed start command ignored: stop command active

Parameters

The following table lists the parameters associated with the Two-Speed operating mode.

Overview

The predefined control and monitoring functions can be adapted for particular needs using the custom logic editor in the TeSys T DTM to:

• Customize the use of results of protection functions

• Change the operation of control and monitoring functions

• Alter the predefined LTMR controller I/O logic.

WARNING
UNINTENDED EQUIPMENT OPERATION The application of custom logic requires expertise in the designing and programming of control systems. Only persons with such expertise must be allowed to program, install, alter, and apply this product. Follow all local and national safety codes and standards. Failure to follow these instructions can result in death, serious injury, or equipment damage.

Possible Functions with Custom Logic

With custom logic, it is possible to customize the motor operating mode to:

• Control the motor through two channels at the same time

• Enable/disable protection functions or change the protection level

• Customize external trips: circuit breaker trip, wrong drawer position

• Create a commissioning or testing mode and activate all outputs without motor current

• Switch to local or remote based on a bit activated by network

• Limit the number of starts per hour

• Use TeSys T for motors over 1000 A, and return correct calculation of power

Configuration Files

The configuration of the LTMR controller consists of two files:

• A configuration file that contains parameter configuration settings

• A logic file that contains a series of logic commands that manage LTMR controller behavior, including:

  • Motor start and stop commands

  • Motor transitions between steps, speeds, and directions

  • The valid control source and transitions between control sources

  • Trip and alarm logic for relay outputs 1 and 2, and the HMI

  • Terminal strip reset functions

  • PLC and HMI communication loss and fallback

  • Load shed

  • Rapid cycle

  • Starting and stopping LTMR controller diagnostics.

When a predefined operating mode is selected, the LTMR controller applies a predefined logic file that permanently resides in the LTMR controller.

When custom operating mode is selected, the LTMR controller uses a customized logic file created in the custom logic editor and downloaded to the LTMR controller from the TeSys T DTM.

Overview

When the LTMR controller detects a trip condition and activates the appropriate response, the trip becomes latched. Once a trip becomes latched, it remains latched, even if the underlying trip condition is eliminated, until cleared by a reset command.

The setting of the Trip Reset Mode parameter determines how the LTMR controller manages trips. The trip reset mode selections, listed below, are described in the topics that follow:

• Manual (Factory setting)

• Automatic

• Remote

The trip reset mode cannot be changed while a trip remains active. All trips must be reset before the trip reset mode can be changed.

Trip Reset Methods

A Reset command can be issued using any of the following means:

• Cycling power

• Reset button on the LTMR controller

• Reset button on the HMI keypad

• Reset command from the HMI engineering tool

• Logic input I.5

• A network command

• Automatic reset

WARNING
RISK OF UNINTENDED OPERATION When the LTMR controller is operating in 2-wire control with an active Run command, a Reset command will immediately restart the motor. Failure to follow these instructions can result in death, serious injury, or equipment damage.

Trip Specific Reset Behaviors

The LTMR controller’s response to trips depends on the nature of the trip that has occurred and how the related protection function is configured. For example:

• Thermal trips can be reset after the Trip Reset Timeout counts down and the utilized thermal capacity falls below the Trip Reset Threshold level.

• If the trip includes a reset timeout setting, the timeout must fully count down before a reset command executes.

• Internal device trips can be reset only by cycling power.

• LTMR controller memory does not retain diagnostic and wiring trips after a power loss, but does retain all other trips after a power loss.

• Internal, diagnostic, and wiring trips cannot be automatically reset.

• All wiring and diagnostic trips can be manually reset by local reset methods.

• For diagnostic trips, network reset commands are valid only in remote (network) control channel.

• For wiring trips, network reset commands are not valid in any control channel.

Trip Characteristics

The LTMR controller trip monitoring functions save the status of communications monitoring and motor protection trips on a power loss so that these trips must be acknowledged and reset as part of an overall motor maintenance strategy.

Introduction

When the Trip Reset Mode parameter is set to Manual, the LTMR controller allows resets-usually performed by a person-via a power cycle of the control power or by using a local reset means, including:

• Terminal Strip (logic input I.5)

• Reset button on the LTMR controller

• Reset commands from the HMI

A manual reset provides on-site personnel the opportunity to inspect the equipment and wiring before performing the reset.

Manual Reset Methods

The LTMR controller provides the following manual reset methods:

Introduction

Setting the Trip Reset Mode parameter to Automatic lets you:

• Configure the LTMR controller to attempt to reset motor protection and communications trips without the intervention of either a human operator or the remote PLC, for example:

  • For a non-networked LTMR controller installed at a location that is physically remote, or locally hard to access

• Configure trip handling for each protection trip group in a manner that is appropriate to the trips in that group:

  • Set a different timeout delay

  • Permit a different number of reset attempts

  • Disable automatic trip resetting

The Trip Reset Mode parameter selection determines the available reset methods.

Each protection trip is included in one of three auto-reset trip groups, based on the characteristics of that trip, as described below. Each trip group has two configurable parameters:

• A timeout: the Auto-Reset Group (number 1, 2, or 3) Timeout parameter, and

• A maximum number of permissible trip resets: the Auto-Reset Attempts Group (number 1, 2, or 3) Setting parameter

WARNING
UNINTENDED EQUIPMENT OPERATION An auto-reset command may restart the motor if the LTMR controller is used in a 2-wire control circuit. Equipment operation must conform to local and national safety regulations and codes. Failure to follow these instructions can result in death, serious injury, or equipment damage.

Reset Behavior

After power is cycled, the LTMR controller clears and sets to 0 the values of the following parameters:

• Auto-Reset Group (number 1, 2, or 3) Timeout and

• Auto Reset Group (number 1, 2, or 3) Setting.

On a successful reset, the Number of Resets counts is cleared and set to 0. A reset is successful if, after reset, the motor runs for 1 minute without a trip of a type in the designated group.

If the maximum number of automatic resets has been reached and if the last reset was unsuccessful, the reset mode turns to Manual. When the motor restarts, the automatic mode parameters are set to 0.

Emergency Restart

Use the Clear Thermal Capacity Level Command, in applications where it is necessary, to clear the Thermal Capacity Level parameter following a Thermal Overload inverse thermal trip. This command permits an emergency restart before the motor has actually cooled.

WARNING
LOSS OF MOTOR PROTECTION Clearing the thermal capacity level inhibits thermal protection and can cause equipment overheating and fire. Continued operation with inhibited thermal protection must be limited to applications where immediate restart is vital. Failure to follow these instructions can result in death, serious injury, or equipment damage.

Number of Resets

Each protection group can be set to manual, 1, 2, 3, 4, or 5.

Select "0" to disable automatic reset of protection trip groups-and require a manual reset-even though the Trip Reset Mode parameter is configured for automatic reset.

Select "5" to enable unlimited auto-reset attempts. After the time delay has expired the LTMR controller continually attempts to reset every trip in that reset group.

Auto-Reset Group 1 (AU-G1)

Group 1 trips require a predefined cooling time after the monitored parameter returns to and falls below a predefined threshold. Group 1 trips include Thermal Overload and Motor Temp Sensor trips. The cooling time delay is non-configurable. However, you can:

• Add to the cooling time delay by setting the Auto-Reset Group 1 Timeout parameter to a value greater than 0, or

• Disable auto-reset by setting the Auto-Reset Group 1 Timeout parameter to 0

Auto-reset group 1 has the following configurable parameters:

Auto-Reset Group 2 (AU-G2)

Group 2 trips generally do not include a predefined cooling time delay before a reset can be executed, but can be reset as soon as the trip condition clears. Many group 2 trips can result in some motor overheating, depending upon the severity and duration of the trip condition, which in turn depends upon the protection function configuration.

You can add a cooling time delay, if appropriate, by setting the Auto-Reset Group 2 Timeout parameter to a value greater than 0. You may also want to limit the number of reset attempts to prevent premature wear or inoperable equipment.

Auto-reset group 2 has the following configurable parameters:

Auto-Reset Group 3 (AU-G3)

Group 3 trips often apply to equipment monitoring and generally do not require a motor cooling period. These trips can be used to detect equipment conditions-for example, an undercurrent trip that detects the loss of a belt, or an overpower trip that detects an increased loading condition in a mixer. You may want to configure group 3 trips in a way that differs significantly from groups 1 or 2, for example, by setting the number of resets to 0, thereby requiring a manual reset after the inoperable condition of the equipment has been discovered and corrected.

Auto-reset group 3 has the following configurable parameters:

Auto-Reset Methods

The LTMR controller allows the following auto-reset methods:

• RB:Test/Reset button on the LTMR or the HMI

• PC: Power cycle on the LTMR controller

• I.5: Set I.5 logic input on the LTMR

• NC: Network command

• Automatic with conditions configured for the protection function group (where AU-GX = AU-G1, AU-G2, or AU-G3)

The following table lists the possible auto-reset methods for each monitored trip:

Introduction

Setting the Trip Reset Mode parameter to Remote adds resetting trips from the PLC over the LTMR network port. This provides centralized monitoring and control of equipment installations. The Control channel parameter selection determines the available reset methods.

Both manual reset methods and remote reset methods reset a trip.

Remote Reset Methods

The LTMR controller provides the following remote reset methods:

Trip Codes

Each trip is identified by a numerical trip code.

Alarm Codes

Each alarm is identified by a numerical alarm code.

Overview

Clear commands allow you to clear specific categories of LTMR controller parameters:

• Clear all parameters

• Clear the statistics

• Clear the thermal capacity level

• Clear the controller settings

• Clear the network port settings

The Clear commands can be executed from:

• A PC running SoMove with the TeSys T DTM

• An HMI device

• A PLC via the network port

Clear All Command

If you want to change the configuration of the LTMR controller, you may want to clear all existing parameters in order to set new parameters for the controller.

The Clear All Command forces the controller to enter configuration mode. A power-cycle is performed to restart correctly in this mode. This enables the controller to pick up the new values for the cleared parameters.

When you clear all parameters, static characteristics are also lost. Only the following parameters are not cleared after a Clear All Command:

• Motor LO1 Closings Count

• Motor LO2 Closings Count

• Controller Internal Temperature Max

Clear Statistics Command

Statistics parameters are cleared without the LTMR controller being forced into configuration mode. Static characteristics are preserved.

The following parameters are not cleared after a Clear Statistics Command:

• Motor LO1 Closings Count

• Motor LO2 Closings Count

• Controller Internal Temperature Max

Clear Thermal Capacity Level Command

The Clear Thermal Capacity Level Command clears the following parameters:

• Thermal Capacity Level

• Rapid Cycle Lockout Timeout

Thermal memory parameters are cleared without the controller being forced into configuration mode. Static characteristics are preserved.

For more information about the Clear Thermal Capacity Level Command, refer to Reset for Emergency Restart.

Clear Controller Settings Command

The Clear Controller Settings Command restores the LTMR controller protection factory settings (timeouts and thresholds).

The following settings are not cleared by this command:

• Controller characteristics

• Connections (CT, temperature sensor, and I/O settings)

• Operating mode

Controller setting parameters are cleared without the controller being forced into configuration mode. Static characteristics are preserved.

Clear Network Port Settings Command

The Clear Network Port Settings Command restores the LTMR controller network port factory settings (address, and so on).

Network port settings are cleared without the controller being forced into configuration mode. Static characteristics are preserved. Only the network communication becomes ineffective.