26
BATCH LIMIT REACHED (NOT DISPLAYED)
Cause: The Part Count fi eld reached the Batch Size
setpoint causing the counter output to drop
out.
Cure: Push the Knob to reset in either RUN or
PROG modes. Batch Count will increment
unless you use the Knob to move the cursor
over that fi eld and clear it.
BELOW MIN SPEED
Cause: The press (after three cycles) was below
the Minimum Speed setpoint.
Cure: 1) Make sure resolver is coupled 1:1.
2) Check your press.
3) Lower setpoint.
BRAKE FAULT
Cause: Press ACTUAL stop time exceeded the FAIL
time.
Cure: Fix the press brake.
BRAKE WARNING
Cause: Press ACTUAL stop time exceeded the
WARN time.
Cure: Fix the press brake.
CHECKSUM FAILURE (Zero, Job0, Job1)
Cause: Data stored in nonvolatile memory has
been corrupted.
Cure: 1) Check for > 0.2A load on +12v output.
The drain can corrupt memory when
powered down
2) Check Electrical noise
3) Check Job memory chip
DIE SENSOR FAULT (NOT DISPLAYED)
Cause: Die Sensor table will display all faults and
indicate the fi rst fault with an “*”.
Cure: 1) Press had die fault.
2) Angle window for sensor is incorrect.
3) Check that unit is receiving the signal
from the sensor.
DRIFT FAULT
Cause: The press moved faster than 1 SPM when
the “control” was not signaled to move.
(i.e. no clutch signal)
Cure: 1) Check that the LED on the I/O Board
for the brake/clutch input is lighting up
when the brake is released.
2) Value set in DRIFT may be too low and
the press may be vibrating from nearby
machinery.
3) Examine brake, clutch, and valves on
the press.
4) Resolver miss-wired or bad.
FEATURE NOT AVAILABLE
Cause: The selected feature cannot be accessed
at the present time.
Cure: 1) Reset any faults you have.
2) Remove the J5 security jumper.
LACK OF MOTION
Cause: The press showed no motion within the
MOTION time period setpoint.
Cure: 1) Check that the resolver is linked to the
crank shaft properly.
2) The setpoint may be too low and not
allowing enough time for the press to
start moving.
MAX SPEED FAULT
Cause: The press was going faster then the
Maximum Speed setpoint.
Cure: 1) Make sure resolver is coupled 1:1.
2) Check for press.
3) Lower setpoint.
MEMORY CORRUPTION
Cause: Internal computer RAM is corrupted or
data coming from the slave CPU has been
corrupted.
Cure: 1) Excessive electrical noise.
MOVING BACKWARDS
Cause: While in RUN mode the press move
backwards. This fault will not occur in
PROG mode.
Cure: If press is moving forward, then check the
resolver wiring at the Master and Slave
board connections. Hit Enter to reset fault.
System Setup & Faults
To Next Page
Loading...