Hello!
I Recently saw a thread recommending to use the Carbide Create âShapeOkoâ PostProcessor compared to âGRBLâ PostProcessor.
So, for my next project i decided to test that out, even if this job did not require a Tool Change or Pause.
Note: I do have the Limit Switches on my Longmill 30x12
@webbit_NJ , I wonât download your files because the visible link and the actual link are different, and the actual link is a shortened version of the link and obscures the actual location linked to.
@webbit_NJ - The program is stopping on the first M6 command which is at the front of the file most likely. You only need to hit resume to continue running. Or you can go into settings and select tool change. Then you can set it to Pause, Ignore or add code that you may want to run when it finds the M6. Easy peasy.
Indeed⊠The Settings for ToolChange was âCodeâ, and the GCode in both fields were a remnant of some bad experimentation.
I cleared the âBad ToolChangeâ GCode and all is good.
My Fault, but it would have been nice if GSender would have specified that the Gcode Error was not on the JOB GCode file, but the âToolChange Codeâ.
I will experiment the CC âShapeOkoâ PostProcessed feature again on next projectâŠ
If I use pause for how to handle tool changes in gSender there is no error. If I do not put a pause command in the second block, there are no errors. Even if the only command in the second code block is a pause command the error occurs.
Hello!
I was not able able to reproduce!!!
I tested an thought i did reproduce, but then i figured out i had typed âMO=O the letterâ (not M0 = MZero)
SorryâŠ
These types of inconsistent issues could be caused by communication issues or problems with the way commands are intercepted/buffered. @SLabuta What happens if you put a G4P0.1 on the line before and after the M0? (Sorry, no time to test now)
OK, this is just getting weirder⊠If I add the G4P0.1 command to wait for a tenth of a second after the M0 pause command, I do not get any errors. BUT, it skips one corner of the square that is getting cut in the gcode right after the tool change. See the gcode I attached earlier. Just the initial corner is missed. Like a part of the gcode got skipped over. I tried increasing the wait command up to a second and it was still occurring. Still, no issues are seen if the M0 command is not included at all in the last code block.
I will have to test tomorrow.
I once had a skip problem when I paused manually in a job (donât remember if it was via GSender or push button on longboard) it âforgotâ to go up (skipping a z move) and the endmill passed through the material. Nothing broke, but I was surprised.
Sounds like the Pre and Post âHooksâ might not be ready for prime time. @SLabuta, you have a BitSetter? The macros work without issue. Leave the code blocks blank and just run macros.
Any confirmation if this is still happening as of 1.0.2? I am unable to recreate it with M0 in either pre- or post- hooks. We made some changes in 1.0.1 to address it.
