ERR-LIST-ACM - 第41页

3104 %1 :\tInvalid bitbus node in module configuration file The configuration file is not correct. - Illegal update of the configuration file. - Re-install software. 3105 %1 :\tFirmware to download to controller not foun…

100%1 / 52
3020 %1 :\tXY-calibration table errors
During X-Y calibration errors are
detected. - Distorted markers on calibration plate. - Fix calibration table.
3021 %1 :\tTransport error
The transport module does not
respond correctly. - Incorrectly installed transport system. - Check transport module.
3022 %1 :\tToolbit present
A toolbit is attached in the head.
For this calibration no toolbit must
be attached. - Toolbit attached. - Detach toolbit.
3023 %1 :\tVacuum flow too high
The vacuum calibration, executed
on a head without a nozzle, gives
a value which is too high. - Filthiness of the measurement restriction. - Check vacuum system (especially the measurement restriction).
3024 %1 :\tNothing to repair
The X-Y calibration is correct, no
extra actions are needed. - Calibration is correct. - None.
3025
%1 :\tNo calibration nozzle at front
side
The calibration nozzle, needed at
front side head, is not mounted. - Not or incorrectly mounted nozzle. - Mount calibration nozzle at front size.
3026 %1 :\tNo rear nozzle
The calibration nozzle, needed at
rear side head, is not mounted. - No or incorrectly mounted nozzle. - Mount calibration nozzle at rear side
3027 %1 :\tCA Camera not configured
The camera needed for calibration
is not configured - Non-configured camera. - Configure camera in human interface (SETUP-CONFIGURATION).
3028
%1 :\tToolbit eccentricity is out of
tolerance - Change toolbit.
3029 %1 :\tZ-Level calibration failed Z-Level calibration failed.
- If head, then head not correctly mounted on the machine.
- If feeder section, then feederbank/trolley not correctly
mounted on the machine.
- Check height of the subframe.
- Re-adjust.
3030 %1 :\tForce table calibration failed Force table calibration failed. - Hardware error.
- Check hardware.
- Retry action. If not correct, contact your service representative.
3031
XY-Calibration plate reference
marker not found
The marker on the XY-Reference
plate could not be located. - Marker is damaged. - Check marker.
3032 %1 :\tPlacement action interrupted
The placement action is
interrupted due to a machine
failure. This may have led to a
wrong placement. - Machine error.
- Check if component was placed correctly. If so, select skip action, otherwise
select retry.
3033 %1 :\tVacuum flow too low
The vacuum calibration, executed
on a head without a nozzle, gives
a value which is too low.
- Obstruction in vacuum system.
- Obstruction in pipette.
- Jammed vacuum tube. - Check pipette and vacuum system.
3034
Calibration slide temp tolerance
error Temperature tolerance error. - Temperature under 0 Celcius or above 60 Celcius. - Report error to your service representative.
3100
%1 :\tModule configuration file
missing on aPC
The configuration data needed for
this module is not available.
- Incorrect installation.
- Files removed from the filesystem. - Re-install software.
3101
%1 :\tInvalid configuration file:
Invalid syntax version
The installed configuration file has
an illegal syntax number. - The installation is not executed properly. - Re-install software.
3102
%1 :\tInvalid module configuration
file: Section missing
The configuration file for this
module is not correct.
- Incorrect installation.
- Files removed from the filesystem. - Re-install software
3103
%1 :\tInvalid module configuration
file: Entry missing
The configuration file for this
module is not correct.
- Incorrect installation
- Files removed from the filesystem - Re-install software
3104
%1 :\tInvalid bitbus node in
module configuration file
The configuration file is not
correct. - Illegal update of the configuration file. - Re-install software.
3105
%1 :\tFirmware to download to
controller not found by module Firmware not available. - Installation not executed correctly. - Re-install software.
3106
%1 :\tError found in firmware
during download to controller
Error found in firmware during
download to controller. - Illegal or incorrect firmware file Re-install software.
3107
%1 :\tUsage requested on a not
configured module
The module on which the action is
requested, is not yet configured.
- Mismatch in configuration files.
- Illegal updated files. - Configure module.
3108
%1 :\tUsage requested on a not
calibrated module
The module on which an action is
requested is not yet calibrated. - Not calibrated module. - Calibrate module (exchange calibration).
3109 %1 :\tModule failed to startup The module can not be started. - Hardware or software problems with module.
- Re-configure modules.
- Exchange module.
3110
%1 :\tModule failed to gain the
requested amount of memory Not enough memory available. - Too much programs loaded in memory.
- Temporary solution:
- Configure only the needed modules.
3111
%1 :\tError in action spec: Invalid
fiducial algorithm
The fiducial algorithm defined in
the action spec is not correct. - Illegal action spec.
- Check action spec.
- See action spec documentation.
3112
%1 :\tError in action spec: To
many fiducials for requested
algorithm
A limited number of fiducials can
be applied for correction. - Incorrect action spec. - Verify action spec.
3113
%1 :\tError in action spec: Not
enough fiducials for requested
algorithm
For fiducial correction at least 1, 2
or 3 fiducials are needed (#
depends from algorithm). - Incorrect action spec. - Check action spec.
3114
%1 :\tError in action spec: Invalid
Global fiducial usage
The global fiducial used is not
correct. - Incorrect action spec. - Check action spec.
3115
%1 :\tError in action spec: Not all
fiducials from a matrix measured
with same FA
For proper working of the
machine, all fiducials used within
set (i.. global fiducials)
must be measured with the same
camera. - Incorrect action spec. - Modify action spec.
3116 %1 :\tModule failed to initialize
The indicated module could not be
initialized. - Hardware error. - Remove module from configuration and re-configure.
3117
%1 :\tAction refused by module:
Module in wrong state
The requested action for a module
is not executed. - The module is in a state in which these actions are prohibited. - Retry the action.
3118
%1 :\tAction refused: wrong
module specified
During execution of the action
specification a illegal module was
specified. - Incorrect action spec.
- Check action spec.
- Verify action spec using single step.
3119 %1 :\tAction refused: Invalid data
The data needed to execute the
action is not correct.
- CA-files missing.
- Action spec error.
- Check if the required CA-file is at the aPC.
- Check action spec.
3120
%1 :\tAction refused: No Z
movement allowed in current state
The requested head Z-movement
is not allowed in this machine
state. - Software error. - Retry.
3121
%1 :\tNo communication to
module allowed
Communication to the requested
module is not allowed. - The module can not be used. - Restart the system.
3122
%1 :\tTimeout occurred during
requested action on module
The requested action for a module
is not executed, the module does
not respond within a pre-defined
time window.
- Communication error with module
- Hardware/software of module
- If module is a traytrolley, then it could be that the laser beam (
front/rear) is obstructed.
- Retry if possible.
- Restart the system.
- If module is a traytrolley, then check if all carriers are correct positioned in the
trolley, so that both laser beams (front/rear) are OK.
3123 %1 :\tToolbit not attached
The needed toolbit for production
is not attached to head or the
toolbit file is not correct.
- The correct toolbit is not attached
- Illegal updated toolbit file
- Not correct installed toolbit file
- Attach toolbit to head
- Re-install toolbit file
3124
%1 :\tUnexpected error occurred
in Module
The indicated module could not be
initialized. - Error on module. - Remove module from configuration and re-configure.
3125
%1 :\tController detected error
during action Internal software error. - Retry.
3126 %1 :\tController is in wrong state Internal software error. - Retry.
3127
%1 :\tIncorrect parameter sent to
controller
Control software sent incorrect
data to controller.
- Incorrect action spec (feeder 0 specified).
- Incorrect firmware.
- Check action spec.
- Check firmware version.
3128
%1 :\tThe firmware command is
not yet supported
A command is given to firmware
that is not implemented yet, or is
unknown. - Not documented commands are used. - Use correct commands.
3129 %1 :\tFirmware refused
The firmware specified in the
configuration is not correct. - Illegal update of firmware. - Re-install software.
3130
%1 :\tUnsupported command is
given to the controller
An unsupported command is given
to the controller. - Internal software error. - Report error to your service representative.
3131
%1 :\tController timed out during
action
The controller response is not
within a certain time window.
- Incorrect movement class.
- Incorrect speed mode.
- Check action spec.
- Check package type database.
3132 %1 :\tIncorrect toolbit type in head Unknown toolbit inserted in head. - Unsupported toolbit type inserted in head. - Replace toolbit with correct one.
3133 %1 :\tbitbus node not found The bitbus node is not found. - Module not connected to bitbus. - Check bitbus connection cable.
3134
%1 :\tNot able to disconnect
controllers Not able to disconnect controllers.
- Bitbus error.
- Software error.
- Shutdown system.
- Restart the system.
3135
%1 :\tPosition of servo system
outside limits
One or more servo systems were
attempted to move outside it
physical range or the tolerance on
the nominal position is too large.
- An error in the action spec.
- Calibration error.
- Mechanical adjustment incorrect.
- Check the action spec.
- Calibrate the specific module.
- Re-adjust and calibrate module.
3136 General servo power failure
All conditions for having servo
power are met but there's no servo
power present
( covers are closed,
feedersections are present, no
mains phase failure, no
emergency buttons pressed )
- Servo power not activated ( yet )
- Defective CAN card, defective LIMMS controller or missing
CAN terminator
- Power failure, defective power supply
- Press 'Servo power On' button
- Check aPC errors, see error descriptions in the Service Manual ( contact your
service representative in case of doubts )
- Check leds on LIMMS Power Supply, see Service Manual
- Check fuses, power supply and safety rel
3137
Invalid or inconsistent SBIP entry
parameters
SBIP encountered invalid
parameter values.
- Component id not known by SBIP.
- Component / fiducial file to download not found on APC.
- Illegal component type specified in component description.
- Check component / fiducial file descriptions.
- Report error to your service representative.
3138 Spurious SBIP error encountered
An unidentified error occurred on
the SBIP.
- Retry action.
- Check vision file.
- Shutdown and restart the system.
- Report error to your service representative.