A little more............I tried to run the file from GRBLMachine but couldn't get past immediate tool change errors. However, on the way, I did elect to overwrite my stored Gcode file with the new version from GRBLMachine. When I opened that GRBLMachine generated Gcode file in UGS, it ran, whereas the CamBam GRBL post generated files would not.....ending with error 33, so I may need to try a couple files to confirm it was just the tool width/guide lsot or whether the post processors also played a role......so fare I haven't gotten anything generated with the cb GRBL to run without ending immediate or early in error 33
So, I thought I'd try to generate a GRBLMachine GCode file for the other part that I have that partially runs but eventually throws error 33 but although GRBLMachine will connect, I can't get my machine to accept commands from GRBLMachine. We'll see what tomorrow brings on that but also, not sure why the GRBLMachine files immediately error on the tool change. I switched tool change to
ignore, but since GRBLMachine won't communicate with the controller, couldn't test that.
My first though would to be check if the arc's are causing the problem, go to your PP and set your arc output to lines. If this eliminates your errors then the arc's are the culprit and you can then change the Arc output back to arc's and change the variable $12 arc tolerance.
I still need to try this from one of my cb generated gcode files to see if it will run from UGS.
There is a picture of my test controller GRBL config which runs the posted code as is with no errors.
I saved the config from the successful run for future comparisons.
Not sure if it means anything but the machine controller is loaded with GRBL 1.1i for the MillRight MegaV.....
Sucks when you don't know what you're doing...
Best,
Kelly