00191494-01.pdf - 第74页
Error Messages Short Reference SIPLACE 80 S-15/F3/G 03/99 Issue Software Version SR.010.x x 72 744 LRS: Command not in comman d list CAUSE ● LR SEND incorrect comm and received REMEDY ● If possible, ignore. 745 LRS: Conv…
Short Reference SIPLACE 80 S-15/F3/G Error Messages
03/99 Issue Software Version SR.010.xx
71
736 GK: Error in local machine data
CAUSE
● There are no real or current machine data on the hard disk; the machine data cannot be conver-
ted due to a structure error.
REMEDY
● Write the MA data onto the hard disk properly.
737 GK: Error in machine data
CAUSE
● The MA data (ideal) coming from the line computer cannot be converted.
REMEDY
● The correct data format must be sent.
738 GK: Error in set-up data
CAUSE
● The set-up data coming from the line computer cannot be converted.
REMEDY
● The correct data format must be sent.
739 GK: Error in cluster data
CAUSE
● The cluster data coming from the line computer cannot be converted.
REMEDY
● The correct data format must be sent.
740 GK: Error in fiducial data
CAUSE
● The fiducial data coming from the line computer cannot be converted.
REMEDY
● The correct data format must be sent.
741 GK: Error in package form data
CAUSE
● The package form data coming from the line computer cannot be converted.
REMEDY
● The correct data format must be sent.
742 LRS: Timeout during transmission to line computer
CAUSE
● Released through IEC bus
REMEDY
● Reboot
Error Messages Short Reference SIPLACE 80 S-15/F3/G
03/99 Issue Software Version SR.010.xx
72
744 LRS: Command not in command list
CAUSE
● LR SEND incorrect command received
REMEDY
● If possible, ignore.
745 LRS: Conversion is not possible
CAUSE
● Could not convert data for line computer telegrams SABR/SBES.
REMEDY
● No
746 LRS: No communication with line computer
CAUSE
● IEC bus is "blocked"
REMEDY
● Reboot station and line computers.
747 DP: Data limits exceeded
CAUSE
● Incorrect date input
REMEDY
● Correct input date
748 DP: required equipment unknown
CAUSE
● Possibly the TASKS.CFG file has been changed, or there is a software fault
REMEDY
● Reboot with the supplied version of TASKS.CFG ; if necessary, notify Siemens Service.
749 No PCB barcode read
CAUSE
● Barcode reader has been activated but barcode was not recognized
REMEDY
● Make sure the barcode type is correct; make sure the mechanical distance is correct
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)
Short Reference SIPLACE 80 S-15/F3/G Error Messages
03/99 Issue Software Version SR.010.xx
73
751 Data preparation : run error
CAUSE
● If there was previously an error in the placement data (MK/GF/RU/NU files) all other telegrams
coming 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; rein-
stall 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.
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.
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.