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:

TFarrell9

Verified Members
  • Posts

    95
  • Joined

  • Last visited

Everything posted by TFarrell9

  1. I have a boring mill operator who's 3 years into machining making $35/hr. So yeah, I'd say you're underpaid....I know I currently am, but expect it to change soon (I'm the department manager and programmer, coming up on 14 years in the industry). Granted, we're in the PNW. Like you, I started at $9/hr at a shop in Portland. I know even then, I was taken advantage of (I was 18 and just glad to get my foot in the door). Pay across the board has changed a considerable amount in the last few years in the region for this industry.
  2. It's just an open pocket with vertical walls. Mill vertical walls, steep/shallow changes, stepdowns, and boundaries made no change, but line/arc filter settings did.
  3. Well, I can't give you an exact answer as to why. I played with a few different settings, without change. But, when enabled Line/Arc Filtering Settings, it worked the way you want. Edit: I suppose it's worth noting to you that you'll essentially always want to use the line/arc filtering settings, or else you'll end up with a massive file. Tadsdwadsadwadswa.emcam
  4. I was using the feedrate checkbox for linear entry/exit and it caused the rapid motion transitions to feed (even in backplot). I unchecked that box and used the plunge rate in tool parameters and got the output I wanted. G2 X-3.1298 Y19.2925 Z3.8295 I-.2462 J.0434 G1 Z3.8795 G0 Z4.8162 X-2.9735 Y20.1788 M5 M9 G0 G91 G28 Z0. M0 (INSPECT TOOL) N100 G0 G90 G54 X-2.9735 Y20.1788 S477 M3 G90 G54 W0. G43 H5 Z4.8162 Z3.8795 G1 Z3.8295 F35. G2 X-2.7707 Y19.8892 Z3.7603 I-.0434 J-.2462 F62.45
  5. Thanks, I'll look more into this. I did search for "sav_pwcs" in the post, but nothing came up. I'm really close to what I want now. I had to specify a value in the "linear entry/exit" box in Linking Parameters then change the "plinout" section to look at "ptool_insp". However, the output is still a bit wonky. It would output a G1 in the work offset line, so I forced a G0 there. So now I just need it to output a G1 on the first commanded Z value that has the feedrate. G2 X-10.0323 Y20.1437 Z3.9325 I-.0895 J.2335 G1 Z3.9825 Z4.8162 X-12.2731 Y-20.1437 M5 M9 G0 G91 G28 Z0. M0 (INSPECT TOOL) N100 G0 G90 G54 X-12.2731 Y-20.1437 S477 M3 <------- Before forcing a G0, it would output the G1 here G90 G54 W0. G43 H5 Z4.8162 Z3.9825 Z3.9325 F25. <------- I need a G1 in front of the Z here G2 X-11.9502 Y-19.9997 Z3.8632 I.2335 J-.0895 F57.24
  6. I posted the ptool_inspection above. It's the section under the first blue text. I'm still learning how to use the forum and make a clear-to-read post. That was also the section I copied, but I removed the B-axis commands and tool-staging. I was able to force the work offset output by using *g_wcs rather than *pwcs. Still trying to figure out how to force a linear feed for Z and/or command the last feed on the first G1/G2/G3 line.
  7. I'm trying to get a tool inspection point setup for one of our boring mills. I've copied what Gcode took from a Haas 5X post and started making some changes. I can do really simple post editing like forcing code output and moving things around to where I like it, but when it comes to "arguments" or logic, I don't know what I'm doing. I have something really close to what I want, however I cannot get a posted result from pwcs. I've tried using an asterisk as well as putting it in it's own line and it will not post. I'm hoping one of y'all can help point me in the right direction. Here is the post section I currently have: ptool_insp #Tool Inspection Point Customization Required #Modify following line to customize tool inspection points sav_absinc = absinc$ absinc$ = one pbld, n$, sm05, e$ pbld, n$, sm09, e$ pbld, n$, *sgabsinc, *sg28, "Z0.", e$ pbld, n$, "M0", "(INSPECT TOOL)", e$ absinc$ = sav_absinc if mi1$ > one, absinc$ = zero pbld, n$, *sgcode, *sgabsinc, *pwcs, pfxout, pfyout, [if nextdc$ <> 7, *speed, *spindle], pgear, strcantext, e$ pbld, n$, *sgabsinc, *pwcs, sw0, e$ pbld, n$, sg43, *tlngno$, pfzout, pcan1, scoolant, e$ prapidout #Output to NC of linear movement - rapid pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, pccdia, pxout, pyout, pzout, pcout, strcantext, scoolant, e$ #Modify following line to customize output for high-speed toolpath #tool inspection/change points if rpd_typ$ = 7, ptool_insp #pbld, n$, "M00", "(TOOL INSPECTION POINT - POST CUSTOMIZATION REQUIRED)", e$ Here is a snippet of the output: G2 X-10.0323 Y20.1437 Z3.9325 I-.0895 J.2335 G0 Z4.8162 X-12.2731 Y-20.1437 M5 M9 G91 G28 Z0. M0 (INSPECT TOOL) G0 G90 X-12.2731 Y-20.1437 S477 M3 <----I want pwcs to output in this line G90 W0. G43 H5 Z4.8162 Z3.9325 <----How can I force a G1 and last commanded feed rate here? G2 X-11.9502 Y-19.9997 Z3.8632 I.2335 J-.0895 G1 X-11.7634 Y-20.0713 Z3.86
  8. Our horizontal posts are based off of the Generic 4 Axis Mill Post, so I'm uncertain if there are major differences, but in mine it's under the pnull_retract section.
  9. Use incremental values and check the "calculate depth from top of stock" box under the "depth" box.
  10. My main complaint with Lathe is I haven't found a way to switch between related toolpaths. I like that Mill has the Toolpath Type window at the top and I wish Lathe had that. It's really only a minor inconvenience sometimes, I just wonder why that isn't an option in Lathe? Unless it's right in front of me and I just haven't noticed it.
  11. My high speed toolpaths and stock models will dirty when I change the program number (in 2022 and 2023) and it drives me nuts. It's also annoying how stock models dirty when a speed/feed change is made.
  12. My last name is Farrell.....my arms aren't super accurate lol I'm sure you mean Pharaoh arm. I always go out and measure things you like you said you do. I don't really see a way around it. Even with a casting model, the castings themselves can deviate a considerable amount as you know.
  13. In my experience, plane commands are cancelled/invalid with G112 because it's a canned-cycle that only functions for the specific plane. G112 is for radial and G107 is axial.
  14. Your entry minimum helix radius is more than likely too big, as well as your XY clearance. Change it to .005" or .01" and change your XY clearance to .005" or .01".
  15. Yeah I ended up really having to wedge them together to get it to post two ops/tools on that first page. I also had to change the "ncfile-short" to 6pt font. I tried deleting it, but it was giving the me "unhandled exception" error, which is odd, because I deleted it from my Mill setup sheet without issues. Same thing with "ncfile-long" on the header page.
  16. I discovered that after the first operation and tool, it will post two ops/tools per page.
  17. Hey All, I got the Active Report setup more or less how I want it, except for the Lathe tool list. I've attached the sample that I have so far. I've condensed the tool and op info so I can ideally fit at least two tools per page, however it's only posting one op and tool per page. I've seen the Varco Reports, so I know it can be done, I'm just not sure how. I've tried manipulating the "shapes" and "data" sizes, but I can't seem to get more than one per page. Does anyone know exactly how to accomplish this? Lathe Setup Sheet Sample.pdf

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