FUJI错误代码查询.pdf - 第1907页
comment in question will be separated as a non-fixed feeder. Remedy: Specify a feeder position within the feeder station's range. ------------------------------ Code: 210060A9 Display: "There is insufficient sp…
Cause: Devices cannot be satisfactorily arranged at the IP3.
Remedy: There are devices in the source program that cannot be placed to the IP3. Fix these at the editor
and reboot.
------------------------------
Code: 210060A2
Display: Information table memory allocation error
Used by:
Cause: The IP3 information table could not be saved.
Remedy: Reboot MCS.
------------------------------
Code: 210060A3
Display: GL_generator error abort
Used by:
Cause: GL generation was aborted due to an error.
Remedy: Proceed depending on the error which occurred during GL generation.
------------------------------
Code: 210060A4
Display: "M/C Nickname is duplicated."
Used by:
Cause: The same machine nickname has been registered more than once in the line descriptor or the
offline descriptor.
Remedy: Make sure that the same machine nickname is not duplicated in the line descriptor or the offline
descriptor.
------------------------------
Code: 210060A5
Display: "M/C type is not specified."
Used by:
Cause: The offline descriptor contains a machine type that does not correspond to any of the machine
types defined in MCS/2.
Remedy: Change the machine type in the offline descriptor to one defined in MCS/2. Refer to the MCS/2
manual for details on defined machine types.
------------------------------
Code: 210060A6
Display: "Feeder specified as "Fix" in PT file can't be used."
Used by:
Cause: A feeder specified as a fixed device in the PST file cannot be used on the machine for which
separation is being performed.
Remedy: Change the feeder type in the relevant device comment to one that can be used by the machine
specified in the PST file.
------------------------------
Code: 210060A7
Display: "Feeder type for comment isn't specified in PT file."
Used by:
Cause: The feeder type cannot be determined, because the feeder type has not been entered in the device
comment field of the PST file. The feeder type will be determined based on the Part data.
Remedy: Enter the feeder type in the relevant device comment field of the PST file.
------------------------------
Code: 210060A8
Display: "Feeder position in PT file is out of range."
Used by:
Cause: A feeder position specified as fixed in the PST file is outside the feeder station range. The device
第 1906 页
comment in question will be separated as a non-fixed feeder.
Remedy: Specify a feeder position within the feeder station's range.
------------------------------
Code: 210060A9
Display: "There is insufficient space for a feeder in PT file."
Used by:
Cause: An attempt was made to allocate the feeder in question as specified by the PST file, but an error
occurred when the feeder width was checked against the end of the station. The feeder in question will be
separated as a non-fixed feeder.
Remedy: Change the PST specification number of the feeder in question.
------------------------------
Code: 210060AA
Display: "Space between feeders in PT file is insufficient."
Used by:
Cause: An attempt was made to allocate the feeder in question as specified by the PST file, but an error
occurred due to interference between feeders.
Remedy: Change the PST specification number of the feeder in question.
------------------------------
Code: 21006400
Display: syntax error - illegal '+' option
Used by:
Cause: An illegal '+' option was specified at start-up.
Remedy: Check the specified option.
------------------------------
Code: 21006401
Display: can't read strings file
Used by:
Cause: The string file couldn't be loaded into the memory.
Remedy: Re-install the software.
------------------------------
Code: 21006402
Display: program file not found
Used by:
Cause: The specified production program name was not found.
Remedy: Check the production programs.
------------------------------
Code: 21006403
Display: change console path error
Used by:
Cause: During operation, the specified terminal path could not be changed.
Remedy: Re-boot MCS.
------------------------------
Code: 21006404
Display: CRT event link error
Used by:
Cause: The terminal event could not be linked.
Remedy: Re-boot MCS.
------------------------------
Code: 21006405
Display: can't fork Ls task
Used by:
第 1907 页
Cause: The Ls task could not be started up.
Remedy: Re-execute the function. If it still doesn't work, re-install the software.
------------------------------
Code: 21006406
Display: can't create Ls task pipe
Used by:
Cause: The Ls task pipe could not be created.
Remedy: Re-boot MCS.
------------------------------
Code: 21006407
Display: can't read Ls task pipe
Used by:
Cause: The Ls task pipe could not be read.
Remedy: Re-execute the function. If it still doesn't work, re-install the software.
------------------------------
Code: 21006408
Display: can't load program
Used by:
Cause: The specified production program couldn't be read.
Remedy: Check the file.
------------------------------
Code: 21006409
Display: can't load old permanent set table
Used by:
Cause: The specified permanent set table could not be read.
Remedy: Check the file.
------------------------------
Code: 2100640A
Display: can't get work memory
Used by:
Cause: The working memory could not be recalled.
Remedy: Re-boot MCS.
------------------------------
Code: 2100640B
Display: WARNING!! D_no.:PT data already exists
Used by:
Cause: The device number in the production program is the same as in the previous permanent set table.
Remedy: This is a warning. It is not an error message. It has no effect on processing. Check the device
numbers in the production program.
------------------------------
Code: 2100640C
Display: can't open program file
Used by:
Cause: The specified program file cannot be opened.
Remedy: Check the file.
------------------------------
Code: 2100640D
Display: can't read program file
Used by:
Cause: The specified program file cannot be read.
Remedy: Check the file.
第 1908 页