Aaron Eberhard - CNC Software

CNC Software
  • Content count

    686
  • Joined

  • Last visited

  • Days Won

    1

Aaron Eberhard - CNC Software last won the day on January 28

Aaron Eberhard - CNC Software had the most liked content!

Community Reputation

381 Excellent

2 Followers

About Aaron Eberhard - CNC Software

  • Rank
    Advanced Member

Uncategorized

  • Location
    Tolland, CT

Recent Profile Visitors

2,283 profile views
  1. Aaron Eberhard - CNC Software

    3D Connexion Buttons Not Working

    These are also in your start menu under 3d connexion > Stop Service & Start Service. I've been lucky, it's been a few years since I had to mess with them!
  2. Aaron Eberhard - CNC Software

    Mcam on my Surface Pro not starting

    Disclaimer: What I'm about to say is TOTALLY UNOFFICIAL.. That means this is not endorsed by CNC Software what-so-ever, just my own personal anecdotal experience. Don't bother your reseller or tech support about it, they'll just laugh at you and tell you to buy a real video card --------- While doing testing previously, I discovered that using the Intel video driver series 21.xx will work fine even with 2021. There's a known problem with Intel's OpenGL implementation that started with series 22.xx drivers that affect us as well some other software with it. Either way, I'm not sure what damage you could cause to backdate your Intel graphics driver to 21.xxx on a modern machine as I think it's about 3 years old, but that may work for you.
  3. Also, make sure you're asking questions like this to our API team... They're sort of our direct "customer" for this sort of thing (if that makes sense to you), so it's always good to be in touch with them so we know how in-demand work like this is when I'm trying to plan out our year..
  4. I know you already figured out the way to make this, in particular work, but I wanted to let you know that I'm not aware of any way to do a duplicate geometry check at regen time, currently. Duplicate filtering is (and has been) on the selection side, not on the toolpath generation side. That said, this sort of thing is one of our goals during refactoring so in the near future you should have access to everything in the toolpath hole definition panel in a very modular manner. The sorting engine, masking, duplicates, etc.
  5. Aaron Eberhard - CNC Software

    3+2 drilling

    This^ Disclaimer: I didn't look at your file... The biggest thing to keep in mind in Multiaxis is how to answer the questions "Where to?" and "Where from?" For example, if you tell a machine to rotate to A90° (where to?), what is that 90° relative from (where from?) (i.e., where did you have your A0° defined?). Mastercam handles this with the WCS (Where from?) and the Planes (where to?). So in your part, you don't have to physically move the model to 0,0,0, just like in 3 axis, you can move a WCS to where the part is going to be mounted in the fixture, and make planes relative to that if it saves you effort. The other thing to keep in mind is that the default planes (front/left/right/back/etc.) may not match your machine's kinematics. A90° or A-90° are equally proper ways to get to the "front" of your part, the C just has to rotate as well to match. So sometimes, if you use the Mastercam Front plane, it'll cause your post to output A-90° C270° because that's closer than what you expected A90 C90 or whatever.. Look to see if you have Misc Integers that allows you to tell it what angle the toolpath is "starting from" so the post can guess the correct way to output it. I think the generic posts use MI 6? (Colin will be along shortly to correct me...) You may find that you just have to create your own plane by rotating the view the way you want the machine to rotate so the vectors line up, i.e., instead of using the Mastercam Front view, you have to create a new plane and only rotate the Y axis or something.
  6. Aaron Eberhard - CNC Software

    NVME Drive

    That's a "how many trees are in a forest?" kinda question... This comes up a lot because it's a confusing topic, but basically, multithreading will help you when you have either a lot of toolpaths to process at once or when your single toolpath can be broken up into logical pockets to be calculated simultaneously. If you're doing simple parts that primarily consist of one area, you're not going to see much benefit from multithreading. For a really quick and dirty example, using an Opti toolpath to rough this pocket: can't be effectively multithreaded because it's all one "slice," and you can't really figure out what how to cut one area without affecting another, so it all has to be processed as one chunk. In this case, clock speed is king. If the part looked like this: The top slice would be one thread, and all of the individual pockets/depths would be an individual thread. So that would (potentially) benefit from more threads
  7. Aaron Eberhard - CNC Software

    Advanced Drill - Wow. Finally. This is awesome!

    Oh yeah! Thanks for the reminder
  8. Aaron Eberhard - CNC Software

    Advanced Drill - Wow. Finally. This is awesome!

    Yeah, I'm really curious to see the new and exciting ways you guys are going to break this one. This toolpath is really a wide open sandbox once you start to wrap your head around the toys you've been given...
  9. Aaron Eberhard - CNC Software

    Advanced Drill - Wow. Finally. This is awesome!

    Thanks mate! We're probably not going to go that direction per se, because that would be a lot of jumping in and out and weird dependencies and kind of annoying in reality, I think. Look for future enhancements to this toolpath to start leaning more on extracting data from a defined hole...
  10. Aaron Eberhard - CNC Software

    Advanced Drill - Wow. Finally. This is awesome!

    Glad you like it, guys Colin, I think we already have the "switching back to a M3 after a M4" thing in progress, but would you mind send your file in to QC so Jamie can add it to the defect and we can verify that it's fixed as soon as the story is done? Thanks!
  11. Aaron Eberhard - CNC Software

    5 axis Tool paths and Planes?

    No problem, I intermixed the current state of Mastercam with things that directly affected Motor-Vater, since I had originally trained him in Mastercam back in the X4 days, and a lot of what was necessary then doesn't apply anymore... The main gist of the conversation was whether it mattered with a multiaxis toolpath to have all of your planes set to Top/Top/Top (abbreviated as T/T/T), because Motor-Vater was surprised to see that it worked fine to output it as Top/Front/Front or any other combination of Top/Xxx/Xxx. So in Ron's reply and my first line, I was confirming that before the Mastercam X9 release, it was VERY important that you always used the Top WCS with a multiaxis toolpath (the planes didn't really matter for most people except in very explicit situations like I talked about with Motor-Vater in my second paragraph). However, since X9, you've been able to use WCS appropriately with the multiaxis toolpaths. As an example, a lot of people get a part in aircraft-coordinate-system, so when they load the part into Mastercam, it may be many meters away from the the T/T/T 0 point. Previous to X9, you would have problems if you didn't move the part back to T/T/T 0, but after that, you can just create another WCS like you would for 3 axis work and it'll work perfectly fine. My second paragraph was about what's happening in the background when you chance a toolpath from T/T/T to T/F/F behind the scenes and why it specifically applied to what Motor-Vater was doing back in 2009 or so and how it doesn't matter to most people most of the time. The last bit was some general guidance on what you're doing if you set a multiaxis toolpath in a non-Top WCS, like my aircaft-coordinate-system example above. When you choose the new WCS, all of the axis references (X,Yz) inside of a multiaxis toolpath mean "The X of chosen WCS" NOT "The X of Top" like it used to before X9. Does that help?
  12. Aaron Eberhard - CNC Software

    5 axis Tool paths and Planes?

    Yep, as Ron said, starting with X9, all of the multiaxis toolpaths became WCS aware... That was my first release as the Product Owner *sniff* Back when I trained you (X4?), it was REALLLY important to always have a multiaxis toolpath set in the Top WCS. Basically, a plane is more or less irrelevant to a multiaxis toolpath (if you have one curve toolpath that starts on the front and then continues around on the side, what "plane" is that toolpath on?"), but the WCS is really important to us. Changing from T/T/T to T/F/F will only change the way the data is stored in the background NCI (if you care, it goes from saving it as XYZIJK to XZYIKJ). Because of the way you were digitizing on the machine at the time, the that plane inversion would alter the commanded positions of the probe, so on a digitizing Flow 5 Axis toolpath, it was REALLLY important make sure it was in Top/Top/Top before posting. So the important thing to remember nowadays is that whenever you interact with an X,Y,Z in a multiaxis toolpath (Lock to 4 axis and rotate around Y, Limit the XZ plane motion, Fixed Angle to X, Retract Along Z, etc.), all of those X Y Zs are relative to whatever WCS the toolpath is in.
  13. Aaron Eberhard - CNC Software

    No more entity selection for drill in 2020?

    Oh, and you may be tired of me saying this sort of thing, but thank you for having these sorts of discussions! Myself, and everyone over here, really appreciate all of the viewpoints they bring, and we use really do use them to (hopefully!) make life better for our users!
  14. Aaron Eberhard - CNC Software

    No more entity selection for drill in 2020?

    You know my number and email address Ron, I'd never forget you You've got me on those points for 2020, as drag & drop and display list size were my biggest problems with new interface.. I know it's cliche, but give 2021 a test drive. UX has finally given us drag & drop and a much better window size. The systems team has also made some pretty massive solids interactions improvements in the back-end which drastically reduce the solids interaction time, whether processing a toolpath that references solids or launching the hole selection panel, so there will hopefully be a lot less reasons for you to select wireframe at all, and you should notice a nice reduction in overall toolpath generation time as there was some overhead there when interacting with solids. I'm finding a lot of toolpaths that I previously would create surfaces > from solids in order to reduce calculation time don't require that step anymore. Note that this is only really noticeable when dealing with the bigger, complex solids like you guys do... A simple one really won't really yield any difference.
  15. Aaron Eberhard - CNC Software

    No more entity selection for drill in 2020?

    Right, it's a click to limit your selection, but that's the same number of clicks you go through to limit your selection in X9, and this one is at least a standard selection like you'd use otherwhere in the software, not a random box in a dialog that only appears in that situation.. I can understand that it's annoying to change a 20+ year learned behavior, though, that took me a bit to get used to! For me, it was always Launch drill > immediately click "entities." Unless I thought I wanted to maybe use something else in which case, forget that I can click anywhere accidentally choose a random point in space, swear, ESC, ESC, ESC and start over...

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