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:

PPRINT

Verified Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

707 profile views

PPRINT's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

1

Reputation

  1. Colin, I am really excited to see you offering this class....especially since I have a current need to edit my posts. I have been in touch with my re-seller here in South Texas (MLC Cad)....but am getting the slow roll on acquiring the required training documents (They are acting like they have never heard of this document). I've let them know the timing of your class and the urgency, but that does not seem to motivate them what so ever. Typical service from them....but that is a whole other discussion. Question, would you be able to recommend another re-seller that you know would be more responsive? We are a licensed user ( we have 4 seats of 4 axis mill, 1 seat 5 axis mill, 2 seats of lathe, and MTM, which I am not sure is a separate license) so we should not have any road blocks from that stand point. Rob
  2. Quick update....I was finally able to get a version that works so far. I have not completely tested this to ensure it works in all cases though. I inserted the following. You can see its position as right in front the motion output section. x$ = x$ * met_conv y$ = y$ * met_conv z$ = z$ * met_conv # -------------------------------------------------------------------------- # Motion NC output # -------------------------------------------------------------------------- I am trying to figure these MC post out, but it is terribly hard without good documentation. Note to self...call my reseller and get post editing documents. Colin, please correct me if I am wrong, but it appears as though the XYZ positions are captured from the NCI file via "xnci$...ynci$...znci$"...which in turn stores the value in the "x$...y$...z$" strings. At least that is what I was banking on. Rob
  3. Sorry it has taken me some time to get back to this thread....been up to my eyes in alligators the last few days. Colin, thank you for taking the time to help with this question, and all the threads you share your knowledge on. I'm a bit thick headed when it comes to a MC post. I read your instructions and interpreted them as best I could. I was not able to get it to work based on my original interpretation. I made a second attempt by inserting your changes at positions that seemed to make sense to me, as well as changing the variable names until I was able to get the output affected. I am not getting the correct output still, but at least the numbers are changing. The problem seems to be that it is applying the multiplier twice. In the test program I am using I have a move 1.5" which is being output as Y967.74. (1.5*25.4=38.1*25.4=967.74) I will post the position that I have the multiplication functions inserted. You will also be able to see what other variable names I tried that are now commented out. # -------------------------------------------------------------------------- # Motion NC output # -------------------------------------------------------------------------- #The variables for absolute output are xabs, yabs, zabs. #The variables for incremental output are xinc, yinc, zinc. # -------------------------------------------------------------------------- arcrad$ = arcrad$ * met_conv #xout = xout * met_conv #yout = yout * met_conv #zout = zout * met_conv #iout = iout * met_conv #jout = jout * met_conv #kout = kout * met_conv #pxout = pxout * met_conv #pyout = pyout * met_conv #pzout = pzout * met_conv #piout = piout * met_conv #pjout = pjout * met_conv #pkout = pkout * met_conv #pfxout = pfxout * met_conv #pfyout = pfyout * met_conv #pfzout = pfzout * met_conv #pfiout = pfiout * met_conv #pfjout = pfjout * met_conv #pfkout = pfkout * met_conv xabs = xabs * met_conv yabs = yabs * met_conv zabs = zabs * met_conv iabs = iabs * met_conv jabs = jabs * met_conv kabs = kabs * met_conv #xinc = xinc * met_conv #yinc = yinc * met_conv #zinc = zinc * met_conv #iinc = iinc * met_conv #jinc = jinc * met_conv #kinc = kinc * met_conv Please let me know if you have any other thoughts I can try. Thank you Sir. Rob
  4. Colin, thank you for the reply. Would this be as easy as modifying the X, Y, Z, F values as they are being read from the NCI file? Or as they are being output? Rob
  5. Morning All. I run a post from IMS in CATIA that converts inches to mm within the post. My question....is it possible to do this in a MC post? Note: I know how to convert inch to metric files within MC and do not like the process...nor the problems it causes. I want a solution outside of MC. Thank you, Rob
  6. Jeff, I am not sure if the Renishaw will probe a segment of a bore. In our case we have to probe a full diameter. There might be a way. Maybe someone else can chime in. Here is the program we use to probe a bore. This program is set to measure a bore Ø1.2002. You can adjust the D1.2002 to whatever bore size you are probing. On our machine it stores the measurement in a Variable. I think it is #185. You will have to check the Renishaw programming manual to see if that is not it. Normally you can scroll down through the variables and find it. % O07000 ( PROBE BORE ) T25 M06 G91 G28 Z0. G17 G40 G49 G69 G80 G90 G00 G90 G55 X0. Y0. G43 H25 Z5. G65 P9832 G65 P9810 Z-0.3 F50. G65 P9814 D1.2002 H0.01 M0.002 W3. G65 P9834 G65 P9810 Z8. G65 P9833 G91 G28 Z0. G91 G28 Y0. M30 % If you pm me with your email I can send you a PDF copy of the Probe programming manual. Rob
  7. I just checked my "surface rough pocket" tool path and it has all 8 pocketing options in it. I can use this as a temporary work around. I will re-install X2 this morning and hope the problem goes away.
  8. Thanks for all the replys fellas. Roger....not sure what the nethasp is, or the command line switches. You might have to expand on that little for me. Colin....I am trying to make a basic 2D pocketing path. Not a surfacing tool path. I will check surfacing to see if the same problem is over there too. Columbo...I have mill level 3. The full blown multiaxis seat. I am a very experience Mastercam user, just going through a transistion phase with X and X2. I will try installing X2 again to see if the problem rectifies itself. I know that was a solution for problems back in V8 and 9, but I had hoped X would be a better arrangement. Thanks again fellas.
  9. That made me chuckle pretty good! Yeah...I am sure I am not looking at a facing tool path. I think I am sure...it says pocket (standard). Yeah....I am pretty sure.
  10. I installed X2 last week and trying to make the transition from X. I finally got around to making a basic pocketing tool path when I realied I only have two pocketing optoins now. "Zig Zag" and "one way" What gives? Is there a parameter that I have set wrong?

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