add logic to check for T and H match

[Zoffen]

i'm wondering what is a good way to write in some logic to a post to check that T and H match when posti

i'm thinking you add it in the toolchng section in the post and can probably figure the logic out but don't know how to make it generate an alarm.

 

so,

 

1. how do you make the post generate an alarm if a condition occurs?

 

2. would this work in the post:

if tlngno$<>t$
[ADD ALARM HERE]

 

or would i have to store them in separate variables at the toolchange and then compare them.

[Jimmy Wakeford from Barefoot CNC]

Depending on the post you start with you my have to put it in psof$ as well as ptlchg$ section.

 

What I do in the haas post is add

 

tlngno$ = t$

and that always makes it equal to tool number.

 

If you want an alarm from post there's a few more steps

 

 

#Declare a string varible to output to screen and dummy varible
s_offset_err "Height offset does not match tool number!"
err_off : 0 # dummy varible to test output


#then add to ptlchg$ and maybe psof$

   if tlngno$ <> t$,[
           err_off = mprint(s_offset_err)
           tlngno$ = t$  # to automatically change it
           #exitpost$    # if you'd rather quit processing and fix in mcx (you have to remove#)
   ]

[EX-wccprogrammer]

This thread covers it.

 

Post Trick

[Zoffen]

thanks, thats what i'm lookin for. making H come from T is a better idea!

[Greg Williams]

I habe the following changes

 

pbld, *n$, "T" *t$, sm06, e$

pbld, n$, sg43, "H" *t$, pfzout, e$, pstagetool, e$

 

and

 

fmt 4 t$ #Tool number GW Removed T

 

T and H will always match now

[EX-wccprogrammer]

There are times that it is not possible for T and H to match. For example, running a 40-tool program on a 30-tool machine. Having a post that automatically matches T and H is not ideal in my opinion. I prefer the notification that they do not match, that way nothing slips through. But I can use different T and H values if I need to.

[Jimmy Wakeford from Barefoot CNC]

Ex, Do you always add 10 to the lentgh offset each time it is used? I done a haas(think it was a haas) post like that that awhile back. I like the notification so I can fix it in the mcx file.