FUJI错误代码查询.pdf - 第2251页
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 ma…
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 页
Display: A board type was reported in the middle of changeover.
Used by:
Cause: Processing was cancelled because the next board type was reported during changeover.
Remedy:
------------------------------
Code: 51??4033
Display: Changeover has been executed even though the board type has not been reported.
Used by:
Cause: The changeover response has been executed even though the board type has not been reported.
Remedy: Get a verification of the board type report for a second time.
------------------------------
Code: 51??4034
Display: The machine has already timed out.
Used by:
Cause: A command to enter changeover has been executed for a machine that has already timed out.
Remedy: After executing board type verification, it is necessary that the command to enter changeover is
executed within a set amount of time.
------------------------------
Code: 51??4035
Display: Board type verification has already been completed.
Used by:
Cause: Board type verification has been executed using the same changeover ID for a machine that has
already executed the board type verification.
Remedy: Check the changeover ID value.
------------------------------
Code: 51??4036
Display: The command to enter changeover has been executed multiple times.
Used by:
Cause: The command to enter changeover has been executed multiple times on the same machine using
the same changeover ID.
Remedy: Check the changeover ID value.
------------------------------
Code: 51??4037
Display: The verification code value of the board type verification is incorrect.
Used by:
Cause: The verification code value of the board type verification has been specified as some value outside
the range of 0 - 4.
Remedy: Check the verification code value of the board type verification
------------------------------
Code: 51??4038
Display: The changeover ID value is incorrect.
Used by:
Cause: The changeover ID value has been specified as some value outside the range of 0 - FFFF.
Remedy: Check the changeover ID value.
------------------------------
Code: 51??4039
Display: The machine has already timed out.
Used by:
Cause: A command to execute board type verification has been executed for a machine that has already
timed out.
Remedy: After reporting the board type, it is necessary that the command to execute board type
第 2252 页