G Code Support

GCode

In the early days of CNC, G-Code programs were written by hand. As a result, the G-Code language was extended with all kinds of commands which are to make writing the G Code simple, putting the complexity in the CNC-controller for executing that code.

Today, G-Code is often 'generated' in a CAD/CAM application. Those CAM post-processors take care of the complexity and then generate G-Code that's rather simple itself, by using more of the simple G-Code words rather than more compact (but more complex) G-Code.

Moovr focuses on G-Code from the CAD/CAM scenario.

Control

On top of supporting G-Code, there are other important things a CNC controller should do. Again we'd like to keep it simple and so we provide:

• homing : indispensable procedure to get your CNC in a precise, well known state.
• jogging : manual moving of the machine, eg. before you set your (XY-axis) Work Coordinates.
• probing : procedure to set your Z-axis Work Coordinates and make (manual) tool changes simpler.
• overrides : manually adjust some of the settings in your G-Code, as you see fit, during the execution of the program.