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:

#Rekd™

Customers
  • Posts

    2,931
  • Joined

  • Last visited

  • Days Won

    48

Posts posted by #Rekd™

  1. Your file shows each toolpath with 1 solid chain selected, this looks correct.

    Work on using Levels to separate your geometry. Move your solid body to a new level and name that level "Solid Model". Then move all your surfaces to a new level and name it "Surfaces". Then if you need any wire frame geometry put that on another level and name it "Wire frame Geometry". This way you can turn on and off the other levels making your geometry chain selection easier. 

  2. Create a standard for levels such as doing them in intervals of 10. Possibly having fixtures on a dedicated level in all files if possible. Have a dedicated level for Notes on the part/ job and programming so anyone that opens the file can view these. 

    Implement the use of View Sheets to easily pick views and or levels.

    If there isn’t anything currently in use create a logical file storage structure system for storing and accessing files. Try to have all files for each part or job contained in the same folder whenever possible. Have a revision naming policy so everyone follows the same process.

    Develop a verification process that everyone will follow when G-Code is created. 

    Insist on having comments added in every tool path. 
     

    I have HSM Advisor for speeds and feeds. We use a lot of Helical Solutions/ Harvey tools, their machining advisor is excellent. 
     

     

     

     

     

    • Like 4
  3. 9 minutes ago, cnc nemo said:

    You say everything correctly, but I don't have a machine and I don't have the task to go through all the stages, I would like to start by understanding the creation of a machine with similar kinematics in Mastercam, so that at least everything works correctly in Mastercam, if I haven't figured out at this stage where I'm going to the postprocessor to the machine, but I want to figure it out while it doesn't work out on my own, so I'm turning to the community / colleagues, I hope they will respond here or on other forums...

    Without a valid Ziptogo file no one will touch this since it reeks of piracy IMHO.

     

  4. On 7/12/2023 at 12:40 PM, cnc nemo said:

    how it should be implemented in Mastercam

    The Machsim is more or less just bling unless you have a kinematic aware post processor from Postability or In-House Solutions. Then you have to license the Module Works module for the full Machsim.

    Having a tested Post Processor, a matching Machine Definition and Control Definition (these are not part of your Machsim file) are the first steps in Mastercam. The post processor translates the NCI file that Mastercam creates in the background into G-Code for the specific Machine/ Control. The Machsim that you can build and or comes with Mastercam is only verifying the NCI code not the actual G-Code that the machine will interpret. This is why there is a need for verification software such as Vericut or Camplete.

    I can show you files that verify fine in Mastercam and on a Machsim but in Vericut it shows the collision as it is verifying the actual G-Code.

    • Like 1

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