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:

agrimsontool

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

agrimsontool's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Ok, I fumbled through it and got it to work. Apparently MC8 doesn't like hsm_flg but hsm_flag works. Really strange. Thanks for the help!
  2. Chris, thanks for the quick reply. I understand what you are saying, but it still depends on that initial definition line. If I put a 0 in there it won't put the hsm code in at all, if I change it to a 1 it will put only the shut off code, and then it will put it for only the first tool. Am I defining it wrong?
  3. Yes, my phsmoff is called up through pretract which is then called up through peof. So I defined my variable like so: #Misc variables sav_mi5 : 0 #Saved mi5 value And at the beginning of psof, ptlchg, and ptlchg0 I added: mi5 = sav_mi5 I then changed my phsm and phsmoff as follows: phsm #High speed machining on if sav_mi5 > zero, [ "G49", e "G5.1Q1R",*shsms, e ] phsmoff #High speed machining off if sav_mi5 > zero, [ "G5.1Q0" ] The problem this presents is that sav_mi5 is defined by the initial definition line. It does not save the current integer in its place with the code: mi5 = sav_mi5 So if I leave that initialization definition at 0 it won't turn on at all. If I change it to 1 it will be on for every tool. Any clue as to what I am doing wrong?
  4. Hello all, I am trying to use mi5 to turn on AINano (similar to HSM on my Bridgeport 760XP3) and am running into problems. I am running Mcam 8.1 and I have it almost working I just need to tweak it a little. AI Nano is called out like this: N200 (1/2 FLAT ENDMILL ) G49 G5.1Q1R4 T2M6 And it's turned of by using: G5.1Q0 G5.1 is the code for the AI Nano mode, Q turns it either on or off, and R(shsms) is a number 0-9 to tell it how much to fudge the corners. I have mi6 set up as that R value using a formula (shsms = mi6), and that works fine. I put the following code in to my post: phsm #High speed machining on if mi5 = one, [ *"G49", e *"G5.1Q1R",*shsms, e ] phsmoff #High speed machining off if mi5 = one, [ *"G5.1Q0", e ] I then put a phsm callout between ptoolcomment and the toolchange line in both the ptlchg and psof sections of the post. Like so: ptoolcomment comment pbld, phsm, e pcan pbld, *t, "M6", e pindex I also put phsmoff in the pretract section of the post. Like so: gcode = zero pbld, phsmoff pbld, sccomp, scoolant, psub_end_mny, e Now the problem I have is that it doesn't always associate turning AI Nano off with the correct tool. Say I have T1 a drill (Misc Values box unchecked), T2 an endmill(Misc Values box checked and mi5 as 1), and T3 a tap(Misc Values box unchecked also). What happens is I will get the G5.1Q0 line at the end of T1 instead of the end of T2. It will however turn AI Nano on correctly for T2, but it won't turn it off for T2. After turning the debugging lines on I see that the command to turn AI Nano off in T1 comes from pretract even though the Misc Values for that tool are off. So it is looking at the value for mi5 from the next tool. I have read online about using sav_mi5 to save it, but can't seem to get it to work. Any help would be appreciated. Thanks, Jerry

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...