Make Your Post Catch Common Errors

[PcRobotic]

would you mind take a look at my file? I'm stump and I'm so thankful that you're very patient with me about this

My Post.txt

[Peter - Avivi CNC Solutions]

PcMannnn,

 

Do this for (2D) mill stuff:

 

Remember? Now define another variable:

OpTopOfStock : 0 # Operation Top of Stock

 

Add another parameter read at pparameter$ postblock:

if prmcode$ = 10027, OpTopOfStock = rpar(sparameter$, 1) # Operation Top of Stock

 

In your post should be some similar I assume... (3 times)

Change them, add an error handling line:

#
"( DOC =", *operation_depth, ")", e$
if OpTopOfStock < operation_depth, [if mprint("Something is verrryyyy-verrryyyy wrooonnngggg", 2) = 2, exitpost$]
last_op_id = op_id$
#

[Peter - Avivi CNC Solutions]

Do this for (2D) mill stuff:

 

It will work @ Drilling too.

[PcRobotic]

Thank you Peter, I got it and I would like it points out WHAT OPERATION HAVING ERROR like

 

CHECK OPERATION #5, SOMETHING VERYYYYYYYYYYYYY WRONGGGGGGG

 

How do I do that? Thank you.

[Peter - Avivi CNC Solutions]

Your post has some error string in this area, you can add another.

Luckily we have "sOpSeqNo" variable also + toolname.... So you can bulit your own error message:

# --------------------------------------------------------------------------
# Error Checks
# --------------------------------------------------------------------------
sOpSeqNo		 : "" #Operation manager displayed operation number
stoollengthoffserror = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG TOOL LENGTH OFFSET#"
sg53xyz = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") UNUSUAL G0 G53 XYZ VALUE IN HERE"
stoollengthoffszeroerror = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG TOOL LENGTH OFFSET"
stooldiameteroffserror = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG CUTTER COMP"
stooldiameteroffszeroerror = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG CUTTER COMP#"
scoolantisoffserror = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") NO COOLANT"
sdrl_sel_tos$ = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG TOP OF STOCK"
serrordetect = "Click OK to Q.C source program, click CANCEL to ignore"

sMyFancyDepthError = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG TOP OF STOCK"

 

And change these lines to:

(add sMyFancyDepthError variable)

if OpTopOfStock < operation_depth, [if mprint(sMyFancyDepthError, 2) = 2, exitpost$]

 

Should work...

[PcRobotic]

wow, you're great. Thank you.

[PcRobotic]

Hi Peter,

Is there away that I can force the window appears the value? ( Please see attach image)

 

PS: Regardless of the colors, they are only to meant to demonstrate for easier to read.

 

 

I wish you were my neighbor, to have dinner with and to learn from. You are one of the amazing guys in this forum.... Once again, thank you for your so much valuable time that you spent for me.

 

 

 

Best regards,

S.Luong

[Peter - Avivi CNC Solutions]

I need beer only. A lot!

Anyway, nothing is impossible...

 

First, format your output:

fmt "Top of Stock: "  2   OpTopOfStock  # Operation Top of Stock

 

Then you can simply add it to the error string:

sMyFancyDepthError = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG TOP OF STOCK" + "Becase depth is " + operation_depth + " BUT " + 2OpTopOfStock

 

Or something like that. I'm not checked, but should work.

Where is my beer???

[PcRobotic]

I did exact as you directed and I have this problem, do you know why?

[Peter - Avivi CNC Solutions]

Bahh... No idea yet, I'll take a look later.

[PcRobotic]

Thank you, Peter.

[Peter - Avivi CNC Solutions]

Change this line to:

sMyFancyDepthError = "Look for CUT# " + sOpSeqNo + ": " + "(" + s20001 + ") WRONG TOP OF STOCK" + "Because depth is " + no2str(operation_depth) + " BUT " + no2str(2OpTopOfStock)

 

no2str() -> NumberToString function

[Peter - Avivi CNC Solutions]

Expanding on above post, the same applies to drl_sel_ref$ and drl_sel_tos. (Note NO $)

 

drl_sel_ref$ is R plane on initial start drill cycle (1st hole)

drl_sel_tos is used on initial start drill cycle (1st hole).

drl_sel_tos$ is used on all subsequent holes.

 

May be I'm wrong, but I made some test, and drl_sel_ref$ and drl_sel_tos$ returns as negative in the following valid situation:

I'm working on a post to catch these type of errors and I think about another solution.

[EX-wccprogrammer]

I use some of those variables in a custom drill cycle that I use. But I have not used the 2 you have listed. I got the information about what they do from the MP guide. Play around with it, and let us know what you come up with.

 

This thread is evolving into some features that are more advanced than I have used so far. I will pick out the useful tricks for incorporation into my arsenal, thanks to all that have (and will have) contributed!

[PcRobotic]

THANK YOU, PETER. IT WORKS BEAUTIFUL, YOU'RE THE MANNNN....

[Peter - Avivi CNC Solutions]

Play around with it, and let us know what you come up with.

 

Yeppp, I think 'bout compare the depth$/initht$/refht$ triangle... We'll see!

(those variables are always absolute value from Z level)

 

 

UpDate: tosz$/refht$/zdrl$ triangle...

[Peter - Avivi CNC Solutions]

THANK YOU, PETER. IT WORKS BEAUTIFUL, YOU'RE THE MANNNN....

 

You're welcome! Where is my beeerrr???

[PcRobotic]

Peter, do you live in the U.S? Let me know if you are, I really want to send you something for my appreciation.

[PcRobotic]

I'm getting greedy since I'm thrill with your functions. Is that possible that I can force it output at the popup window just like the WRONG TOP OF STOCK like, WRONG CUTTER COMP VALUE with value or TOOL LENGTH HEIGHT value?

[EX-wccprogrammer]

Peter, you have a fan.

 

PcRobotic, we post snippets of code to show how things can be done in a post. The intent (as far as I am concerned) is to guide others how to make similar edits on their own. I for one have no interest in making every single edit for you. Take the ball and run with it. If you get stumped, then by all means ask.

 

Perhaps Peter has enough idle time to write every snippet of code that you desire.

 

Cheers!

[PcRobotic]

I know I'm kind of abuse the help of you and Peter. Perhaps someone just have the same questions and afraid to ask. Once again, you guys are helping me more than enough. Thank you Ex-wcc and Peter. You guys are amazing....

[Peter - Avivi CNC Solutions]

Peter, do you live in the U.S? Let me know if you are, I really want to send you something for my appreciation.

No, but don't worry, if I will (and I will!) spend my holiday in California, I'll stop by... :D

 

 

I'm getting greedy since I'm thrill with your functions. Is that possible that I can force it output at the popup window just like the WRONG TOP OF STOCK like, WRONG CUTTER COMP VALUE with value or TOOL LENGTH HEIGHT value?

You lucky, beacuse in these days I have a bunch of time... (but I have no a bunch of beeerrr...!!! :D)

I'll take a look, but not promise

 

 

Peter, you have a fan.

 

Perhaps Peter has enough idle time to write every snippet of code that you desire.

Cheers!

Yessss and yes! As I said, in these days I have a lot of free time to play with, until october, so PcRobotic get hurry!

[Peter - Avivi CNC Solutions]

Suppose the TOP OF STOCK = -1.100 and the DEPTH = -1.757

 

and someone made mistake and put the TOP OF STOCK = -2.000 and the DEPTH is okay = -1.757

 

G43 H20 Z.1 T16 M8(DOC= Z-1.857)

M135 S320

G98 G84 Z-1.757 R-2.000 F10. --------------------------> WRONG ARE VALUE base on TOP OF STOCK VALUE GIVEN...

X3.4047 Y-3.4047

 

Before we go ahead, stop for a moment here, at drilling stuff.

One thing crossed my mind, and I made some test with drilling. Basically I can say, that there is 2 important value at every

drill toolpath. One is RETRACT as a basic starting point and DEPTH which is end-depth.

So that's why I was confused about TopOfStock. It's not affect (not really, especially in absolute mode) the output of drilling

NC code. But the Retract and Depth (in Mastercam OP) they do, they give the "R" and "Z" value. Am I right?

 

PcRobotic, my confuson starts here, you mentioned and showed on a picture that Top of Stock value is wrong. Was -2 I think.

Are you sure that "R-2" comes from Mastercam Top of Stock setting? Did you tested?

I believe that (unfortunatelly) scrapped a part because R value was lower than Z, but I think it not comes from Top of Stock.

Yepp, I'm not checked in your post, I just wanna ask first.

 

This question and note is not for you only, it's for the community too!

 

Back to the topic, I think at drilling it's enough to compare the R and Z values.

[PcRobotic]

You already helped me to figured it out for the

 

G43 H20 Z.1 T16 M8(DOC= Z-1.857)

M135 S320

G98 G84 Z-1.757 R-2.000 F10. --------------------------> WRONG ARE VALUE base on TOP OF STOCK VALUE GIVEN...

X3.4047 Y-3.4047

 

I concern about the window thing because it tells the user what to expect to have certain COMP, TOOL LENGTH OFFSET (Please see attached image)

 

PS: Let me know when will you come to San Jose, California or Oakland, San Francisco because I can drive to these 3 cities and have drinks with you.

 

 

Thank you so much for your help, I'm definitely a FAN of you.

[PcRobotic]

You know these procedures are GOLDEN like checking INITIAL HEIGHT, RETRACT HEIGHT,

 

 

USE CLEARANCE ONLY AT THE START AND END OF OPERATION

G89 OR G88 WARNINGS.

 

 

 

These kind of rules are worth millions dollars for the HORIZONTAL where they run 100 pieces at the same time and if the post checks all the safety prior posting it just like we have to check all the gauges before flying an airplane for enough OIL, HYDROLLIC, ELECTRICITY... Same as CNC because one wrong G-CODES can cost someone's life and that is no body wants to happen.

 

May be too much checking at the programming room but it sure the heck of much easier for the setup-man.

 

 

 

Thank you Peter, once again I don't know how much thankful from me to you. You just blew me away with your positive attitude.....