After working with a Chinese-origin 6090 CNC router with a USB-based Mach3 controller for the last 10 years or so I have made the decision to move on. This move was triggered by a number of problems developing with the controller (including loss of PWM signal to control spindle/laser). The decision was then to provide a full heart and lung transplant, replacing all the electronics and the spindle, and keeping only the frame, the drive mechanisms, stepper motors and limit switches.
While I could have gone for a new Mach3/4 based system I made the decision to go for a GRBL based controller. While the GRBL systems provide some limitations on machining options, I made the decision that I could mostly work around these limitations. The basic GRBL controllers are open source but do have some limitations. I went for one of the more developed (commercial) options that provides for a 4th axis, hand-held MPG controller, WiFi access and integrated Laser support. The model chosen was the Nighthawk from CNC3D.com.au. This controller comes with a companion controller package for a Windows PC: CNC3D Commander.
With the decision made, I turned my attention to better understand the GRBL postprocessor as provided with the CamBam release, and also learning more about how the CamBam Postprocessor system actually works. I have learnt a lot in this process. The first task focussed on was the drill MOPs, especially the peck-drill options that I often used with Mach3. These canned cycles (G81, G82 & G83) are not supported by GRBL. The provided GRBL postprocessor replaces G81 and G82 with simple G-Code equivalents (no pecking), but pecking requires an iterative process. To resolve this limitation, I am in the process of:
• Modifying the base GRBL postprocessor.
• Developing a post-build executable that will add-to, or modify, the NC file to achieve the required GRBL compatible G-Code.
I have this basic package working for my immediate needs, but I can see that there may be other GRBL users that have identified other needs, or issues, that could be imbeded into a GRBL postprocessor for CamBam. To get started, therefore, I am releasing my first version (below) for comments and feedback. I am prepared to look at any suggestions that could improve either the postprocessor or the post-build executable. I am sure I have missed some useful options that might be included and/or GRBL issues that need to be addressed when producing G-Code from CamBam.
Thanks
Geoff