GL541操作手册.pdf - 第220页
Part 6 6 - 5 V ersion 2.0 Chapter 1 Errors Displayed by the GL-541E 0003 Cause: The mark-reading sequence that should be referred to comes after the glue sequences in the sequence data. Remedy: Using the F4G program edit…
Chapter 1 Errors Displayed by the GL-541E
Part 6
Program
Cause:
(1) If the axis and direction are displayed:
A coordinate value in the program exceeds the range specified by the travel limit in
Proper data.
(2) If an error code is displayed:
The program contains an error or there is an error in the machine operation method.
Remedy: Verify the sequence in which the error has occurred and check the
program.
If the program contains an error, correct the error and transmit the
program to the machine again.
• Travel_limit range
Proper data
X-axis maximum value: 66900 - Travel_limit_max.X (Unit is pulses)
X-axis minimum value: -1400 - Travel_limit_min.X
Y-axis maximum value: 39400 + Travel_limit_max.Y
Y-axis minimum value: -1400 + Travel_limit_min.Y
• Error Codes
0001
Cause: The head number (“Head #”) is not input in the sequence
data.
Remedy: Input head number “Head #” into the sequence data with
the F4G program editor, then retransmit the program to the
machine.
0002
Cause: The specific glue sequence referred to is not a mark-reading
sequence.
Remedy: Enter the information necessary to make the sequence in
question a mark-reading sequence and then retransmit the
program to the machine.
6 - 4
Version 2.0
GL-541E Operation
Part 6
6 - 5
Version 2.0
Chapter 1 Errors Displayed by the GL-541E
0003
Cause: The mark-reading sequence that should be referred to comes
after the glue sequences in the sequence data.
Remedy: Using the F4G program editor, input the mark-reading
sequence before the glue sequence data and then retransmit
the program to the machine.
0004
Cause: The mark-reading sequence that should be referred to is
skipped.
Remedy: Using the F4G program editor, cancel the mark-reading
sequence skip flag or create a new mark-reading sequence.
Then retransmit the program to the machine.
0010
Cause: An attempt was made to execute glue sequences either
without executing the required mark-reading sequences or
after a mark-reading sequence error had occurred.
Remedy: If there is no mark-reading sequence, use the F4G program
editor to set such a sequence. If the mark-reading sequence
has stopped because of an error then execute the sequence
again.
0011
Cause: The fiducial marks specified in the “M Mark #” and “S Mark
#” columns of a glue sequence do not exist.
Remedy: Using the F4G program editor, check the relevant columns
for the sequences in question in mark data.
Either the mark-reading sequences must have the same block
number “Block #” as the glue sequences they refer to, or the
mark-reading sequences must have block number zero.
0020
Cause: G data has not been input in a glue sequence.
Remedy: Input G data into the glue sequence using the F4G program
editor, then retransmit the program to the machine.
GL-541E Operation
Chapter 1 Errors Displayed by the GL-541E
Part 6
PCB Transport Error: #
Cause: A board could not be properly transported on the conveyor
indicated by #.
Remedy: Transmit Proper and status data to the machine. The conveyor types which
may be indicated by # are identified below.
“Prev.” — Previous stage conveyor
“MCID” — MCID conveyor
“IN” — In-conveyor
“OUT” — Out-conveyor
“NEXT” — Next stage conveyor
PCB Stopper Error
Cause: The upper or lower limit sensor for the board stopper has not been tripped
within 5 seconds after the board stopper has been signaled to rise or drop.
Remedy: Check for foreign objects (for example, a board) that may hinder stopper
movement.
If such a foreign object is found, remove it. If no such object is found check
the stopper upper and lower limit sensors using the I/O board. For details
on performing checks with the I/O map, refer to Part 3, “Description of
Commands” and to Appendix A concerning the GL-541E I/O map. For
further information on sensor adjustment procedures see the
GL-541E Maintenance Manual.
PCB Setting Error
Cause: If a board is on the main conveyor an attempt to load a board has been
made. If a board is not presently on the main conveyor then an attempt to
unload a board has been made.
Remedy: Check the condition of the main conveyor for any unnatural movement. If
no such movement is found, check the MAIN ARRV CHK sensor on the
main conveyor using the I/O check function.
For details on performing checks with the I/O map, refer to Part 3,
“Description of Commands” and to Appendix A concerning the GL-541E
I/O map. For further information on sensor adjustment procedures see the
GL-541E Maintenance Manual.
Conv. PLC Alarm
Cause: The CPU module (board loader PLC) is not working properly.
Remedy: Contact Fuji.
6 - 6
Version 2.0
GL-541E Operation