Verified Members
  • Content count

  • Joined

  • Last visited

Community Reputation

13 Good

About Delcandoit

  • Rank
  • Birthday 06/27/1974


  • Location
    Washington State

Recent Profile Visitors

255 profile views
  1. Probing with G68.2

    I'm trying to figure out why you are using G68.2 in this situation. The Tilted Workplane created by the G68.2 in the program sample you provided uses the same origin and axis direction that the workpiece would normally have at A-90. C180. on your machine. It took me a bit to discern your parts orientation from your description but I think I have it right and I'm assuming that you have a table/table machine. In Mastercam the Tool Plane is basically an upside down Front View right? Tool Plane X, Y, Z = Mastercam -X, -Z, -Y if I'm reading the code correctly. After the rotation you described the Tool Plane matches Top so Y+ on your program will be Y+ on your machine, so on and so forth. Depending on your control there are limits to what you can do while G68.2 so you end up creating more problems for yourself in the end. My control doesn't allow the origin defined by G68.2 to be shifted so incremental or machine coordinates are the only options.
  2. Mastercam Supersitions

    I save before making a stock model or verifying. (or most anything) I close and restart my computer every 4 hours to stave off the inevitable crash. I happily realize that every problem I report "will be addressed in the next release".
  3. I've managed to get the logic implemented to our Mill post except for the "use_oal" logic. I'm having trouble tracking down where the math is done to offset the toolpath by the RAH gauge length and the tool overall length. I am using the MPRouter post as my inspiration and I have it narrowed down to the pxyzcout3 area, more specifically za and zshft. Does anyone have any reference documents they could point me towards for shift maps and mapping coordinates? We are an AS9100 shop with a very rigid QMS that dictates which code, and posts, we're allowed to use or I would just post with router and doctor the end code for HAAS. No doctoring allowed outside of Mastercam unfortunately. I have all of the values pulled for what I need, now it's just the vector math using our HAAS post. Any nudges and guidance is greatly appreciated. Format:HTML Format Version:1.0 StartHTML: 165 EndHTML: 5913 StartFragment: 314 EndFragment: 5881 StartSelection: 314 EndSelection: 314 pxyzcout3 #Multisurf rotary axis motion & toolplane if ra_type$ = 0 | fmtrnd(lng3(ra_svecx$) = zero), [ #If you're not using the C-hook... #your not getting C-Axis! csav = zero !cabs, !cinc ] else, [ if fmtrnd(vecz) = one, [ c_tmp = atan2(m2$, m1$) xshft = vequ(vzerox) ] else, [ csav = atan2(-ra_svecy$, -ra_svecx$) ptfixx$ = vequ(vzerox) axisx$ = vequ(caxisx) tvecx = rotv(-csav, vecx) csav = atan2(tvecy, tvecx) axisx$ = vequ(caxisx) c_tmp = csav csav = atan2(vecy, vecx) irotv = rotv(-csav, vecx) bsav = atan2(irotv, krotv) #Apply tool length #(G43 is set with tool in Vertical for CA Head) xshft = vequ(vzerox) if ra_type$ = 1 | ra_type$ = 2, #If right angle or compound angle aggregate [ if use_oal, zshft = tl_oal + gauge_length #Captured from 20007 & 20008 parameters ] axisx$ = vequ(caxisx) axisx$ = rotv(csav, baxisx) ptfixx$ = vsub(xa, xshft) xa = rotp(bsav, xa) if set_g43_vert = 0, za = za + zshft if set_g43_vert = 2 & ra_type$ = 1, za = za + zshft ] csav = c_tmp ]
  4. As usual Colin, you're awesome. I thought that I had done all of that already and no matter what Tool Axis Length I used there was no change in the code. I also got a G17 on line N9 in the sample code I posted. But, I have a feeling that I'm jumping the gun and that I need to read your well laid out tutorial a bit better and it will be clearer. Thank you for responding and I hope that the everything is still going great for you in CT. Sorry for almost falling asleep in your Post class, jet lag and all lol.
  5. Good Day, I have searched the forums for this subject and I wasn't able to find what I was looking for, so here we go. We run all HAAS in our shop and I currently have some solid 3, 4, & 5 axis posts that output what we need. We are getting 2 indexable aggregate heads and 1 Right Angle Head here shortly and I would like to add the correct functionality to our existing posts. I understand the programming of the heads and I have added an aggregate component to the Machine Definition within Mastercam. I have set my planes as I would with rotation Ex: WCS: Top C/T: Right. I have gotten an angled head within the toolpath and all of that good stuff. G19 posts in the safety line but reverts to G17 further down. It also doesn't seem to recognize the tool axis length. I converted a router post to Mill and it seems to output correctly but I'm not sure how to add that functionality to my existing posts. I know enough to be dangerous with posts and I pretty much just need a solid nudge in the right direction please. N1 T14 M6 ( T14 - 180.00 / 90.00 - STATION # ) ( RAH TEST PATH ) (OP.1) N2 G0 G19 G20 G40 G49 G80 G90 N3 G0 G90 G54 X1.9375 Y2.875 A0. S5000 M3 N4 G43 H14 Z2. T4 N5 M8 N6 Z.2 N7 G1 Z0. F5. N8 G41 D14 Y3. F10. N9 G17 G2 X2.5 Y3.5625 I.5625 J0. N10 X3.0625 Y3. I0. J-.5625 N11 X2.5 Y2.4375 I-.5625 J0. N12 X1.9375 Y3. I0. J.5625 N13 G1 G40 Y3.125 N14 Z.2 F15. N15 G0 Z2. N16 M9 N17 M5 N18 G91 G28 Z0. N19 M1
  6. Which toolpath should I use?

    I will try to get one up ASAP. I'm burning the midnight oil keeping the machines fed atm. I will try by lunch tomorrow. Thanks!
  7. Which toolpath should I use?

    Hello all! I have one of those "What toolpath should I use" types of questions. I have a thin wall ITAR part I'm working on that has rigidity issues due to being on a 5-axis out of necessity but forces some pretty long tools and such. Many deep pockets with acute angles and the like. Long story short, I need to be able to drive against surfaces and use thin wall techniques. The pocket in question would be an open pocket, 0.06 walls, and acute angles. Dynamic Core with a thin wall finish pass similar to a Surface Rough Pocket that can be driven against a 3D model would be the perfect toolpath. When using the Surface Rough Pocket I have to go inside out or outside in and this is more of a Waterline open pocket. Since it is ITAR I can't share the file but I will try to work on a dummy file to give a visual. So, is there a toolpath that can rough with dynamic/opti and take 2-3 finish steps for every rough step?
  8. Invalid tool

    Same issue here, any solutions?
  9. Tool Manager Glitchy?

    I just sent this issue in to my reseller and he has passed it on to CNC Software. Some tools with drag and drop without an issue and others will not. I haven't found a rhyme or reason just yet and I'll post their reply once they give us an answer.
  10. STL is even more horible

    The problem that I have with Stock Model is that it works fine until things get more precise and the models are more organic with many different toolpaths. It is a fantastic tool when working with simple parts or a handful of toolpaths. I work with multiaxis complex shapes with at least 100 toolpaths. The first few stock models are great and then it just starts spinning and crashing after it gets more complex. This has happened in all versions of X7, 3 entirely different computer systems, and default settings, posts, etc... I have worked with my reseller and Mastercam for months on this issue and there have been no answers or resolutions to the problem. I still love stock models and I use them all the time. I just can't use them on my more complex jobs.
  11. Traking MC, users, dates, times etc.

    We have had similar issues here. We have it setup now to where the programs, NC, and setup documents are on a server that only the primary programmers have write access to. If someone on the floor makes a change they have to save it to a temporary folder and notify our department by email that they made a change, who authorized it, etc.. If we make a change within programming we ghost the original toolpath and create an entirely new toolpath with the requested edits. The geometry, if any, are on a separate level as well. Then we create lettering on another level saying what was changed, why, when, and by who. This isn't the slickest system by any means but it works for us so far. It's an honor system but if I had someone I couldn't trust to follow that system in my department, they wouldn't be in my department much longer.
  12. "Error occurred in EndSession" Verify problem

    I'm glad that posting this has been helpful to some people. When I contacted my reseller and CNC Software this was an issue that they hadn't heard of before and we really had to do a lot of troubleshooting before finding the problem. This just goes to show that we can't fix a problem unless we know about it. Report all issues to your reseller and the more those reports show up at CNC Software, the more likely they will be addressed. Happy programming!
  13. Need a programmer!

    Right offer, wrong time unfortunately I'm deeply seated where I'm at with my recent promotion to programming lead and a bit too far North. I will put my ear to the ground for good programmers looking for work in the area. Unfortunately, multiaxis programmers that are worth a salt are few and far between. I'm going to forward this to my local Mastercam reseller Steve Kidd, he knows everyone.
  14. adding groups to the solids op manager

    Without a doubt that would be very useful. I usually reach several dozen solids in any given file. I rarely use the solids tree because of this honestly. I just remove solid history, modify, then do it again. It takes less time than trying to find the solid I need. Is it copy of solid? Or is it copy of copy of copy of solid? hehe

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