We can easily pull up an old program and throw the new NC code in it in a matter of minutes and be off and running. Us custom users don't need the M codes or extra junk that goes along with a specific post processor. The number of digits of resolution should also be able to be selected. Well there are hundreds of thousands of systems out there that are custom made and also many applications where a user may just need to generate NC code from a drawing, either in INCREMENTAL or ABSOLUTE output. Everything is based on some machine someone is using. I am just shaking my head that there are no basic post processors for generating NC code. I think it would be a great idea if Autodesk implemented this as a standard for their generic posts From my understanding this will require a bit of work by Autodesk on their generic posts.
The stop gets posted before the code has told the machine to go home, ideally we want the machine to finish its operation completely and then stop. The Tailstock M21 is just one of a few custom actions I have made however the issue still applies to all other actions, stops, comments that are built into hsmworks/post processor.
This has happened on all versions of HSMWorks and all versions of post processors. I then have to manually re-arrange the post code and line numbering using hsm editor every time. However when posted out, the manual nc gets posted within the operation just before the last few lines of code in that operation. When adding manual nc like a comment, action or a stop in HSMWorks, I place the manual nc where I would like it either before or after a certain operation.
0 kommentar(er)
