ERR-LIST-ACM.pdf - 第48页

3203 RETRY INFORMATION\x0ASection : %1\x0AFeeder : %2\x0AChannel : %3\x0AToolbit : %4\x0ANozzle : %5\x0AVacuum specified : %6\x0AVacuum measured : %7\x0AComponent : %8\x0A 3204 The recovery action failed One or more erro…

100%1 / 52
3190 %1 :\tno bump match
- Number of bumps is too large for
bump checking algorithm.
- No bump present or too many bumps (objects) found at
expected position.
- Bad component quality.
- Adjust matrix definition.
- Check component quality.
3191
%1 :\tToolbit too big for coplanarity
actions
Toolbit does not fit in the
coplanarity unit. Using this toolbit
for coplanarity actions may cause
serious damage to the toolbit,
head or coplanarity unit. - Not supported toolbit size Update action spec
3192
%1 detected an unexpected
collision
During Toolbit exchange, the head
detected an impact with an object
while lowering the head. - A toolbit is in a toolbit exchange location that should be empty.
- Update the toolbit exchange data, or
- Remove / replace the unexpected toolbit from the toolbit exchange unit.
3193 %1 did not detect a touchdown
The head did not detect an impact
within the specified search area.
- The impact surface is not present.
e.g. during picking from tray, no component is present in tray
pocket.
during fetching a toolbit while executing a toolbit
exchange, no toolbit is present in the toolbit pocket - Check if the requested part is present on the machine.
3195 Invalid feeder file
The system encountered invalid
data in a feeder control file of a
feeder that is used in the action
spec.
- Syntax error in feeder control file.
- Value out of range. - Check the feeder file.
3197 %1 :\tFeeder in error
One of feeders in the feeder
section reported an error. - Problem on feeder. - Solve the error cause.
3199
Restoring XY calibration data
failed
The data to restore has arrived on
the aPC, but the processing of this
data has failed.
- Original data could not be backed up.
- Current calibration values could not be invalidated.
- New calibration data could not be used.
- If the original data files were all backed up, restore these files manually and
restart the machine.
- Otherwise, the machine still has valid calibration data. Try to restore again
when the problem that caused the backup to fail is solved.
3200 MIS data collection failed
The MIS data collection failed, no
MIS data is retrieved from the
system. The MIS data for this
order period is not reliable.
- Disk full.
- Illegal file modifications by user.
- System communication error.
- No current order available on the system, or no previous order
selected.
- Check disk capacity.
- Check if there is a current order on the system, or if one is selected.
3201
RETRY INFORMATION\x0ANo
extra information available
3202
RETRY INFORMATION\x0AHead
: %1\x0ASection : %2\x0AFeeder :
%3\x0AChannel :
%4\x0AComponent : %5\x0A
3203
RETRY
INFORMATION\x0ASection :
%1\x0AFeeder : %2\x0AChannel :
%3\x0AToolbit : %4\x0ANozzle :
%5\x0AVacuum specified :
%6\x0AVacuum measured :
%7\x0AComponent : %8\x0A
3204 The recovery action failed
One or more errors (possible the
same as the original one(s))
occurred during the error recovery
action.
3205
Head: %1\x0ASection:
%2\x0AFeeder: %3\x0AChannel:
%4\x0AComponent:
%5\x0APackage: %6\x0A
3206
RETRY INFORMATION\x0AHead:
%1\x0ASection: %2\x0AFeeder:
%3\x0AChannel:
%4\x0AComponent:
%5\x0APackage: %6\x0A
3207 No active MIS period available
There is no active MIS period, so
the operation cannot be executed.
- The current MIS period is not started yet.
- Inconsistency in internal administration.
- Start production and enter a board.
- Delete current order, start new order and resume production.
3208
Measured: %1 mm.\x0ALower
limit: %2 mm.\x0AUpper limit: %3
mm.\x0A
3209
RETRY
INFORMATION\x0AMeasured:
%1 mm.\x0ALower limit: %2
mm.\x0AUpper limit: %3 mm.\x0A
3210
RVS :\tthis function (%d) has not
been implemented (yet).
A function was activated that has
not been implemented in the
current software version.
- Functions that are not complete yet should not be accessible
for the user.
- By mistake, this function is accessible for the user.
- Clear the error and do not use the functions again.
- Report the error to your service representative.
3211
RVS :\t system communication
error on: %d. A system error occurred. Unknown.
- Retry and continue.
- Restart the system.
- Report error to your service representative.
3212
Component description
incompatible with CA-camera type
The component description is
incompatible with the CA-camera
used.
- The component type is specified for use on only one of the
camera types (LFOV-SFOV) and an attempts is made to use
the component with the other camera type.
- Use the appropriate camera type, or
- Modify the component description.
3213
Error in merging vision data with
action spec data.
Unable to update action spec with
modified vision data. - Not consistent system data.
- Remove order from system.
- If this problem occurs frequently, contact service representative.
3214 %1 :\tFeedback error lift The lift servo loop is not closed.
- Defective cabling to motor or encoder.
- Defective motor or encoder.
- Defective motor controller.
- Defective driver board Check possible causes.
3215 %1 :\tFeedback error puller The puller servo loop is not closed.
- Defective cabling to motor or encoder.
- Defective motor or encoder.
- Defective motor controller.
- Defective driver board. Check possible causes.
3216 %1 :\tFeedback error snapin The snapin loop is not closed.
- Defective cabling to motor or encoder.
- Defective motor or encoder.
- Defective motor controller.
- Defective driver board. Check possible causes.
3217 %1 :\tCarrier not safe for move lift
Carrier is not positioned well on
the lift, after the carrier was in the
position to pick components out of
it.
- Carrier lost from puller tip.
- Sensor B3 not well adjusted. Check state of puller tip.
3218
%1 : Wafer handler
communication error
Error communicating with wafer
handler feedsection
- Hadware or software connection error
- Communication protocol error
- Check RS 232 connection between wafer handler section and machine
- Check communication port configuration
- Retry the operation
- If not correct, contact your service representative
3219 %1 : Wafer handler data error
Invailid message data for the
wafer handler feedsection is sent
or received
Communication protocol error, the data does not comply with
the communication interface of the wafer handler section
- Make a logdisk as described in the Service Manual
- Report error to your service representative
3220
%1 : Wafer handler command
failure
Reply message data of wafer
handler feedsection data indicates
operation failure Wafer handler is in wrong state
- Check wafer handler module for errors, warnings, etc.
- Retry the operation
- If not correct, make a logdisk as described in the Service Manual
- Restart the system
3221
%1 : Wafer handler servo power
failure
Servo power of wafer handler
feedsection can't be turned on/off Wafer handler is in wrong state
- Check wafer handler module for errors, warnings, etc.
- Retry the operation
- If not correct, restart the system
3222
%1 : Unable to remove wafer while
homing all wafer handler axes
Wafer handler feedsection cannot
home all axes Selected wafer cannot be removed
- Check wafer handler module for errors, warnings, etc.
- Retry the operation
- If not correct, restart the system
3223
%1 : Unsafe to home all wafer
handler axes
Wafer handler feedsection cannot
home all axes It is not safe now to home all the wafer handler's axes
- Check wafer handler module for errors, warnings, etc.
- Retry the operation
- If not correct, restart the system