FUJI错误代码查询.pdf - 第2250页

Remedy: ------------------------------ Code: 51??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, exe…

100%1 / 5282
Code: 51??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: 51??4010
Display: Presently not used.
Used by:
Cause:
Remedy:
------------------------------
Code: 51??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: 51??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: 51??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
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: 51??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: 51??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: 51??4016
Display: Cannot connect.
Used by:
Cause: For some reason a connection cannot be made with ProduSS.
第 2249 页
Remedy:
------------------------------
Code: 51??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: 51??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: 51??4019
Display: Already connected.
Used by:
Cause: Connection has already been made with the specified machine.
Remedy:
------------------------------
Code: 51??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: 51??4021
Display: Remote command canceled.
Used by:
Cause: The remote command was canceled due to the machine status.
Remedy:
------------------------------
Code: 51??4022
Display: Machine power off.
Used by:
Cause: The machine power may be off.
Remedy:
------------------------------
Code: 51??4023
Display: Production program name too long.
Used by:
Cause: The production program name is too long. The maximum length is 23 characters.
Remedy: Change the production program name so that it is within 23 characters.
------------------------------
Code: 51??4024
Display: Start instruction canceled.
Used by:
Cause: The start command was canceled (release). At present cancel is not supported for the start
第 2250 页
command.
Remedy:
------------------------------
Code: 51??4025
Display: The machine is already in a time up state.
Used by:
Cause: The board type report was confirmed(pcbconf)or a changeover executed(chgover)after the machine
for which the board type report was made was already in a time up state. Alternatively,the board type
report was confirmed several times for the same machine using the same changeover ID.
Remedy:
------------------------------
Code: 51??4026
Display: The machine is an active cell or a passive cell.
Used by:
Cause: A board type report was confirmed for the cell.
Remedy: Confirmation of a board type report is valid only for a unit.
------------------------------
Code: 51??4027
Display: A changeover ID different to the board type report from the unit was specified.
Used by:
Cause: An error was made when the changeover ID was entered,or the next board type report was
reported from the unit before the current board type report was confirmed.
Remedy: Check the Changeover ID.
------------------------------
Code: 51??4028
Display: A child process could not be ended when disconnection was performed.
Used by:
Cause: When disconnection was performed,a child process could not be normally ended and the child
process hung up.
Remedy:
------------------------------
Code: 51??4029
Display: The changeover command for that changeover ID has already been completed.
Used by:
Cause: A changeover instruction was executed using the same changeover ID.
Remedy:
------------------------------
Code: 51??4030
Display: This changeover ID is not valid.
Used by:
Cause: The changeover instruction(chgover)was executed after the changeover complete report was
received from the machine.
Remedy:
------------------------------
Code: 51??4031
Display: The cell status has been changed.
Used by:
Cause: Processing was initialized because the cell status was changed during changeover.
Remedy: Check the machine's cell status.
------------------------------
Code: 51??4032
第 2251 页