Frankenstein Upgrade of a CR10 keeps going to PAUSE
Hey! I upgraded my old CR10 that, since I got my VCore3.1 500, just sits there and collects dust. I got an direct extruder, an Octopus V1.1 and a BLTouch - I am running the board with the original 12V powersupply. No filament runout sensor yet.
I installed the latest RatOS on the RPi 3 that used to be the home to Octoprint. Sensorless homing works, PIDs are optimized, bed is level and so on...
If I start a new print the printer goes through the START_PRINT macro (I used the v_minion templates and then modified what I needed from there) - and then it starts printing for maybe 2 seconds and then goes to PAUSE - the console shows no hint for the reason. THe CPU of the Pi is at about 20% load - memory at around 50% , all temperatures are super stable - Octopus at 40°C, Pi at 56°C
If I continue the print it takes just a few seconds of printing before the printer pauses again.
Is there any way I can narrow down the possible causes for this - or does anyone have an idea what could be going on?
All help is appreciated!
BJ
8 Replies
Printer.cfg?
Voilà
@blacksmithforlife 🇺🇸 in the meantime I did quite a number of tests and optimized whatever I could. I am not too happy with the bed mesh results - pretty sure this can not lead to frequent pausing - right?
what slicer are you using?
Using OrcaSlicer as I do for my vcore 500
Not sure if OrcaSlicer has this, but if it does it should be checked
and then for your custom start gcode use https://os.ratrig.com/docs/slicers#orcaslicer
what happens if you have other start gcode is that imports all of that before hand and it causes pauses. I would get like 10-15 second pause after prime line before printing
I did not find this check box in orca but I saw something funny during the last test print: the ratrig dashboard keeps showing all kind of different current layers during the 1st layer.
So I removed all the g code except the print start macro - and now it works! Thanks for putting me on the right track!