00191025-01.pdf - 第670页

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 - 83 756 Data preparation : error in fiducial data CAUSE ● MK cou ld not be con verted. REMEDY ● If t…

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 - 82
750 Data preparation : internal error
CAUSE
●
Not possible to write to station computer hard disk.
REMEDY
●
Check disk; disk full?; files write-protected ? (check *.MA, *.GF, *.NU, *.RU)
751 Data preparation : run error
CAUSE
●
If there was previously an error in the placement data (MK/GF/RU/NU files) all other telegrams com-
ing from the line computer will be discarded and in each case a message generated.
REMEDY
●
Reboot station (a great deal of specialist knowledge is required for precise identification of this fault).
752 Data preparation : error in machine data
CAUSE
●
It was not possible to convert the MA data (files AKTUELL.MA, REAL.MA, IDEAL.MA, RASTER.P1,
RASTER.P2).
REMEDY
●
Check the hard disk for bad clusters with the DOS program using the CHKDSK command; reinstall
machine data (files) onto the hard disk.
753 Data preparation : error in cluster data
CAUSE
●
It was not possible to convert the NU data.
REMEDY
●
The line computer has generated a faulty cluster, check data in line computer.
754 Data preparation : error in set-up data
CAUSE
●
It was not possible to convert the RU data.
REMEDY
●
The line computer has generated a faulty set-up, check data in line computer.
755 Data preparation : error in package form data
CAUSE
●
GF could not be converted.
REMEDY
●
Check GF in the line computer.
SIPLACE 80S/F/G User’s Manual 19 Error Messages
Edition 12/96 from Software Version SR.009.xx 19.1 Error Messages
19 - 83
756 Data preparation : error in fiducial data
CAUSE
●
MK could not be converted.
REMEDY
●
If this occurs only with a pure SIPLACE line (with MVS) it is best simply to reteach the MK.
757 Data preparation : error in fiducial list
CAUSE
●
Does not occur.
REMEDY
●
758 LR: Error reading telegram
CAUSE
●
Separators or value fields in the line computer telegram are incorrect or overrun.
REMEDY
●
Check hard disk of the station (MS-DOS CHKDSK); reboot.
759 LR: Error in telegram output
CAUSE
●
Does not occur
REMEDY
●
760 LR: Error during telegram treatment
CAUSE
●
Does not occur.
REMEDY
●
761 LR: No memory, task stopped
CAUSE
●
Memory of the station is not fragmented.
REMEDY
●
Reboot station.
762 VS: Maximal gradient number of fiducial profile exceeded
CAUSE
●
Fiducial structure with poor contrast value as background; horizontal / vertical fiducial profile which
contains more than 100 gradients which reach 20% of maximum gradients.
REMEDY
●
Reduce template field, select another fiducial structure.
19 Error Messages SIPLACE 80S/F/G User’s Manual
19.1 Error Messages Edition 12/96 from Software Version SR.009.xx
19 - 84
763 BO: Error dur. memory request f. text pool (no./length)
CAUSE
●
System error, not enough memory available.
REMEDY
●
764 BO: Cannot open text file
CAUSE
●
Text file not found.
REMEDY
●
The name of the text file is in the file C:\Texte\SITXT.CFG. If this file does not exist, the software
must be reinstalled.
765 BO: Text index too large (text index/max index)
CAUSE
●
A text in the text file is too large.
REMEDY
●
Ignore but inform AUT 5 BSM 14 Development.
766 BO: Text index defined twice (text index/i. )
CAUSE
●
On loading texts, double text indices were detected. Loading is repeated.
REMEDY
●
Ignore, but inform AUT 5 BSM 14 Development.
767 PCB barcode: incorrect format
CAUSE
●
The machine has not identified the board barcode received from the barcode reader.
REMEDY
●
Input manually via the keyboard or try again. Once placement of the current board is complete the
error menu will drop down.
768 No data received from PCB barcode reader
CAUSE
●
PCB barcode reader not responding.
REMEDY
●
Check PCB barcode reader.