-
Notifications
You must be signed in to change notification settings - Fork 55
Home
Strooom edited this page Aug 22, 2016
·
8 revisions
The built-in 'GRBL Generic' post-processor that comes with Autodesk Fusion360 has a number of problems. Looking into the code (these post-processors are written in JavaScript) I realised it was more a quick & dirty hack.. After finding a nice Class Reference I decided to give it a try and write a better GRBL Post Processor
- Functional restrictions of GRBL - currently version V0.9j
- 1.1 only 3 axis - so don't bother with 5-axis functions
- 1.2 no automatic tool change - no need to send tool-change commands
- 1.3 no radius compensation
- 1.4 see: https://camforum.autodesk.com/index.php?topic=7571
- 1.5 https://github.com/vlachoudis/bCNC/issues/88#issuecomment-129568125
- Based upon my specific machine configuration 2.1 set machine to mm, inches are not supported 2.2 spindle only clockwise (M3)
- Based upon making things simpler and thus more solid 3.1 don't try to save a few characters on blocks that only appear once per section - do a proper initialisation at each section start 3.2 always send comments. They will be ignored by GRBL, only appear at file/section begin and make the GCODE more readible 3.3 don't use linenumbers : GRBL doesn't use them, and when editing each editor has them anyway, so why have them in the GCODE... 3.4 don't remove spaces... UGCS can do this for you before sending it to GRBL
- Additional test which can make the GCODE more robust : 4.1 check if radiuscompensation is ever used.. should always be done in the CAD/CAM computer.. 4.2 check if units are mm 4.3 check if multiple tools are being used 4.4 check the state of the machine after job has finished - could conflict with manual jogging..