When I wrote it, the generated G-Code starts with (specification correct) “%” line. If there is trouble using the post processor, let me know and I’ll get rid of it and have @WillAdams update the post processor.
The post processor supports automatic tool length changes, something that the Nomad can do easily but most SO3 are not equipped for.
If someone has a Shapeoko set up for automatic tool length changes they did it themselves and they know, and they need to share / document how they set it up.
Those SO3s that are equipped for automatic tool length changes may be identified by?
@WillAdams is the SO3 expert. Correct me if I’m wrong but as I understand it one would know they such automatic tool length change support because C3D doesn’t sell it; they had to add it themselves.
I’m not sure that the SO3 can support it or support it easily. Will?
First off, I ain’t no expert — if I were, I wouldn’t need to crib from all the personal notes which are essentially what the Shapeoko wiki is.
FWIW, I started on modifying my Shapeoko 1 to have a tool length sensor — in theory it’s simple, just a homing switch embedded in the machine wasteboard — all you need to know is its position in absolute machine coordinates and one can then reliably send the machine to it to measure after a tool change — software support is built into Carbide Motion and Grbl (see any video of the Nomad doing a tool change).
One of these days I’ll get the basement tidied up enough that I can get the SO1 and a bunch of other abandoned projects re-started.
I’m trying this postprocessor with my S3 and when I try to run it, Carbide Motion doesn’t recognize it as a file. I’ve opened the file after postprocessing and it appears all the information is there. Is there a tag or command that is needed for it to be recognized?