Post help

[connormac]

Is there a way to set up a post show an error if there is a Q0 in a G83 line. Sometimes when I copy a spot drill operation and make it a drill operation, I forget to put a number in the peck depth.

[Zoober]

How do you want the error to show? in the .err file? or just a note in the gcode?

I do checks on fixture offsets and such...

[connormac]

Just a note in the gcode. How do you do checks on fixture offsets??

[Zoober]

Here is a snippet of how I check them.

code:

---

 sav_spc = spaces$

spaces$ = 0

if workofs$ <= 4, 032, "MSG", "(",034,*sbadoff,034, ")"

if workofs$ > 100, 032, "MSG", "(",034,*sbadoff,034, ")"

spaces$ = sav_spc

if workofs$ >= 0 & workofs$ < 4,

---

For your Q value, you can can track the peck1$ variable as I do the workoff$

 

perhaps like.......

code:

---

ppeck$ #Canned Peck Drill Cycle

pdrlcommonb

if peck1$ <= 0,

[

032, "MSG", "(",034,*sbadq,034, ")"

]

else,

[

pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout,

prdrlout, *peck1$, *feed, strcantext, e$

]

pcom_movea

---

[Tim Johnson]

IMO you're better off creating an error message that will post up on the screen so you can fix it immediately.

 

to do this;

 

Create an error message. If you're using mpmaster there should be an error message section;

 

code:

---

speckrate_error  "ERROR --- PECKRATE = 0"

---

setup a conditional line to catch and print the error;

 

code:

---

ppeck$           #Canned Peck Drill Cycle

savdrl_gcode = gcode$

pdrlcommonb

if peck1$ = 0, result = mprint(speckrate_error) #<<<<<<<<<<<<<<<<<<<<<<

pcan1, pbld, n$, *sgdrlref, pgdrill, pdrlxy, pfzout, pcout,

prdrlout, *peck1$, *feed, strcantext, e$

pcom_movea

---

You will get a message window on the screen that you'll have to click "ok" to close and resume posting.

[crazy^millman]

I agree with Tim this is my preference.

 

[ 03-20-2008, 05:19 PM: Message edited by: Crazy^Millman ]

[Zoober]

Tim, thats good info.

I gave connormac that example based on what he required.

Also, don't forget to define the sbadq(or whatever )variable.

[connormac]

Thanks Tim you are right that is what I need . Sorry Robert I didn't know what I needed. My bad.

[connormac]

Do I need to do something special to enable error messages? I'm not using mpmaster. But I tried to set up my post like mpmaster is set for errors.

[Tim Johnson]

In my control def file under "Files" I have Keep error file "On post errors and messages" and under Message options "All error messages to file" but I would think you shouldn't need to have that turned on.

 

I do have this in my post (from V9)

 

code:

---

error_msg$   : 0     #0=file and prompt, 1=to screen, 2=one to screen

err_file$ : 1 #0=fatal, 1=all errors, 2=inc mprint, 3=inc prompts, 4=always

---

You can try adding it to your post and see what happens.

[connormac]

I can get the way Robert says to do it to work. But I can't get mprint to bring up message box.

[Tim Johnson]

Send me your post and I'll see what I can do.

 

Edit: Send me your mach/control def also just in case....

[connormac]

Tim You have mail.

Thanks for looking

[Tim Johnson]

For whatever reason the "result =" wasn't working in connormac's post. What I ended up doing was adding a variable to trigger the error;

 

code:

---

testpeckrate : 0    #switch to turn on peckrate flag

---

and replaced the "result =" with;

 

code:

---

         if peck1$ <= 0, testpeckrate = mprint(speckrate_error)

---

[connormac]

Thanks so much. This will help prevent errors in program from getting to the floor.

 

 

Thank you Tim and Robert

[Zoober]

Tim is the man....

Mine was kind of a kludge. I now know of a better way.

[Lars Christensen]

connormac,

Thank you for asking that question

 

Tim,

Thank you for sharing your knowledge