hamsamsquanch
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by hamsamsquanch
-
-
Just throwing a SOLVED in here for future searchers.
-
Thank you guys so much for the suggestions! And apologies for the response time, my rookie account is limited on posts per day.
Jparis,
Your suggestion resulted in the same as I had prior, a G165 on the previous tool.
Colin,
I believe your suggestion put G165 on every tool in the file, and every new toolpath between tool changes. Tried a lot of variations on this one and I cannot remember exactly what the carbon copy of what you suggested output.
Another programmer here found an old post processor manual and wrenched on this project for a bit last night. He got it really close, then I moved one of his lines this morning and got it 99% of the way to where I want it.
WHAT WE HAVE RIGHT NOW:
We ended up making a "Common User Defined Variable Initialization" called: sav_mi7 : 0
Near the end of ptlchg$: sav_mi7 = mi7$
Then in pretract (under the G90 line) I put: if sav_mi7 = 1, n$, "G165", e$
This outputs the G165 on the tool with mi7 set to 1, but only registers the first toolpath that uses that tool, unless another tool is called up between instances of the tool needing the G165. (ex. Three drilling paths in a row, using the same tool. The first path has the mi7 set as 1, so the end of the tool gets a G165. If the first is set to 0, but the second and/or third are set to 1, there is no G165 called). I am getting around this on drills, taps, spots and bores by setting the toolpath defaults to put a 1 in the mi7 box. Other toolpath types will require the programmer to keep this condition in mind though.
-
Okay, got the G165 to land after the G90, but now the G165 is only on the toolpath prior to the one with a "1" in the mi7 box.
-
5 minutes ago, Colin Gilchrist said:
Try 'resetting' the value of 'mi7$', after you output the G165. That should make it so it only outputs "once", unless there is another Operation where MI7 is set:
if mi7$ = 1, [ pbld, n$, "G165", e$ mi7$ = 0 ]
I noticed in your sample above, that you have 'mi7'. Is that a typo, or did you try to create your own User Defined variable named 'mi7'? (When using the predefined variable, it should be followed by a Dollar Sign character. The only exception, would be if you were working on a 'pre-X' Post Processor. [V9])
mi7 is supposed to be the Miscellaneous integer #7 and this is a modern Post, so I'll add that $ in and try out the reset code in a few.
Also, with fresh eyes this morning I realized that I need to be putting the G165 in AFTER the G90. Tuesday hit me more like a Monday this week.
Thank you for the reply!
-
Hey all,
I am currently working on a Makino post processor and am trying to setup mi7 to output a G165 at the end of toolpaths. So far I have gotten the G165 to drop in where I want it in the toolpath, but it adds it to all of the posted tools instead of only the one tool I need it on.
Right now I am putting this if statement in pretract above the G90 line
if mi7 = 1, n$, "G165", e$
Have tried adding an else statement after it on the G90 line to cover non "1" values and get the same results. Anyone delt with this before?
Thanks in advance!
Adding height check at the end of toolpaths
in Post Processor Development Forum
Posted
My previous comment is the solve. The condition I spelled out at the end of the comment is how the post is supposed to work, so I am not calling it a problem. If that switch were being read after the first instance of the tool, there would be a height check at every toolpath change, not just the end of the tool.