There are two new vCarve post-processors attached here:
Shapeoko_inch_AX.pp: For GRBL-Panel and other more standard gcode senders
Shapeoko_CM_inch.pp: Specifically for use with Carbide Motion and it’s slightly odd tool-change commands.
I had two goals in with creating these. The first was to create gcode that was more readable for a newbie (like me?). I’ve commented the gcode as much as I think is helpful, without being too verbose.
The second goal was to provide some level of “toolchange” functionality. At the moment this takes the form of stopping the spindle, moving back to material setup HOME and waiting for a RESUME from the gcode sender. In GRBL-panel this is hitting the Resume button. You can also send a ~ to resume. In CM you have to hit the “Start” button again.
For now, please test if you can or want, provide as much feedback as you like. I’ve tested, but I’d probably suggest running air-jobs first, just to make sure nothing goofy happens.
Please take the “.zip” extension off the file. It should have a .pp file extension. Copy the file into C:\ProgramData\Vectric\VCarve Desktop\V9.0\PostP and restart vCarve.
Updates:
Shapeoko_Inch_AX updated to include dwell times to allow time for the spindle to come to and down from speed.
bug: Do not include any parenthesis ( or ) in your job names, it will cause grbl errors because of the un-escaped comment characters. I’ll look into fixing this, but for now, just omit those characters.
M6 is used in the CM PP because CM understands what to do with that command. Other g-code senders do not. Read the comments in the standard PP, they’re pretty self-explanatory
I looked at the “generic”, non-CM version. Just want to make sure that people understand that the use of these PPs depends on the Gcode sender that is being used. Before using you have to verify/test that the M00 and/or the M06 is being interpreted.
Do not include any parenthesis ( or ) in your job names, it will cause grbl errors because of the un-escaped comment characters. I’ll look into fixing this, but for now, just omit those characters.
Hi. I had some difficulty with PhotoVCarve using these post processors. I was rejecting the part of the code dealing with sections. I ended up having to comment it out. I haven’t done anything very intricate but so far everything has worked well since then.
Thank you for providing these. For some strange reason the generic code quit working with my Shapeoko. Everything was coming out very tiny!
@karen, thanks for mentioning this. I had the same issue recently with PhotoVCarve, which I purchased months ago when I got VCarve Desktop, but hadn’t tried to use yet. Same thing, whatever I tried came out very tiny when using the Grbl post processor, and this one worked for the metric but not inch post processor.
Hm… sorry to hear it’s giving you trouble! the Photo vCarve PP must be different in syntax… if somebody can upload one of the stock ones, I can look into working up a new one.
