Cutter comp move

[Roger]

Is there anyway to tell in Mastercam, or, Cimco if cutter comp is being turned on/off in an arc?  Most of the time I have the lead-in/lead-out set to a line with an arc.  Sometimes it doesn't have enough room for the line, and when posted it turns on/off on an arc, resulting in an error on the machine.

I would like to know this before sending the code to the machine, and the operator has to have me revise the program.

[Matthew Hajicek - Singularity]

My post warns me if I have that situation.  Your dealer or post supplier can add that function for you.

[mkd]

hmm. most modern posts will yell at you, right?

[Roger]

I'm using the generic Hass post.

[mkd]

switch to MP master, eh?

[AHarrison1]

I'm not sure about any other controls but I know HAAS will always shout if there is cutter comp on an arc move.

Link to another thread talking about this 

 

Edited November 22, 2019 by AHarrison1
Spelling

[gcode]

13 hours ago, Roger said:

Is there anyway to tell in Mastercam, or, Cimco if cutter comp is being turned on/off in an arc?  Most of the time I have the lead-in/lead-out set to a line with an arc.  Sometimes it doesn't have enough room for the line, and when posted it turns on/off on an arc, resulting in an error on the machine.

I would like to know this before sending the code to the machine, and the operator has to have me revise the program.

MPMaster

 

These posts will yell at you if you output cutter comp on an arc move

 

[JParis]

Here is what I added to my post it's a bit of a hybrid of what MPMaster does, ...it checks both Comp on & Comp off moves

 

In error messages..

scompwarn   : "WARNING - CUTTER COMP APPLIED ON ARC MOVE, POST WILL EXIT, CHECK PATH AND REPOST"

 

In motion output components under pccdia

pcompwarn       #Cutter Compensation Check                     #added 10/02/15
      if prv_cc_pos$ <> cc_pos$ & cc_pos$ & gcode$ > 1,
        [
        if compwarnflg = 0, result = mprint(scompwarn)
        spaces$ = 0
        n$, pspc, *sm00, " ", sopen_prn, scompwarn, sclose_prn, e$
        n$, pbld, exitpost$, e$
        spaces$ = sav_spc
        compwarnflg = 1
        ]
       if prv_cc_pos$ <> cc_pos$ & cc_pos$ = 0 & gcode$ > 1,
         [
        if compwarnflg = 0, result = mprint(scompwarn)
        spaces$ = 0
        n$, pspc, *sm00, " ", sopen_prn, scompwarn, sclose_prn, e$
        n$, pbld, exitpost$, e$
        spaces$ = sav_spc
        compwarnflg = 1
        ]

 

and my pcirout was modded to this

pcirout         #Output to NC of circular interpolation
      if not(arccomp), pcompwarn      # added 10/02/15
      pcan1, pbld, n$, `sgfeed, sgplane, sgcode, sgabsinc, pccdia,
            pxout, pyout, pzout, pcout, parc, feed, strcantext, scoolant, e$

 

and the switch for it

arccomp      : 0     #Allow for cutter comp to be applied on arc, 0=no, 1=yes    # added 10/02/
compwarnflg  : 0     #Flag for compensation warning output         #added 10/02/15

 

 

I have previously been questioned why I exit the post as I do...I tend to post larger files, I don't want to chance one getting to the production floor and them finding the error than.. so I created mine to bomb at the point of the error to make finding it easy & immediate and to force you to fix it "now".

 

JM2C YMMV