Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

ahaslam

Verified Members
  • Posts

    272
  • Joined

  • Last visited

Everything posted by ahaslam

  1. Thanks MIL, This gave me just the ticket.
  2. I am looking to use a G94 at the end of my tapping cycle after all the holes have been tapped. ptap$ # Canned Tap Cycle n$,"G93",e$ n$, *sgdrill, g98_g99, *x$, *y$, *dpoint, *refht$, pplunge,e$ if I put it in as a new line in will run after the first hole has been tapped canceling my IPR before all holes have been tapped. so I have been sticking it in my g80 line. pcanceldc$ # Cancel canned drill cycle n$, "G80", "G94",e$ I just don't like that it pops up every time I use g80. How can I get it to cancel after all the holes have been tapped?
  3. Yeah, that's all in newer versions. Thanks just the same.
  4. Thanks, that cut my program size in half. I looked for the check box Rstewart pointed out and couldn't find it. I am still on X5 though and that may be why. Maybe one day they will buy me an upgrade, till then.
  5. Is there any way I can make the program for the HS tool paths smaller? The linearized entry makes for some massive programs and we just don't have the memory in our old machines. I love the way that the tool paths only remove material needed (less time cutting air) but the lead in/out is killer on memory. Maybe I am missing a setting, or maybe someone could guide me in a new direction other than contour and basic pocketing.
  6. You may find more help from the Mastercam C-Hook, NET-Hook and VBScript Development forum Try moving your post to that forum.
  7. Try adding some code to test 'op_id$', as that is a more reliable way to do what you are after. The 'Tool Op' value can be the same, from Operation to Operation, but 'op_id$' is a unique value for each specific tool path being processed. The 'op_id$' does not have to be in numeric order though, it only has to be a "unique" value. (This is because you can re-order ops, and you can also select ops independently (while leaving some "unselected") when you post First off, thanks for working with me on this. I think I understand what you are saying, using op id would let me identify each operation as a unique output. All that I am looking for in a way to tell the operators what tool path I am using. if it contours three time, each a different operation then that's okay, it's still just a contour. I could add both so it says (op1 contour) (op 2 contour). Is that how op id works?
  8. okay, progress has been made. Now my issue is that it puts out (example) opcode every time the tool moves in z. Hard to explain, let me show you. O4309 ( BA4309A ) G0 G90 G59 X0 Y0 T1 M6 ( Facing ) S6000 M3 G0 G54 X-5.9 Y4.3249 G43 H1 Z.25 T2 M8 Z.2 G1 Z0. F40.0 X5.9 G0 Z.25 X-5.9 Y3.2437 ( Facing ) Z.2 G1 Z0. X5.9 G0 Z.25 X-5.9 Y2.1625 ( Facing ) Z.2 That is because I put it in my null tool change line. Now I just need to add some logic that says if tool_op is equal to the last tool_op then don't output tool op. I am so very new to this and only have a basic understanding of code but, think you're willing to give me this one?
  9. Thanks guys, I will adjust my tool paths to avoid this.
  10. Okay then, I will keep that in mind, thank you.
  11. One quick thought about this, If you remove the pccdia command from your arc move wont that remove your cc entirely, and doesn't that make the whole thing meaning less? I only ask because I am having the same issue and tried to delete my cc from the arc line and then force cc in the next line but it never came.
  12. I have been looking through the form trying to find a solution to this issue, although a number of people are having the same issue, I haven't found a solution specific enough to help me. I am trying to create some logic in my post that well stop it from spitting out CC in an arc move. Here is my code, pcir$ # Circular interpolation 2 n$, sgplane, sgcode, pccomp, x$, y$, z$, parcrad, pfr, pcan,e$ now, if I delete pccomp I won't get a g41 at all and that doesn't help, I have also tried to force output in Linear movements but sometimes the first tool motion is an arc. Any ideas on how to cure this?
  13. thanks, I will try to work with it and let you know how it goes.
  14. so I am really new to this and the information I have relating to posts is out of date. I am trying to put information about the operation being preformed into the program such as "(contour)" and found a value called opcode, the only problem that I have found is that when I try to out put opcode for Circle mill it doesn't have a number. I just get "( )" and there isn't much I can do with that. Can some one tell me what I am missing here.
  15. I am looking for a list of variables/postblocks that Mastercam uses when posting. Specifically I am looking for ones that relate to the tool group, WCS, and operation name. I would like to add them in to my programs as comments so that operators know what is going on. I can do that part, I just need the list. Thanks.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...