Baldor Flex+DriveII Installation Manual page 84

Incremental move. An incremental move is being profiled. See the Mint keywords
INCA and INCR.
Jog. The drive is jogging. In the Mint help file, see the topics JOG, JOGCOMMAND and
Jog screen.
Preset jog. The drive is jogging. The jog was triggered from a Preset jog table.
Overspeed. The measured speed of the motor has exceeded the trip level defined by
DRIVESPEEDFATAL. Check that the trip level is set to a suitable value for your
application. When accelerating to a demand speed close to the trip level, there will
typically be a certain amount of overshoot. Using the Fine-tuning tool, check the
amount of overshoot you get with the acceleration and demand speeds being used in
your application.
Positional Move. The drive is performing a linear move. See the Mint keywords MOVEA
and MOVER.
Preset positions. The drive is performing a linear move. This motion has been triggered
from a Preset move table.
DB Overload. The regeneration resistor (Dynamic Brake) has been overloaded. See
the Mint keyword DBEXTTRIPSWITCH and associated keywords.
Stop. A STOP command has been issued or the stop input is active.
Drive disabled. The drive must be enabled before operation can continue. See section
3.8. Click the Drive enable button in WorkBench v5.
Crash. The drive enable input or the Enable DIP switch have become inactive whilst the
drive was in the enable state (or the drive was enabled whilst they were inactive) - bit
13 in AXISEERROR will be set. The drive can be programmed to ignore this state using
the Mint keyword DRIVEENABLEINPUTMODE (see the Parameters tool).
Suspend. The SUSPEND command has been issued and is active. Motion will be
ramped to zero demand whilst active.
Speed demand. The drive is under speed control. See the Mint keywords SPEEDREF,
SPEEDREFSOURCE and related commands.
Reverse software or hardware limit. A reverse software limit has been activated.
See AXISERROR and/or AXISSTATUS to determine which applies.
Forward software or hardware limit. A forward software limit has been activated.
See AXISERROR and/or AXISSTATUS to determine which applies.
Firmware being updated (horizontal bars appear sequentially). New firmware is being
downloaded to the drive.
Initialization error. An initialization error has occurred at power on. See the Error Log or
INITERROR topics in the help file. Initialization errors should not normally occur.
User defined symbols can be made to appear using the Mint keywords LED and LEDDISPLAY.
6-4 Troubleshooting MN1902