Scan Post output for H0

[B.D.]

Is there someway for the post to scan and report any (H0)zero height offsets. Just made an operation change, and Mastercam changed the offset to 0 and.......CRASH!!!!!! Would like to avoid this in the future.

 

 

TIA

[Mr. Wizzard]

I dont know how, but I'm pretty sure this was covered recently. Try a search for it.

[Greg Williams]

There was a thread last year on this one

[Rob @ Target Machine]

First we need to define an error message. Do a search through your post for "error" and find a section that looks like this:

 

# --------------------------------------------------------------------------
# Error messages
# --------------------------------------------------------------------------
saxiswarn      : "WARNING - POST ROTARY AXIS ASSIGNMENT ('rot_on_x') OVERWRITTEN BY OPERATION"
saxisoff       : "ERROR - POST ROTARY AXIS ASSIGNMENT ('rot_on_x') IS DISABLED"
saxiserror     : "ERROR - INVALID ROTARY AXIS ASSIGNMENT ('rot_on_x') FOR CURRENT OPERATION"
sindxerror     : "WARNING - INDEX ANGLE DOES NOT MATCH POST SETTING ('ctable')"
stlorgerr      : "ERROR - TOOL ORIGIN DOES NOT MATCH CENTER OF ROTATION IN POLAR MILLING"
shomeserror    : "ERROR - G92 WORK OFFSET ('wcstype') DOES NOT SUPPORT TRANSFORM SUBPROGRAM"
ssubprgerror   : "ERROR - TOOL SUBS (REPS) ('mi1) DO NOT SUPPORT TRANSFORM SUBPROGRAMS - SET mi1$ TO ZERO AND REPOST"
scdsubprgerror : "ERROR - CUSTOM DRILL SUBS ('mi10) DO NOT SUPPORT TRANSFORM SUBPROGRAMS - SET mi10$ TO ZERO AND REPOST"
sprognoerror   : "ERROR - PROGRAM NUMBER CANNOT BE ZERO"
sprogfmterror  : "ERROR - NCI NAME MUST BE FORMATTED AS 5 SPACE DELIMITED FIELDS CONTAINING 'REV' AND 'OP' Example:'CC33042 REV 2 OP 1'"
sprgnerror     : "ERROR - SUBPROGRAM NUMBER MATCHES THE MAIN PROGRAM NUMBER"
scompwarn      : "WARNING - CUTTER COMP APPLIED ON ARC MOVE"
smiscerror     : "WARNING - MISC VALUES SET TO POST DEFAULT FOR CURRENT OPERATION"
srotaxerror    : "ERROR - MORE THAN 1 ROTARY AXIS DETECTED IN SELECTED AXIS COMBINATION - OUTPUT MAY BE INVALID"
swriteopserror : "ERROR - WRITE NC OPERATION INFORMATION MUST BE ENABLED IN CONTROL DEFINITION - SET AND REPOST"
sxaxiswarn     : "ERROR - SELECT MACHINE ACHIEVABLE TOOLPLANE WITH X-AXIS ALONG MACHINE X - SET AND REPOST"
syaxiswarn     : "ERROR - SELECT MACHINE ACHIEVABLE TOOLPLANE WITH Y-AXIS ALONG MACHINE Y - SET AND REPOST"
szaxiswarn     : "ERROR - SELECT MACHINE ACHIEVABLE TOOLPLANE WITH Y-AXIS ALONG MACHINE Y - SET AND REPOST"
srotlimwarn    : "WARNING - ROTARY LIMITS EXCEEDED (CANCEL TO EXIT)"
saxissuberror1 : "ERROR - AXIS SUBSTITUTION IS SETUP FOR HMC WITH -Y ZERO POSITION (PLANES 2,5,3,6)"
saxissuberror2 : "ERROR - AXIS SUBSTITUTION IS SETUP FOR VMC WITH +Z ZERO POSITION (PLANES 1,2)"
swcserror      : "ERROR - WORK OFFSET NUMBER OUT OF RANGE"

Let's add a new one for this example.

stool_length_error      : "ERROR - TOOL LENGTH OFFSET NUMBER IS ZERO"

 

Now look for the G43 output lines in your post. Usually there are two lines. One will be in ptlchg_com, and one in ptlchg0$.

 

Here we need to test for the condition to warn against, and trigger a warning message.

 

 

pbld, n$, "G43", *tlngno$, pfzout, scoolant, pfspindleout, next_tool$, e$

if tlngno$ = 0,
             [
             result = mprint(stool_length_error)
             exitpost$
             ]

 

HTH

[K2csq7]

I put this right at the top of my toolchange postblock

 

  	if t$ <> tlngno$, pbld, "M00", e$ "(", "T & H DO NOT MATCH!!!!!!!!!!!!!!!!!!!!!!", ")", e$ "M00", e$
  	if t$ <> tloffno$, pbld, "M00", e$ "(", "T & D DO NOT MATCH!!!!!!!!!!!!!!!!!!!!!!", ")", e$ "M00", e$

 

Works like a charm!!!

[B.D.]

Thanks very much fellas.....

[Colic]

Thanks from me to.