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:

gms1

Verified Members
  • Posts

    789
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by gms1

  1. Im trying to setup my post and im having an issue with the peof section of the post. After each canned/tool cycle I have to insert a G30P3 at the end of the cycle. So at the end of each drill cycle you will see G80M9 G30P3 M1 This was an easy change to the pretract section of the post. Now at the end of the program I need to output G30P2 instead of P3. The peof section calls back to the pretract section first before I get my P2 output so I get this: M9 G30P3 G30P2 M30 My question is can I put a conditional statement in the pretract code that says if pretract is called from peof dont output the P3? code: pretract #End of tool path, toolchange sav_coolant = coolant$ coolant$ = zero #cc_pos is reset in the toolchange here cc_pos$ = zero gcode$ = zero pbld, n$, sccomp, psub_end_mny, e$ pbld, n$, scoolant, e$ pbld, n$, sg30, "P3", e$ #pbld, n$, sgabsinc, sgcode, "G53", "Z0.", e$ coolant$ = sav_coolant peof$ #End of file for non-zero tool pretract pbld, n$, sg30, "P2", protretinc, e$ comment$ #Remove pound character to output first tool with staged tools #if stagetool = one, pbld, n, *first_tool, e n$, "M30", e$ mergesub$ clearsub$ mergeaux$ clearaux$ #"%", e$ This would be an easy fix if I could control the coolant output between the pretract and peof section but the coolant shutoff command is output in the peof section at the end of a file.
  2. I can never wait long enough for the backplot window to fully load before I press S for step. So, I get quite a few crashes daily. I need some ridilin or less stress or something
  3. Ill be dropping an ma-600hb on the floor in a couple weeks. I cant wait as this will be my first horizontal machine.
  4. I can think of at least a dozen jobs off the top of my head that I could have used this on lol.
  5. I see it now I was picking the wrong t/plane picking the same plane as the toolpath itself. Man I never knew trim could do this to a hsm path thanks Rick
  6. quote: I put your file on the ftp site renamed it gms-pocket_RS.mcx I pocketed it with a containment and trimmed the toolpath to a closed profile and it cuts no air at all. i used a 1/4" em .05 stepdown for the example See if that is what you are looking for. I timed the work I did and it took me 2-1/2mins total. Wait! download this one it has the pocket cut you described gms-pocket_RS_2.mcx When it asks "pick a point on the side to keep" where do you pick a point because this isnt working for me with a 1/2 ballnose and wcs
  7. Ive tried everything I could to makea pocket toolpath for this thing and I can't get what I want. I uploaded it to the ftp under mx2 files -> gms-pocket.mcx I need to cut that pocket out and the part is already shaped to the 1/8 thick walls surrounding the pocket. I want to cut the pocket out without cutting a full size pocket as if there is material there above the 1/8 walls. I basically want to cut this pocket with the angle of the outside walls acting as som sort of upper boundry so the tool doesnt cut so much air while running. Is it possible?
  8. You should have toolpaths that go like this. WCS=Top TPlane/Cplane = Front Tplane/Cplane = Right Tplane/Cplane = Back (or left depending on how you rotated)
  9. You should be able to open the max file in rhino. I have rhino3 and there is an option to open .3ds files. So you could open the .3ds file in rhino, save as .3dm then open in mcam.
  10. Ive been thinking about trying out that cimco-hsm addon just havent had time. No thanks to 'renting' software.
  11. Thats what im talking about Robert. 'n_flutes' is not listed inside X+ available parameters so I can't add it to the output when I generate the setup sheet.
  12. Ok after looking at that list you can see 'n_flutes' which obviously means number of flutes. Is it possible to add this parameter to X+ so it prints this out for me? Second question is what is the parameter for 'chuck' in the tool parameters page? And whatever that parameter is, is it possible to add it to X+?
  13. I could never use red as its group color and it would drive nuts. Red, purple, and yellow are offlimits for me. Im partial to #3, #94, and #7 for a lot of things. Black background only.
  14. The info for the specific tools I already have. Its the definitions mastercam uses for all the different parameters for a tool. Im playing with the X+ setup sheet and I would just like to know what all the different parameters are that you can use with this thing.
  15. Im looking for the definitions of all the different tool parameters like tl_dia, tl_rad, tl_nr, etc. I can't find them anywhere. I have the v9 post ref guide and I looked through help and the documentation for x2. Where can I find this info?
  16. I usually do the overwrite install but with this version it has given me problems so I uninstalled everything and reinstalled. So far so good.
  17. For merging toolpaths I always use the import function. Right click in the ops manager window and select import. At the top of the screen that comes up you will get the file name which is usually the mill_default file. Click the folder button next to that and you can navigate to any folder. Select the folder your part is in. Then you get all the toolpaths in that file so you can select the toolpaths and import the geometry with the toolpaths and other options there. You wont get the geometry for the entire part, just the geometry for each specific toolpath you import. You even get to select where to place the geometry.
  18. Perfect! thanks a bunch guys
  19. I am trying to have my post output text and part numbers with a popup question before posting so It will be stuck in the header of the file. Ive done the search thing and found the definition from v9 but it doesnt help me format it to output what I want. I define the variable at the top of the post: job_no : 0 #Job Number I define the question string with: fq 3 job_no "Job number" I ask question in the pheader section: q3 I define the format in the pheader section: scomm_str, "Job Number - ", job_no, scomm_end, e$ And this is the result: (Job Number - job_no 2173.) I dont know how to format this thing to output correctly. Whether its text or numbers. This example uses this number 2400-2-225. What else do I need to do to get this output looking right? (Job Number - 2400-2-225) (Part Name - Door Hinge)
  20. Before I go bugging my reseller I was wondering if there is a mpmaster post for a horizontal okuma with an osp200 since we are getting a ma600 in november here. Also if this post exists are the super-nurbs functions in it?
  21. I voted to keep the topics from 2002. Just a few weeks ago I got e-mailed a question about something I did that was somewhat related to mcam back in 2003. There is so much info on the main forum related and unrelated to mastercam that is valuable info. The off-topic section on the other hand while some good info is in there, some of that could be removed.
  22. Yeah the pressing S thing was a big problem for me. I just have to wait for it load completely. Sometimes, it looks like its loaded up but its not finished and I still press S before its done loading then bam. Im getting a prompt hang like the cross hatch bug whenever I do fill holes also. I create the fill holes surface, save my file and the prompt window sits there with 'Select the boundary of the hole to fill' on the screen the whole time until I close mastercam and im not even in the fill holes dialog. Guess I can try a complete new install. Doubt this will work since the hatch thing ive had since x.
  23. code: ID cnc00028587 Product Design Version X2 MR2 Major Category Create Minor Category Drafting Sub Category Hatch Description Open the attached file. Create-> Drafting ->Create X-Hatch Green check to accept the default cross hatch settings. Chain the rectangle and click the green check in the chain manager. The cross hatch gets created. All is well. Machine Type-> Mill-> Default Toolpaths-> Contour Toolpath Note the "Cross hatch: calculating cross hatch" prompt window opens. As you go thru the motions of finishing the toolpath the prompt keeps popping up. This problem still exists. Create a cross hatch. Save file. The 'Cross hatch: calculating cross hatch..' prompt pops back up and stays there until you close mastercam. It stays up even if you delete the hatch. Another bug. Select toolpaths, click backplot icon, press 'S' for step control while backplot window opens and mastercam will crash everytime with an 'unhandled exception' error. Just a heads up.

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