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:

Leaderboard

Popular Content

Showing content with the highest reputation since 03/21/2024 in all areas

  1. Right, there's no way to force it inside of the toolpath parameters. You can, however, leverage the fact that it is stock aware to cause it to drop into a position you'd like. Create a Helix Bore (or drill, or whatever you want your entry to look like) at the specified entry point, then, make a stock model. Pocketing will use it to drop into: Video showing it in action:
    7 points
  2. To use your car example, though, call up BMW, and see if they'll give you a new ECU for your 2009 325is? If it's NLA (no longer available) as a lot of the 90s/2000s electronics are, ask them to just put in a new model's version. When you ask for the ECU, they'll try to (kindly) tell you that it's no longer made, "Talk to junk yards and see if you can find someone to re-key it for you" (i.e., go try to find someone who switched to a software license that can give/sell you their old hasp). When you ask them why doesn't the 2024 ECU "just incorporate that into the new one so it can work on 15 year old cars?" they'll laugh at you. That's not a practical use case, and it would require tons of engineering to support a very slim "customer" base. X5 is ~15+ years old at this point. Unfortunately, you're talking about jamming a new ECU into it. They started supporting software licenses in the 2019 release, which was made ~7 years ago. The software that powers the licenses now wasn't even in existence when X5 was programmed. To put it bluntly, if you only have a 15 year old version of the software that you haven't maintained, you're not really a customer anymore. I can understand why you're upset, but the reality is that it's hard to justify engineering effort for someone who only buys a product once every ~15 years... Same thing people get told when they try to get BMW to cover a blown transmission in their 15 year old car.
    6 points
  3. Maybe a servo-modded knee mill with a 4k spindle and DRO can't handle 2D dynamic ruffing? Dunno. Wouldn't be surprised if it was that kind of issue though... Buddy came in pretty hot, not really asking for assistance. I don't know if it comes from a place of technological ignorance, or wanting/needed something to work just as it has for a few years. EVERYTHING wears out eventually, gotta have a plan in place for when the failures materialize!
    5 points
  4. Instead of editing the jump heights, try using "automatic linking" on the Linking page.. It's more betterer.
    5 points
  5. All was well - but I had to play to get to grips with the settings. And confidence....as Bus partner was still of the belief that you get the largest cutter you can and plough it through the part shaking the machine to pieces and sod consumable cost and part distortion But....it was faster than I thought - F2250.00000000000000HHHHH https://www.youtube.com/watch?v=_PZHd73Ovis
    3 points
  6. Haha, yeah! I showed these guys how to use Dynamic on some wear plates (4140 PH?? I can't remember), either way, took the cycle time from 27 minutes down to like 3... And ended up just letting the stuff pile up and snow shovel it off the floor every half hour or so. You couldn't stand within 10' of it while it was cutting. I hate open machines.
    3 points
  7. You're welcome sir. You can do the same thing with an Opti toolpath in 3 axis, as they're really both just volumetric removal tools. The only thing that trips people up is that they try to drill too small of a hole (the tool can't plunge and then start its programmed stepover) or they use a 118° drill bit, and leave a "cone" at the bottom. The software will see that, recognize that it can't plunge the tool into that and then go back to "it's a full block" mode. That's why I prefer to use a Helix with the tool I'm going to be roughing with as I know it'll fit in the hole it makes
    3 points
  8. Again you don't provide a file. Here is a sample like yourS with 4 bosses. Only goes up to start the next depth outside the part like it should since the stock is define correctly. Again you keep thinking were the idiots with that arrogance you keep not realizing you are putting out. No file and keep prompting two different CAM Software means you're a shill or a pirate. BIRD FLEW THE COOP REALITY CHECK
    3 points
  9. Mastercam will use the graphics card for certain calculations during HSM (High Speed Machining toolpaths) such as Opti, Waterline, Equal Scallop, etc. via the OpenCL (note: C, not G) standard If you're benchmarking programs using the GPU, look for GridComputeServer.exe, as that's the process that handles the GPU utilization: https://my.mastercam.com/knowledgebase/opencl-troubleshooting/ In practice, the calculations being done on the GPU are so trivial for it, that you have to be really logging a lot to notice a blip. The first question people have about using GPU processing is "Why aren't you doing ALL of the calculations on the GPU then!??!?11" The truth is the majority of the time savings of using the GPU for stuff like this is taken up by the operational overhead of managing the data and handing it back and forth from the GPU.
    3 points
  10. I've put a bunch of my most commonly used functions on the QA (Quick Access) bar. It's very easy to add or remove functions from the QA bar so I'll add or remove them as my current project requires.
    2 points
  11. The Good Old Old Days Of Dodging Hot Chips and Coolant ,Or at the least Using The Wood Or whatever As a shield While Using A Spray bottle for Coolant Sprays!
    2 points
  12. I know several small shops that do just fine without CAM. One shop has a bunch of bar feed Okumas. If you know anything about Okuma lathes, you'll know their canned roughing/finishing cycles are world class. They got along fine programming at the control and the owner is doing very well for himself. Occasionally they would get a part that had geometry issues the Okuma control couldn't solve. He'd give me a call, I'd whip out a finish toolpath and a bill for a 1/2 hour minimum of $45. No doubt it could have all been done better with Mastercam or some other CAM software but he didn't want to invest the $$ to buy it or the time to learn it. Eventually, he hired a guy with a cracked copy of AutoCad and they started using that to solve math the Okuma control couldn't handle. That was one more customer gone.
    2 points
  13. When I was a kid in Saudi Arabia, people would cut your throat for Double Bubble... even though it had been in transits so long it was rock hard. When I got to the states and bought some fresh chewing gum, I thought something was wrong with it cause it was soft.
    2 points
  14. Oh man, I gotta check the grandparent's basement now. Also makes me wish I had bought an IBM XT with a board instead of a bare chassis a few years ago, it's destined for a modern gaming rig so it only had the PSU inside. Never thought about reselling the innards at the time.
    2 points
  15. I usually back their numbers off to about 70% to start and see how it responds on the machine/ part.
    2 points
  16. You're right, and that's why they haven't used them for quite a few years now. In all honesty, it sounds like your mind was made up from the beginning anyways. I'm curious though, what is this "new stuff" that's way too slow and doesn't work in "real life"??
    2 points
  17. Thanks !!! That is good to know. I hadn't thought of that. My managers have this project scheduled to run on a horizontal boring mill old school plunge mill roughing or maybe rough, index, rough etc etc. I know for sure that it is not capable of running a B axis dynamic roughing path My test file posted at 21meg... for one of two slots LOL!!! I put this sample file together to demonstrate what modern toolpaths and a state of the art Okuma 5X HMB can do. I'm still working on my demo and sales pitch. What I really need are realistic feeds, speeds and stepovers DOC is 2.25, Material is Ti ( don't know full specs yet) endmill is a 6 or 7 flute Ø1" bull /.06r Tool holder is an HSK125 RegoFix Secure Grip... or maybe a heavy duty hydraulic chuck. Up to 500 or 1000 psi though coolant is available. I've tried HMS Advisor and Helical for feeds and speeds. HSM seems realistic but a little slow,, Helical at even half recommended feeds and speeds is stupid fast.
    2 points
  18. IF you're connected to the interwebz, try rolling back any updates. Then if this works, unplug from the interwebz and NEVER plug it back in....
    2 points
  19. Legal; Neither me, nor my company are responsible for any paramters yiu change. Your machine is your responsibility. It is advisable to consult a competent Machine Tool Applications Engineer that is familiar with your machine. Without further adieu, some of my favorites are as follows: #929=1, 1=Always make FTP Data in Attribute = ASCII #1300.1 = 1 Handle Jog OT alarm not output. (NAL) #1401.1 =1 No dogleg rapid (LRP) #1401.4 = 1 Rapid Stops when Feed Override is at 0% (RF0) #1604.0 = 0 AICC not on always in Auto Mode. (SHP) #3106.6 = 0 During TWP or WSEC, "Absolute" position display is Program Coordinate system (DAK) #3203.6 = 0 - Do Not Delete MDI Program after execution (MER) #3203.7 = 0 - MDI Program not cleared by reset (MCL) #3204.6 = 1 - Do not Automatically erase MDI program. (MKP) #3207.5 = 1 Display #500-#549 MACRO Variable Name (VRN) 7 #3233.1 = 1 (PDM) Folders in the Dataserver can be set as the foreground and background folder #3301.7 = 1 Screen Capture Enable (HDC) - Hold Shift for 5 sec. #5004.2 - 1 = Diameter, 0 = Radius for CC. (ODI) #5013 = MAX Wear Offset Value #5014 = MAX INC Wear Offset Input (INP.+ Method) #5148 (VMC Boring in Z-Axis) Z 1 = Shift X+ -1 = Shift X- 2 = Shift Y+ -2 = Shift Y- ALL other axes = 0 #5200.5 = 1 High Speed style peck tap (PCP) #5202.0 = 1 for Spindle Orient prior to rigid tap (reboot req.) (ORI) #5213 = Rigid Tap Backoff Dist. #5400.5 = 1 (LV3) Rotates MACRO Variables to be read in active coordinate system - For Probing in TWP. #6001.3 = 1 Output all MACRO Variables on punch (PV5) #6001.6 = 1 #100-#199 not cleared on reset. (CCV) #6005.0 = 1 In Sub Program Call use Sequence Number (SQC) #6008.3 = 1 On reset, POPEN is closed (KOP). #6019.0 = 1 Output all variables as decimal number (MCO) #6019.3 = 0 File Format of output file =PRNTnnnn.DAT (OFN) non =0000-9999 #6019.7 = 1 File Format of output file =PRNTnnnn.DAT (SFN) non =0000-9999 is memorized. #11200.3 = 1 system variable #5061- #5080 Skip Coordinates can be read - for probing with WSEC active (WSK) #11350.1=1 Current section of program only displayed, not look ahead section (APD) (Requires Reboot) #11351.6=1 Parameter Group Names Displayed (GTD) #13451.1 = 1 TWP 0's ok. (ATW) #14701.5 & .4 = 1 Maximum clipboard size. (CLP) (Reboot Req.) #14853.4 = 1 - Able to transfer from memory card to Dataserver. (Reboot Req.) (MDO) #14854.6 = 1 Program Input/Output is enabled during Background Editing (BGO) #19746.4 = 1 (TBP) for G41.2/G42.2
    2 points
  20. Something definitely looks wrong with your G68.2 lines. It looks as if they have the post setup for a C Axis machine, rotating around Z. The order of rotations for Eulers Angles should be Z, X, Z again. The J's look good but the I's don't
    2 points
  21. As long as you understand what MockSim is and is not, what Vericut is and is not, what CAMplete is and is not you can make educated decisions about what fits your need. MockSim doe NOT check G-Code. Tied to a Postability post it is a good solution for most things. Again, it's not fully simulating ALL the motion in your machine like M-Codes, etc... Vericut... they simulate the actual G-Code that will run in your machine. As good as your control file and machine stuff is determines how good your simulation is. By and large it is the gold standard for simulation. You can create your own machines if you desire to learn or you can buy them from Vericut, or you can hire someone to build them for you. YOu have choices. Vericut is NOT an integrated post processing solution so you will need a post either from your CAM vendor or from ICAM, or somewhere else. CAMplete... they simulate the G-Code created from their posted code. You cannot import and edited code. CAMplete IS an integrated Post Processing solution that will simulate the factory G and M-Codes. You have almost as much control over your machine as you would in a Vericut machine. You have limited machine editing capability and you cannot create your own machines. That is not an anticipated feature. The machines are factory configured meaning Matsuura, Okuma, Kern, Mazak, Haas, etc... has given their blessing on the accuracy of the models, motion, and functionality. Because CAMplete is an intagrated Post Processing solution, you have control over the code. The NC Formats are user customizable. Typically a basic NC Format is given to the customer that will run the machine well. I've got a decade and a half's experience developing NC Formats and I've got highly tuned NC Formats that take advantage of the majority of the features and functions of the Matsuuras (since that95% of what I spend my time on) and I'm adding new stuff all the time based on customer requests. Knowing the tools, knowing their strengths, weaknesses and capabilites os the key to getting the best solution for you. For me, nothing beats CAMplete. For you, Postability and Vericut may be best, for someone else, MockSim will do the job. Know your tools.
    2 points
  22. Yep, I didn't show it on the screen (my bad!) I only put it in the comments on the video... On the toolpaths type page, add those to the "avoidance geometry"selection... Then auto linking should work fine.
    2 points
  23. The only thing I ever have really customized was my right click menu,.. other than that I just roll with the defaults. ehh probably not the best choice but it's all good.
    1 point
  24. Since the release of X, I live on the RMB....I go to the ribbon bar for VERY little, as such I haven't done anything with it. Of course at this point I do very little programming with my hands in so many things and management
    1 point
  25. I was pretty bitter about the interface change in the beginning. After a while I just conformed.
    1 point
  26. When I bought the lathes with Shopturn (this was 810D), I had looked at Fanuc Manual guide and laughed. And also wasn't "that" impressed by Mazatrol (on an Integrex i200). The Siemens was awesome, and latterly fully endorsed by the late Tim M. I never looked at the Okuma though - didn't know anyone in the UK with one but was also far too spendy for my short arms
    1 point
  27. Our C-Axis lathe has a Siemens 840D controller on it with shop turn software. The Shop Turn software is really powerful and easy to use. We have MC lathe license but the Shop Turn software for R&D one offs is really convenient as you can "copy", "cut", "paste" from existing programs.
    1 point
  28. Saw these guys at IMTS last year. They had some little baby right angle heads they were demo'ing. They're available to us through our mitsubishi rep. https://www.mst-corp.co.jp/en/home/angle_head-top/mini/
    1 point
  29. I am a big fan of Lenovo! Maybe it's because I get a massive discount through my wife's employer. The previous company I worked for used Lenovo mobile workstations and they worked flawless. Thought we had them replaced every two years, just to keep up with technology. My new employer chooses HP Zbook workstations. I can't stand them! I have not used a desktop for almost two decades due to my job requirements of being mobile. I have enjoyed my Lenovo mobile workstations! I have never used a Legion, so I could not say anything about them, but I highly recommend the Lenovo workstations. I even bought my own Lenovo P17 fully stacked ($8k+), wifey job got it down to ($3600) just to have at home.
    1 point
  30. Running a repeat Ti6AL4V job at the moment in our measly HAAS UMC500. Using KMetal UDDE hognose cutters. Can't do the depth of cut you require due to machine tool rigidity but we get good tool life in 3d Opti milling at 2xD depth, 7% step over, 90m/min surface and 0.15mm per tooth feed.
    1 point
  31. That was a heavily modified machine....I had a fab company next door and I had a powder coater as a supplier. So one Sunday morning armed with cardboard and masking tape, I removed/scrapped all the original guarding and made cardboard templates. The front plastic guards had a couple of pins sticking out the bottom so I could lift them out the way and they ran in a channel so I could slide left to right. Worked well. Another Sunday gone though.... Top tip for the cardboard guarding is to first coat it with parcel tape - keeps it waterproof for a surprisingly long time....
    1 point
  32. ProtoTrak DPM SX5 was the first NC machine I ever ran, ~2013, fond memories. Would be a messy job running HSM toolpaths on an open machine! We had to get out the cardboard box panel to deflect the facemill chips back then, lol.
    1 point
  33. Thanks for the Novo tip I didn't know Kennametal had a feeds and speeds app I'll be signing up for that!
    1 point
  34. Bottom driving surface problem, rotate it or re-establish it to avoid the "position" of the "hidden" boundary line of the surface Make it not exist (if it is a 360-degree surface, there is no way to eliminate it, it must be there, you can only change the position) I don't know the English meaning, but my understanding is this...
    1 point
  35. the problem probing at angle may not be the lack of software it seems... If not, it may likely be connected to my post processor not agreeing with the machine! I have been getting movement out of travel on the g68.2 line. the B axis on the head wants to08.nc turn upside down! In case your curious... The V536 file is code that worked for another dept. found on this machine. I have the team at inhouse solutions looking at it for me. I'm sure we will get it straight. s. V536LHB
    1 point
  36. #5400.5 = 1 (LV3) Rotates MACRO Variables to be read in active coordinate system - For Probing while TWP is active. Interesting about being out of range. In a few machines I've encountered over the years, for some unexplainable reason, I've had to set #1301.7 = 0 Stroke Pre-Check Off because for some reason the control thinks it is going to overtravel while TWP was active. It's only been on certain FANUV CNC Series and Edition Softwares. But the machine never did overtravel. High Level Math... one of the great mysteries for me.
    1 point
  37. James, I haven't a clue why. The factory doesn't respond to questions of such magnitude. But it isn't just us. The Renishaw manual clearly states the need and use of these 2 parameters leading me to believe that having them on all the time is not universal.
    1 point
  38. Lie .... make your drive geometry longer than the actual part so the plunge move is safe.
    1 point
  39. Looky there. Way easier than jump heights. It's funny to hear my methods as something from "waaaaaay waaaaay back" LOL Can't believe I didn't look over there and see Avoidance Thanks again guys
    1 point
  40. I agree with James. Been using Camplete now for a while and have had no issues. I let the install add Fusion but have never even opened it up. Camplete is well worth the investment.
    1 point
  41. The specs alone take it away from a gaming rig... If you're doing workstation work, buy a workstation.....if you're gaming, buy a gaming rig... That's just how I approach it...
    1 point
  42. Yep, you guys are correct on the Machsim/Postability integrated version. There is a reason for the confusion, as confusing as that is! MachSim (by MolduleWorks) has its own post processor (it has to, or else it couldn't figure out how to interpret moves from the CAM system). It's called MultiXPost (https://www.moduleworks.com/software-components/utilities/ppframework/) When you launch "Normal" Machine sim, it's using the MultiXPost to generate moves. As long as it "guesses" the same movements that your Mastercam post will make, you're good to go! If it doesn't guess correctly, though, you can be in for a surprise. An example would be that you're on a B/C machine, and MultiXPost guesses that your toolpath needs B90 C0, but, when you post out of Mastercam, it goes to B-90, C180. Both are valid solutions, but one could cause a problem and one could be fine. What the "add on" allows you to do is to swap out the MW Post Processor for the same MP post processor you'll use in Mastercam to generate the NC, so that the moves that are fed into MachSim are ran through the same engine that will write the code. That means, the X/Y/Z/A/B/C moves are calculated the same as they will be on your machine. You should always see the same B-90 C180 in both (to use my above example). The downside is that it's not simulating M codes, etc. If you have an m-code on your machine that causes the C axis to reset the counter or something, it won't see it. Probing? Won't see it. Tool changes? You guessed it. HPCC causing weird motion? You're not going to see it. You're only seeing what the toolpaths generate. The upside is that because it's not as complete (i.e., requiring a control model to simulate the control state) of a solution, it's a LOT cheaper, and because it's integrated, it's quite fast to check setups and motion. Your Mastercam reseller can give you a final price, but I believe for a "normal" 5 axis machine, it's somewhere in the $3-5k range. What I often tell people about a 5 axis toolpath: Backplot? 50% confidence that it'll run without crashing into something MachSim? 75% confidence MachSim w/ Post Integration: 95% To get to 100% confidence, you really need Vericut/NCSimul/CAMPlete/etc.
    1 point
  43. If it were me I'd post a file to prove my legitimacy.....
    1 point
  44. straight machine sim? yes all the time Postability Machinesim is much better, One thing Vericut does than Machine Sim can't is Autodiff
    1 point
  45. I use Machine Sim from Postability on our Okuma 5X HMC's It is linked to the post but I don't believe it runs on actual gcode. It is very useful for instantly checking the stability and smoothness of 5X toolpaths. Of course the final program goes through Vericut before it hits the machine.
    1 point
  46. No never used it and posted over 19,500 postings that helped not a single person in the last almost 21 years of being on this forum. Again post a file glad to help I guess you cant read that due to your poor English? I live in a tri-lingual house so really annoys me when someone try to use that as an excuse. 沒有人從未使用過它,並且在過去近 21 年的時間裡,在這個論壇上發布了超過 19,500 條帖子,沒有對任何人有任何幫助。 再次發布一個文件很高興能提供幫助,我想您由於英語不好而無法閱讀該文件? 我住在一個講三種語言的房子裡,所以當有人試圖以此為藉口時,我真的很惱火。 上傳一個包含刀具路徑的主文件,然後我們就可以說同樣的語言了。
    1 point
  47. That will be it's death knell if you ask me.... This company will NOT utilize software that is subscription based.....Autodesk was already dropped...Materialise is about to hit the curb...if a perpetual license isn't available it won't be here.
    1 point
  48. How many serious crashes cost less than $4,500.00 to get going again? Saving even one major crash would likely pay for itself. Another post mentioned MachSim is 98% as capable as Vericut. Not sure how different that is from Camplete but seems MachSim would be an excellent investment.
    1 point
  49. M/C remembers all settings made in the previous toolpaths in the same file...even comp type. I don't know if there is a setting in config that will force M/C to reset all settings
    1 point

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