I have made a g-code checker to scan for common errors or possible/likely mistakes. Although it’s a web page, it operates entirely client-side.
This is an alpha version and I am looking for feedback on things that could be helpful to improve.
Eventually I want to extend it with post-processing capability where it can modify and “download” a version with optional adjustments made:
- Split long movements into multiple smaller movements so the GUI and LCD have less lag
- Collapse multiple tiny movements that are collinear (within some tolerance) into single larger movements to reduce stuttering
- Inject fake tiny extrusion movements so that Octoprint will render the toolpath
Any thoughts, however minor, I’m happy to hear.