clay
2006-10-29 05:18:51 UTC
I have a Fanuc OT-Mate control on a lathe. Today, when uploading code,
there was an error, that Ihave never had before. I also couldn't run the
last two programs that were already in the control. They worked a few
weeks ago, but now they error out on the comment lines. It works fine
with a comment / by itself, but as soon as I put any characters behind
it, I get the alarm.
Here is a snippet of the code:
%
O4805
N100 G20
/CNMG/ <--- here is where it was choking
N102 G0 X1.0 Z6.0
N104 G0 T0303 M42
the fanuc errors were either PS 005 for the newly uploaded code, or PS
009 for the programs already in memory. It was always on the comment
line where it alarmed. If there were any numbers after the comment, the
files wouldn't even upload without alarming out. If it was letters after
the comment, it would upload fine, but the program would alarm when it
got to the / line.
the OT-Mate is a pretty basic control. It doesn't even have soft keys,
and doesn't support standard {} comment characters either, but the / has
always worked. For years in fact.
so what could possible have changed. I haven't even touched the parameters.
totally stumped
ca
there was an error, that Ihave never had before. I also couldn't run the
last two programs that were already in the control. They worked a few
weeks ago, but now they error out on the comment lines. It works fine
with a comment / by itself, but as soon as I put any characters behind
it, I get the alarm.
Here is a snippet of the code:
%
O4805
N100 G20
/CNMG/ <--- here is where it was choking
N102 G0 X1.0 Z6.0
N104 G0 T0303 M42
the fanuc errors were either PS 005 for the newly uploaded code, or PS
009 for the programs already in memory. It was always on the comment
line where it alarmed. If there were any numbers after the comment, the
files wouldn't even upload without alarming out. If it was letters after
the comment, it would upload fine, but the program would alarm when it
got to the / line.
the OT-Mate is a pretty basic control. It doesn't even have soft keys,
and doesn't support standard {} comment characters either, but the / has
always worked. For years in fact.
so what could possible have changed. I haven't even touched the parameters.
totally stumped
ca