Okuma post question

[jeff]

I have a heavily altered post and somewhere along the line I changed something and can't figure out where.

Specifically this is only an issue when ramping a contour such as a bore WITH cutter comp on.

The problem is that it doesn't turn it off after the lead out, doesn't turn it off at all.

 

A lot of times I have to ramp a hole using CC (set to wear),.

Does anyone know what I would put into my post and where? To make it input a G40?

I have no issues with G40 anywhere else in any other toolpath.

::banghead::

[K2csq7]

The last move (where you would expect to see the G40) is it an XY linear move?

Run that op through the debugger with a normal contour op (one that has comp working correctly) and see if the beginning of the line that calls out (or should call out) the G40 comes from the same spot in the post for both the working and not working operations.

P.S. your sure it is set to wear?

[jeff]

The last move (where you would expect to see the G40) is it an XY linear move?

Run that op through the debugger with a normal contour op (one that has comp working correctly) and see if the beginning of the line that calls out (or should call out) the G40 comes from the same spot in the post for both the working and not working operations.

P.S. your sure it is set to wear?

 

Yes, I only use wear and computer comp.

But this issue is only when I am ramping.

If I am doing a normal 2D contour the G40 appears normally, but if I am ramping, the G40 never gets put into the program.

[Guest]

Jeff, try adding a perpendicular entry move in and out

[jeff]

This is a sample program I just created.

2" hole, 1" deep with wear comp:

 

(XXX)
(JUL-08-11)
(T01 3/8 CARBIDE FINISHER,DIA=.3750)
N100(CONTOUR)
G15H01
/M08
G00G40G80G90
G56H01X.0325Y0.Z2.S2500M03
G00Z.1
G01Z0.F149.
G41D01X-.215Y.2475F20.
G03X-.8125Y0.I-.2475J-.2475
G03Z-.1I.8125J0.
G03Z-.2I.8125J0.
G03Z-.3I.8125J0.
G03Z-.4I.8125J0.
G03Z-.5I.8125J0.
G03Z-.6I.8125J0.
G03Z-.7I.8125J0.
G03Z-.8I.8125J0.
G03Z-.9I.8125J0.
G03Z-1.I.8125J0.
G03I.8125J0.
G03X-.8124Y-.01I.8125J0.
G03X-.212Y-.2501I.3499J.0043
G01X.0325Y.0004
G00Z2.  [b](should be G00G40Z2. on this line)[/b]
M09
X-10.Y20.Z20.M09
M02
%

 

 

According to the debug, the G00 Z2. line is this:

 

prapid$ # Linear line movement - at rapid feedrate 0

pcan

pcan1, pccomp, `sgcode, x$, py, z$, pfr, strcantext, e$

pcan2

 

 

 

With comp set to computer:

is says the post is using this line:

 

prapid$ # Linear line movement - at rapid feedrate 0

pcan

pcan1, pccomp, `sgcode, x$, py, z$, pfr, strcantext, e$

pcan2

 

Ok so it's the same post line, what is missing?

[jeff]

Jeff, try adding a perpendicular entry move in and out

 

My lead in/outs are:

 

Tangent with length and arc the same (in this case .350")

and 135 degree sweep.

Keeping the start point center of the hole, or darn close to it.

I will try a perp lead for kicks.

 

EDIT:

Switching from Tangent to Perpendicular gave me the same result... no G40.

[Guest]

there are some issues in X5 and cancelling comp properly, I am wondering if this isn't part of the issue.

 

Nothing has changed but X5, correct?

[jeff]

This has been an issue since I altered this post back in V9.

Other than that, the post is flawless.

[jeff]

Ok when not ramping, and using Wear, the post uses this line, and gives me the G40 like it's supposed to.

 

 

pcancelcc$ # Cancel cutter comp.

"G40", !ccomp$,e$ # Update prv_ccomp

[jeff]

So maybe I need the pcancelcc on this line somwehere?

 

 

prapid$ # Linear line movement - at rapid feedrate 0

pcan

pcan1, pccomp, `sgcode, x$, py, z$, pfr, strcantext, e$

pcan2

[jeff]

Also I noticed that there is a ` before the sgcode.

I assume that's not supposed to be there?

 

edit: nevermind, that needs to be there

[jeff]

Ok, whatever is causing this, is making the post not look to the pcancelcc$ line when ramping and wear comp.

For kicks, I altered that line and forced it to include "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

nothing.

What in the post directs it to this line?

I've tried pzrapid$ and this doesn't affect anything, even when forcing that line to output "XXXXXXXXXX"

 

 

prapid$ # Linear line movement - at rapid feedrate 0

pcan

pcan1, pccomp, `sgcode, x$, py, z$, pfr, strcantext, e$

pcan2

 

pzrapid$ # Linear movement in Z axis only - at rapid feedrate 0

pccomp, sgcode, z$, pfr,e$

#pcooloff # Coolant off

 

 

edit: I'm heading home for the day and beat my head against the wall lol

[Rob @ Target Machine]

Jeff - I think you're due to have your post updated.

 

pcancelcc$ is called by the mp.dll when gcode 1004 is found in the nci. I suspect you won't find the 1004 in the nci for that toolpath.

The use of the pcancelcc$ postblock is not recommended.

This was fine way back in V9, but I don't think you're going to have much luck using this V9 style post in X5 without some modification.

 

If I'm not mistaken, your cutter comp string select table is likely using ccomp$, and needs to be modified to use cc_pos$, to select the string to output and cancel your cutter comp codes correctly.

 

You can grab the framework and logic right out of the mpmaster if you're comfortable making the edits, otherwise, I'd give a call to my VAR for the mods.

[Greg Williams]

Jeff,

 

Can you do a file compare on the original V9 post from the CD?

 

The original V9.0 post had

 

pccdia      	#Cutter Compensation
 	if prv_cc_pos <> cc_pos & cc_pos & (gcode = two | gcode = three),
   	[
   	if omitseq = no,
     	scdc_error = scdc_error + strspace + strlp + strn + no2str(n) + strrp
   	result = mprint(scdc_error)
   	]
 	if prv_cc_pos <> cc_pos & cc_pos, prv_tloffno = c9k #Force Dxx
 	sccomp           	# Output G40/G41/G42 as needed
 	if cc_pos, tloffno   # Output 'Dxx' offset register if G41/G42

[Goldorak]

there are some issues in X5 and cancelling comp properly, I am wondering if this isn't part of the issue.

 

Nothing has changed but X5, correct?

 

my okuma post works as it should until X5 , i get the same compensation error as jeff

 

my reseller was able to correct it but i had no clue how he does .....

[jeff]

Jeff - I think you're due to have your post updated.

 

pcancelcc$ is called by the mp.dll when gcode 1004 is found in the nci. I suspect you won't find the 1004 in the nci for that toolpath.

The use of the pcancelcc$ postblock is not recommended.

This was fine way back in V9, but I don't think you're going to have much luck using this V9 style post in X5 without some modification.

 

If I'm not mistaken, your cutter comp string select table is likely using ccomp$, and needs to be modified to use cc_pos$, to select the string to output and cancel your cutter comp codes correctly.

 

You can grab the framework and logic right out of the mpmaster if you're comfortable making the edits, otherwise, I'd give a call to my VAR for the mods.

 

Yes it's using ccomp$.

I guess I'm due to start over fresh, since there are a few things I'd like to change anyway,I've just been putting it off.

Thanks!