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:

Hubz

Verified Members
  • Posts

    10
  • Joined

  • Last visited

Hubz's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Are you running a Mill Level 3 HASP?
  2. Thanks for the help and ideas After doing speeds/feeds tests, I settled on the following; side cutting - 1/2" carbide single flute router bit (new), 14,000/40, thru-tool coolant - I tried HSS and it chattered at all rpm's, switching to the additional weight of the carbide helped reduce and finally remove the chatter at higher rpm's. finishing bottoms of grooves - 1/4" carbide 4-flute em(new) 3/4" loc, 15,000/40, thru-tool coolant - HSS left a beautiful finish along a 3" path only finishing the floor and removing .025"...then progressively/visibly dulled , but still pulled a nice chip. Taking the same path with the carbide, I was able to complete the cut (9" circ,, .400" slot) and another before noticing any surface dulling. I want to try diamond tooling....maybe next project HSS left the best finish though. If I had a small job to do, that's what I'd use....with a few spares too. I hope that this info helps you on your next Ultem experience...hehe. I plan to keep playing with a few material samples I have, I will post the results. -BC
  3. Greetings! I'm looking for a bit of input. I've been working with ULTEM 1000 recently and have had some surface finish issues. All the tooling we are currently working with is carbide. I've read that HSS, and diamond tooling, produce a superior surface finish with this material. My employer is willing to purchase a limited amount of new tooling for this next project and I want to get the correct tools. So, here's my question. Would it be better for me to purchase HSS, or diamond tooling? Also, if you've worked with this material before, any tips on feeds and speeds would be appreciated. Looking forward to your thoughts.....and thank you in advance -BC
  4. Greetings! I'm looking for a bit of input. I've been working with ULTEM 1000 recently and have had some surface finish issues. All the tooling we are currently working with is carbide. I've read that HSS, and diamond tooling, produce a superior surface finish with this material. My employer is willing to purchase a limited amount of new tooling for this next project and I want to get the correct tools. So, here's my question. Would it be better for me to purchase HSS, or diamond tooling? Also, if you've worked with this material before, any tips on feeds and speeds would be appreciated. Looking forward to your thoughts.....and thank you in advance -BC
  5. UPDATE: I have had a few conversations with MCAM NW and found out the true issue. It was NOT because I had MCAM X6 open twice. It was because I had used the "Group Comment" field in the "Machine Group Properties" tab for program notes, and had entered an unrecognized integer into that field( hit tab most likely). This caused the error code and wouldn't let the post processor progress part that point. I have stopped using that field for notes, and have noticed no other issues Happy Programming! -BC
  6. UPDATE: I have successfully recreated this file and have come up with a reason why this happened. It seems that I had MCAM open twice. I didn't realize that I had an extra copy running in the background with the offending file open. DOH! Won't be doing that again! Thanks guys for all your assistance -BC
  7. I have regenerated the toolpaths, with no success. I also verified that the files were routed to the correct folders and posts. Thanks for the reply Colin, any chance that I have to save this program I will jump at! BC
  8. Well.....I've reloaded the Mach def's...didn't help. Tried this too......didn't help. Still get the errors in posting message. /sigh Oh well, guess I'll remake the program. Thankfully I get paid by the hour....hello incoming OT! Thanks for your help gcode, BC
  9. I tried posting one at a time...didn't work. LOL, the only one to post correctly was the manual entry. I have not reloaded the Machine Def yet. I'll give that a shot, TY!
  10. HELLO EVERYONE LONG TIME READER, 1ST TIME POSTER MORI SEIKI MV-50 MILL, USING X6 I'M HAVING AN ODD ISSUE TODAY. A PROGRAM THAT WE HAVE RUN 20+ TIMES THIS MONTH, WILL NO LONGER POST. THE POST PROCESSOR ATTEMPTS TO RUN, SAYS THAT IT HAS A POSTING ERROR AND THEN GIVES ME THE FOLLOWING .ERR MESSAGE; 30 May 2013 10:50:27 AM - <0> - Report created. 30 May 2013 10:50:27 AM - <2> - Initialize posting log file 30 May 2013 10:50:27 AM - <2> - Using MP run version 15.00 and post components version 15.00 30 May 2013 10:50:27 AM - <2> - Initiate opening the post processor file(s). 30 May 2013 10:50:27 AM - <2> - C:\USERS\PUBLIC\DOCUMENTS\SHARED MCAMX6\MILL\POSTS\MORI SEIKI MV-50.PST 30 May 2013 10:50:27 AM - <2> - The post processor file has been successfully opened. 30 May 2013 10:50:27 AM - <2> - Post version information (input): 30 May 2013 10:50:27 AM - <2> - UPDATEPOST Version 15. was used to modify this file. 30 May 2013 10:50:27 AM - <2> - The file was modified by this product on 11 Jul 12 10:09:30 30 May 2013 10:50:27 AM - <2> - The post was written to run with Mastercam Version 15. 30 May 2013 10:50:27 AM - <2> - The post product type is Mill. 30 May 2013 10:50:27 AM - <2> - Initialization of pre-defined post variables, strings, postblocks was successful. 30 May 2013 10:50:27 AM - <2> - Search for defined post variables, strings, postblocks was successful. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'dec_seq_right$' was re-initialized from 3. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'sub_seq_typ$' was re-initialized from 0. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'tplanemode$' was re-initialized from 2. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'bldnxtool$' was re-initialized from 0. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arctype$' was re-initialized from 2. to 6. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutput$' was re-initialized from 1. to 2. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arctypexz$' was re-initialized from 2. to 6. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputxz$' was re-initialized from 1. to 2. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arctypeyz$' was re-initialized from 2. to 6. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputyz$' was re-initialized from 1. to 2. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctype$' was re-initialized from 2. to 6. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutput$' was re-initialized from 1. to 2. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctypexz$' was re-initialized from 2. to 6. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctypexz$' was re-initialized from 1. to 2. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctypeyz$' was re-initialized from 2. to 6. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutputyz$' was re-initialized from 1. to 2. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcs$' was re-initialized from 2. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcsxz$' was re-initialized from 2. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcsyz$' was re-initialized from 2. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcs$' was re-initialized from 2. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcsxz$' was re-initialized from 2. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcsyz$' was re-initialized from 2. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'helix_arc$' was re-initialized from 2. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lhelix_arc$' was re-initialized from 2. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arccheck$' was re-initialized from 1. to 10111. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larccheck$' was re-initialized from 1. to 10111. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed4$' was re-initialized from 2. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed5$' was re-initialized from 3. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed4$' was re-initialized from 2. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed5$' was re-initialized from 0. to 1. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'sub_level$' was re-initialized from 1. to 0. 30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'peckacel$' was re-initialized from 0. to 1. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file. 30 May 2013 10:50:27 AM - <2> - Successful completion of posting process! I HAVE CHECKED OUR POST WITH OTHER PROGRAMS AND THEY HAVE NO ISSUES AND WORK JUST FINE. I'M THINKING THAT MY PROGRAM IS CORRUPTED.....ANY THOUGHTS? THANK YOU! -BC

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