RRC[

Rat Rig Community [Unofficial]•13mo ago•

38 replies

lingo124

RatOS Post-Processing Introducing Errors in GCode (More like destroying good GCode)

I've recently run into issues with what seems like the RatOS post processor mangling GCode. For background, I sliced a model (actually had errors in a couple other earlier prints of different parts too) in PrusaSlicer 2.9.0 for my VCore4 IDEX with the 400 IDEX machine selected in PrusaSlicer. When I upload it to the printer to print, at some point the printer errors out during the print saying some ridiculous move out of range error: "Move out of range: 1882.736 206.573 4.148 [2567.194]"

That X movement is of course impossible. Knowing I was already running into issues earlier with a model I directly uploaded to RatOS from PrusaSlicer, I had opted to export the GCode from PrusaSlicer first and then uploaded to RatOS using the webUI. It turns out, the RatOS post processing seems to damage the GCode, introducing syntax errors and whatnot (posted the screenshot of some examples). I have no clue how that happens...

I've attached both the pre and post processed files in case anybody is able to discern something... debug zip is also attached in a later comment

I am on: PrusaSlicer 2.9.0, RatOS v2.1.0-RC3-26-g33980992

camHolder_postProcess.gcode3.27MB

camHolder_preProcess.gcode3.25MB