Ideally I'd like to see roughing moves such as the 2D & 3D adaptive machining implement G64 per operation and take the motion blending tolerance from the specified tolerance in the operation. no maximum deviation from programmed path), so we can end up with smooth but inaccurate parts unless the preamble is manually entered to the file or the machine defaults have something else specified (which may be inappropriate for the part to be machined). The default for LinuxCNC in the absence of either of these commands is to use G64 with no tolerance (i.e.
#Hsmworks post processor code#
I've been looking at the code generated by post processor supplied for LinuxCNC and I realised that it is not applying any settings for G61 (exact path mode) or G64 (path blending) either in the code preamble or per operation.
The other option would be to have about a dozen generic Post processors covering basic DIGITS (resolution), INC or ABS, and Axes Names (XYZ, XAZ etc)
#Hsmworks post processor software#
6 digits, X, A - G1 X3.973433 A0.898672) I think it would be easy to develop a software that gave you these 3 basic selections, DIGITS (resolution), INC/ABS and AXES NAMES and spit out a post processor for Fusion 360 that would produce the proper NC code for us people who actually program our machine programs. G1 X3.232454 Y 5.234362) - (for Aerotech users) 5) if the digits and axes could be selected that would be a bonus also (e.g. In my opinion some basic post processors should be developed and be available to everyone who just needs the NC code 1) 4 digit INCREMENTAL (e.g. The one thing we can't find with Fusion 360 is GENERIC POST PROCESSORS to spit out BASIC NC CODE. 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.
#Hsmworks post processor manual#
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)
