[VC3.1-400][ratos 2.1.0-RC2] Do I have to restart from scratch?
Yesterday I put the 2.1.0-RC2 ratos installer on my Pi and followed the setup instructions. I successfully got the Pi to connect to my WiFi network. Next, the Pi successfully detected my Octopus and flashed the firmware onto it. After that the webclient asked me to choose my Extruder, Thermistor, Fan, etc. which I did.
So I believe I am now at the step where I go to the Update Manager and update the RatOS package. But there is no RatOS entry in my Update Manager.
As you can probably tell I am not really a software guy and this is my first time working with a Pi. At this point is it safe for me to connect all my steppers, fans, etc. to my Octopus? How do I know if I have made any mistakes so far?...
Ellis pressure advance tool won't print
I'm trying to do PA tuning with a new filament, and the generated gcode from Ellis' tool results in a "print aborted".
VAOC won't connect
The camera wont connect maby because I did not wire it correct but I check evertying, and it connecten good.
so dis meant somthing els is up can somebody help me please?...
RatOs invalide
Hi!
I’m triying since the morning to install RatOs as explain on the website but I m not able to update RatOs or RatOs configurator. On the picture you can see that the both are invalid… soft or hard recovery have no effect...
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...
