Appendix 1. Program Error
568
Error No.
Details
Remedy
P170
No offset number
The compensation No. (DOO‚ TOO‚ HOO)
command was not given when the radius
compensation (G41‚ G42‚ G43‚ G46)
command was issued. Alternatively‚ the
compensation No. is larger than the number
of sets in the specifications.
• Add the compensation No. command to the
compensation command block.
• Check the number of compensation No. sets
a correct it to a compensation No. command
within the permitted number of tool
compensation sets.
P171
No spec:Comp input by prog G10
Compensation data input by program (G10)
was commanded even though there is no
specification of compensation data input by
program.
• Check the specifications.
P172
G10 L number error
(G10 L-No. error)
The L address command is not correct when
the G10 command is issued.
• Check the address L-No. of the G10
command and correct the No.
P173
G10 P number error
(G10 compensation error)
When the G10 command is issued‚ a
compensation No. outside the permitted
number of sets in the specifications has been
commanded for the compensation No.
command.
• First check the number of compensation sets
and then set the address P designation to
within the permitted number of sets.
P174
No spec:Comp input by prog G11
Compensation data input by program cancel
(G11) was commanded even though there is
no specification of compensation data input
by program.
• Check the specifications.
P177
Tool life count active
Registration of tool life management data with
G10 was attempted when the used data count
valid signal was ON.
• The tool life management data cannot be
registered when counting the used data. Turn
the used data count valid signal OFF.
P178
Tool life data entry over
The number of registration groups‚ total
number of registered tools or the number of
registrations per group exceeded the
specifications range.
• Review the number of registrations.
P179
Illegal group No.
• When registering the tool life management
data with G10‚ the group No. was
commanded in duplicate.
• A group No. that was not registered was
designated during the T
99
command.
• An M code command must be issued as a
single command but coexists in the same
block as that of another M code command.
• The M code commands set in the same
group exist in the same block.
• The group No. cannot be commanded in
duplicate. When registering the group data‚
register it in group units.
• Correct to the correct group No.
P180
No spec: Drilling cycle
A fixed cycle command was issued though
there are not fixed cycle (G72 - G89)
specifications.
• Check the specifications.
• Correct the program.