Chally72

Verified Members
  • Content count

    53
  • Joined

  • Last visited

Community Reputation

31 Excellent

About Chally72

  • Rank
    Member

Recent Profile Visitors

386 profile views
  1. Chally72

    Stock model work planes

    The processing time being extraordinarily long is a good clue that your planes are probably not correct in your stock model operation. The stock is likely sitting right where the tool/holder pass through, and that starts to cause major stock calculation headaches when it results in things like driving the holder through the entirety of the stock body at odd angles. No need to let it run all weekend, especially if you know that a similar stock model generated in 2 minutes- stop the processing and then take a look to see what's wrong with your planes. A good sanity check is to create the stock model with your plane setup, but without applying any Source Operations to make sure that it's starting in the position and orientation you actually want. Then you can go back in and add Source Operations back in- maybe even one by one, allowing you to diagnose if a particular operation is causing a stock model calculation hang. It would be helpful if you could post a file that shows how you're setting up your ops and stock- even if it's on a simple sample rectangle- so that we can provide you specific feedback on what you're doing.
  2. I believe Terrance's issue is that he has machines that have perhaps been migrated, and the files physically exist in the folder, but do not show up in the machine list inside of Mastercam when he goes to Manage List to add them to the machine dropdown menu. I've seen this happen occasionally when users manually copy/paste the machine folder structure from an older version, and also if there was a hiccup in migration.
  3. This usually occurs when the files are manually copied, for example, from /Shared Mcam2019/ into /Shared Mastercam 2020/ instead of migrated using the migration wizard. When you see this problem, have you tried doing an advanced migration and specifying these two folders as source and destination?
  4. Chally72

    mmd & control files

    The possible axis combinations in Machine Definition manager are based off of what machine components you have set up, and how you have set them up, in the Machine Component manager- which you get by double clicking on any component in the machine configuration 'tree'. Jim, you can get in touch with me by clicking on my username and then clicking "Message" on the next screen, or by emailing me at dylan.gondyke@mastercam.com
  5. Chally72

    why does raster rise and fall next to walls?

    It is climbing to avoid contact with the wall avoidance surfaces when the toolpath puts it right against the wall surfaces and it thinks the tool is interfering, be it actual interference based on stock to leave or even a loose tolerancing issue or unseen sliver areas/non-perfect surfaces in the avoid selection.
  6. Chally72

    mmd & control files

    The migration process to 2020 rebuilds the axis combinations available for machine def. In some cases, this will turn off invalid combinations and will require you to create a valid axis combination. Make sure that your axis Machine Coordinate dropdown is not set to Macro for axes used in your axis combos: It is important that machine defs are cleaned up and fixed going forward, as the settings here are driving more and more things. If you're having issues with a machine def, feel free to message me and we can take a look at what's going on.
  7. Chally72

    need to post drill cycle that starts slowly

    Hey Dan, You don't change speeds and feeds when you first initialize the point toolpath. You first choose your point(s) and create the path, then you can go into Parameters or Geometry to change speeds/feeds or point geometry. For drilling a single hole with a slow entry and then a feed change, I would end up with two point operations in the toolpath manager. One drives the drill from my initial clearance point to the end of the entry move, at my slow feedrate, and the second drives the drill from the end of the entry move to the full depth of the hole, at normal feedrate.
  8. Chally72

    need to post drill cycle that starts slowly

    Once the initial points are picked and the toolpath is created, dive back into the parameters and you have quite a few more options to play with:
  9. Chally72

    need to post drill cycle that starts slowly

    Without making a custom drill cycle, which your reseller should be able to help you with, you can also do a point toolpath and use some wireframe entities to drive the drill around and change the speed/feed at specified depths. This is what I use when I need a hole or two with an entry feed that kicks up when I hit full diameter engagement.
  10. Chally72

    Change Log

    For ISO, what is most commonly done for CNC/CMM programs is to do rev control/change logs of the posted code, and NOT the actual file- as Tinger mentioned above. A good ISO implementation of change control will shift the records requirements downstream to the simpler file to manage, and keep you from expending enormous amounts of effort for no reason. Remember, YOU write your ISO document control standards, so take some time to write them sensibly or they'll end up being a pile of rope long enough to hang yourself several times over.
  11. Chally72

    Dynamic OptiRough

    When you use minimum vertical retract, are you checking the Output Feed Move box? If not, you're likely running into dogleg collisions on your G0 moves, which of course vary machine to machine. Ocean Lacky, could you post the file or send to me if you'd prefer not to post it here? I'd like to take a look at the path. If the problem does lie at the control, you're on the right track tuning the Min/Max arc filter settings.
  12. Chally72

    Machine Simulation false collisions

    Just some updated information after looking at the part file in question here- The Collision Tolerance in Machine Simulation (under Info on the menu when a Machine Simulation window is open) is a calculation based on, in part, the Simulation Tolerance in the Machine Simulation settings page. Because the very small scribe tool radius on the etching ops of this part forces that Machine Simulation tolerance to a very small value, and that applies to all operations being actively simulated, we now see all these false collisions for the previous ops. There is no current way to maintain two different tolerance sets for operations being simulated in a single instance of Machine Simulation, and thus the workaround would be to simulate your etching ops separately from the rest of the ops on this part. Also, The Linear interpolate choice will also remove this tool holder orientation swap from the operation transition move in Simulation. In the future, all three options will keep the tool from starting the first point of a subsequent op in the wrong orientation in Simulation.
  13. Chally72

    Machine Simulation false collisions

    You're likely seeing crashes during the rapid moves that link operations, and what Radical1 mentions is the way to remove these 'false positives'. Be aware though, that now you may have a clean Machine Sim that actually does crash or clip a corner at the machine. The control definition setting "Each axis moves at maximum feed rate independently" is basically showing the dogleg motion that will occur in real life during a G0 move. This will depend on the machine and the acceleration of each axis of the machine. Usually, G0 moves between operations are at a clearance height that is above all part and fixturing features, but if you're down in between things, you have the chance of collision because of this dogleg. Note the Linking Parameters page of a Dynamic Optirough path. When you set the retract strategy to Minimum Vertical Retract, you have the opportunity to convert all rapid G0 motion to G1 motion with a designated feed speed. This is to avoid dogleg crashes that now become much more of a possibility while keeping the tool so close to the part- now all our motion will be linear interpolated at the feedrate specified.
  14. Chally72

    Tool Manager crashes in 2018

    Hi Juyong, If you only have Intel integrated graphics, you could try different driver versions and see if you find one that works. Mastercam is not supported on integrated graphics cards, however.
  15. Chally72

    Mill Face Problem

    The issue here is depth cuts are turned on, with depth set to zero. Turn depth cuts off and you should see it generate/backplot/post OK. This has been addressed for 2020. Edit: They aren't set to zero in your path, but the gist is that yes, depth cuts are causing the issue here, and you're not doing anything wrong. Setting Top of Stock to something other than absolute/incremental zero will also allow the toolpath to generate correctly WITH depth cuts.

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