To make it show up in webcontrol the optimized gcode needs one extra step.
open optimized gcode in notepad++ and replace all the lowercase commands to Uppercase.
g to G, f to F, x to X, y to Y, z to Z.
resave.
This new resaved .nc file will graphically show up in WebControl.
I have successfully cut multiple designs with separate roughing and detail nc files using this method. No issues thus far. Just make sure that you donāt mess up the command replacement⦠in other words do not mistakenly replace x with Y. Unable to really give details on how much time it saves since Easel wont let me re-import the new files (lame). But the travel paths look way more efficient. + when the cut is done it just stops at its last point and will not return home. For what I do⦠that is never necessary.
your site takes too long to respond and no page loads. With 4 different posts today, 3 of which are word for word identical, one may question if you are spamming a bitā¦
nope! just wasnāt sure which site or subject to put the matter under. so I put it under a few. did not suspect that it would garner much attention anyway. Not selling anything⦠so donāt see how this is spam⦠but sorry it bugged you. BTY its not my page⦠that is slow and buggy. many user just mentioned they had tried the script stating they could not figure out why it didnāt work with webcontrol. well I figured it out and was Just trying to help out.
no worries. The inquiry wasnāt intended to be offensive, just asking questions. I was just curious about the number of posts and I asked by posting rather than just flagging it and you responded. Please excuse my lack of manners.
I tested a code fix for the lower case to upper case gcode upload a while back (~6 months?), so it should fix that, but a new version of webcontrol has not been released with that incorporated, so nobody else has the fix. We found it some time earlier this year I think. Great job finding it. It was a weird bug.
Iirc this gcode optimizer does a tsp optimization of travel moves, but no other changes. It could be interesting to combine this step with md8nās gcodeclean since many CAM programs are pretty brain dead about unnecessarily zipping back and forth during jobs
Cool. The script will also need to take into account the final path to the home position. After 3 different projects were loaded (after optimization) and successfully cut, not a single one retained the final trip to the home position. I guess cutting out that last move is part of the optimization.