00191025-01 - 第684页

SIPLACE 80S/F/G User’s Manual 19 Error Message s Edition 12/96 from S oftware Version SR.009.xx 19.1 Error Messages 19 - 97 852 DP: Cannot save current MA data CAUSE ● Not poss ible to c hange or r ewrite the ak tuell.ma…

100%1 / 736
19 Error Messages SIPLACE 80S/F/G User’s Manual
19.1 Error Messages Edition 12/96 from Software Version SR.009.xx
19 - 96
845 DP: Head in local files wrong or incomplete
CAUSE
●
Incorrect head entered in machine data
REMEDY
●
Check machine data
846 DP: Loading of pack. form or fid. data not successful
CAUSE
●
Error while reading and loading the package form or fiducial data.
REMEDY
●
Data of package form and fiducial file should be checked
847 DP: Error in list for passpoint sets and fiducials
CAUSE
●
Error in real.ma and fiducial file
REMEDY
●
Data in real and fiducial files should be checked
848 Cannot save current MA data
CAUSE
●
Changing and rewriting aktuell.ma is not possible
REMEDY
●
Hard disk should be checked
849 VKL file cannot be stored
CAUSE
●
Not possible to rewrite the *.VKL file
REMEDY
●
Hard disk should be checked
850 Process data cannot be stored
CAUSE
●
Not possible to rewrite the glueing head process switches (C:\TMP\VL_PDAT.K1/2/3)
REMEDY
●
Hard disk should be checked
851 Process data cannot be read
CAUSE
●
1. At first time still no process data found
2. Error occurred during read
REMEDY
●
To 1. Not an error
To 2. File and hard disk should be checked
SIPLACE 80S/F/G User’s Manual 19 Error Messages
Edition 12/96 from Software Version SR.009.xx 19.1 Error Messages
19 - 97
852 DP: Cannot save current MA data
CAUSE
●
Not possible to change or rewrite the aktuell.ma file
REMEDY
●
Hard disk should be checked
853 MA data: Invalid fiducial number for system fiducial
CAUSE
●
System fiducials must lie within the range 250 to 255
REMEDY
●
Correct the fiducial data in the MA data or set-up.
854 MA data: Error in sensor system types
CAUSE
●
Different sensor system types, or invalid for machine, in real.ma and ideal.ma
quoted (line computer telegram).
REMEDY
●
Make data consistent.
855 MA data: Missing height offset
CAUSE
●
Height offset not entered in real.ma.
REMEDY
●
Measure height offset and enter in real.ma.
856 MA data: Too many zero point fiducials
CAUSE
●
More than one zero point fiducial has been entered in ideal.ma.
REMEDY
●
Enter one fiducial only.
857 MA data: Mapping plate irregular
CAUSE
●
Irregular mapping plate is not supported.
REMEDY
●
Raster.px file should be checked; if necessary, remeasure
858 MA data: Error in nozzle type/vacuum correction values
CAUSE
●
For nozzle type in aktuell.ma no vacuum correction values can be found.
REMEDY
●
Enter valid nozzle type in aktuell.ma.
19 Error Messages SIPLACE 80S/F/G User’s Manual
19.1 Error Messages Edition 12/96 from Software Version SR.009.xx
19 - 98
859 MA data: Invalid compartment at nozzle changer
CAUSE
●
An invalid compartment number has been entered in aktuell.ma or real.ma
REMEDY
●
Make the data consistent again.
860 MA data: Unknown nozzle changer type
CAUSE
●
An invalid nozzle changer type has been specified in aktuell.ma or real.ma.
REMEDY
●
Make the data consistent again.
861 Cluster data: Error in nozzle type/vacuum correction values
CAUSE
●
Error must not occur; for the nozzle type specified in the cluster nozzle type there are no vacuum
correction values in ideal.ma.
REMEDY
●
Check consistency in the line computer.
862 Cluster data: Error in chain of placement positions
CAUSE
●
Error in the line computer telegram for cluster
REMEDY
●
Cluster should be checked in the line computer ; if necessary, compile again (feasibility)
863 Cluster data: Error in passpoint sets
CAUSE
●
Error in the line computer telegram for cluster.
REMEDY
●
Cluster should be checked in the line computer; if necessary, compile again (feasibility).
864 Cluster data: incorrect track number
CAUSE
●
Incorrect track number in cluster or set-up.
REMEDY
●
Cluster and set-up should be checked in the line computer; feasibility.
865 Cluster data: Error during creation of fiducial list
CAUSE
●
Software error
REMEDY
●
AUT 5 BSM 14 Development should be notified.