FUJI错误代码查询.pdf - 第2324页
Display: No reply from command server to the transmit OK request. Used by: Cause: An attempt was made to receive a reply from the command server to the transmit OK request but a read error occurred in the named pipe. Thi…
Display: No vQN line in "UNIT", "STATUS" - "BLOCK", "IMAGE-".
Used by:
Cause: The vQN line in "UNIT", "STATUS" - "BLOCK", "IMAGE-" in the specified transmission image type
status data was not found.
Remedy: Check the content of "UNIT", "STATUS" - "BLOCK", "IMAGE-" in the production program.
------------------------------
Code: 52??2111
Display: "UNIT", "STATUS" - "BLOCK", "HEADER-" format error.
Used by:
Cause: "UNIT", "STATUS" in the specified status data was read and a format error was detected in
"BLOCK", "HEADER-".
Remedy: Check the setting for "UNIT", "STATUS" - "BLOCK", "HEADER-" in the production program.
------------------------------
Code: 52??2112
Display: "UNIT", "STATUS" - "BLOCK", "STATDT-" format error.
Used by:
Cause: "UNIT", "STATUS" in the specified status data was read and a format error was detected in
"BLOCK", "STATDT-".
Remedy: Check the setting for "UNIT", "STATUS" - "BLOCK", "STATDT-" in status data.
------------------------------
Code: 52??4001
Display: Presently not used.
Used by:
Cause:
Remedy:
------------------------------
Code: 52??4002
Display: Presently not used.
Used by:
Cause:
Remedy:
------------------------------
Code: 52??4003
Display: The cell status is underfined.
Used by:
Cause: A board type report was confirmed for a machine with an underfined cell status.
Remedy: Request the cell status.
------------------------------
Code: 52??4004
Display: Named pipe could not be created.
Used by:
Cause: The named pipe used to read the CCPSS process could not be created or opened.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4005
Display: Remote command named pipe could not be opened.
Used by:
Cause: The named pipe used to read the remote command could not be opened.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4006
第 2323 页
Display: No reply from command server to the transmit OK request.
Used by:
Cause: An attempt was made to receive a reply from the command server to the transmit OK request but
a read error occurred in the named pipe. This error occurs if there is a named pipe read error or an
incorrect format for the transmit OK request, and may be caused by the C/C not operating properly.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4007
Display: Remote command did not start.
Used by:
Cause: An attempt was made to receive a startup report from the remote command but a read error
occurred in the named pipe. This error occurs if there is a named pipe read error and may be caused by
the C/C not operating properly.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4008
Display: Presently not used.
Used by:
Cause:
Remedy:
------------------------------
Code: 52??4009
Display: Command execution status could not be registered.
Used by:
Cause: The command execution status for the client process could not be registered. This error occurs if
either the named pipe for the client process cannot be opened or an error occurs when writing to the
named pipe, and may be caused by the C/C not operating properly.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4010
Display: Presently not used.
Used by:
Cause:
Remedy:
------------------------------
Code: 52??4011
Display: Named pipe could not be read.
Used by:
Cause: For some reason the named pipe could not be read.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4012
Display: SECS/GEM could not be initialized.
Used by:
Cause: For some reason SECS/GEM could not be initialized.
Remedy: Check that SECS/GEM is operating properly. Otherwise cease using SECS/GEM.
------------------------------
Code: 52??4013
Display: Command could not be started.
Used by:
Cause: The slave process could not be started. The cause may be one of the following: There is no
第 2324 页
command file, the command file is damaged, the directory storing the command has no path setting.
Remedy: Check the path setting or reinstall ProduSS.
------------------------------
Code: 52??4014
Display: Line descriptor data cannot be acquired.
Used by:
Cause: The line descriptor information created in the memory cannot be acquired. This error may be
caused by the C/C not operating properly.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4015
Display: Insufficient memory.
Used by:
Cause: The required memory space cannot be secured due to insufficient memory.
Remedy: Install more memory or halt the execution of processes which consume a lot of memory or
remove unnecessary modules from the memory.
------------------------------
Code: 52??4016
Display: Cannot connect.
Used by:
Cause: For some reason a connection cannot be made with ProduSS.
Remedy:
------------------------------
Code: 52??4017
Display: Cannot connect.
Used by:
Cause: It is not possible to connect because ProduSS has not been started.
Remedy: After checking that ProduSS has been started, execute the connect command.
------------------------------
Code: 52??4018
Display: The C/C settings was not found.
Used by:
Cause: The C/C setting data which was created in memory was not found. This error may be caused by
the C/C not operating properly.
Remedy: Switch the power off and then on.
------------------------------
Code: 52??4019
Display: Already connected.
Used by:
Cause: Connection has already been made with the specified machine.
Remedy:
------------------------------
Code: 52??4020
Display: Error ending machine.
Used by:
Cause: The connect or disconnect command was executed for several machines and a machine which
had made an error ending was discovered.
Remedy: The result code for each machine is reported as supplementary information. Check the machine
error codes.
------------------------------
Code: 52??4021
第 2325 页