MCU shutdown: timer too close - after I start a print (quite a heavy file)
Hi, any ideas what is wrong with my printer? Once I have started a big print job, klipper shuts down with this error (photo below). I have done a couple of small prints with no problem, so I assume the gcode file is too heavy (which would be weird in my opinion)
58 Replies
I'm getting the same error now too
Tried with two different pi's
Are you getting this error when trying to print a larger file? Because I am not getting this error if gcode size is up to 250 mb
Other gcode size is 350 mb. That’s when I first got this error
okay this might not be related to gcode size, because I just got an error again with a smaller gcode
Yeah unrelated to size for me
That's really frustrating. @miklschmidt maybe you have some insights?
So you guys can't print anything right now?
@armearme. please post a debug zip
I have managed to start the print once in the last 4-5 attempts. I also sometimes receive an error of "communication lost while homing" and similar.
I just tried to start the same gcode one more time and looks like this time it worked. And I did not have these errors until I have started to test the printer with large parts (250 mb gcode)
Hmm
Can you show me a screenshot (or even better a video) of the live output of this:
After you've started a print ?
In case it's a postprocessor issue, rebooting should help (at least to print smaller files). But it shouldn't run out of memory at this point, it should throw an error saying it can't post process the file instead.
It might not have anything to do with that however. There aren't really any obvious clues in the logs.
idk now I have this:
that's during the bed probing before print starts
And this one after I press "home"'
okay that's getting bad. I just pressed "home" once more after the "communication timeout during homing", printer probed the bed 3 times and then shutted down:
Did you reboot?
Please show me the output of htop.
I didn't understand, do I have to send that code via console after I start the print? or just after rebooting?
Ah, sorry, i'll explain better. It needs to be run through
ssh, so open the command prompt (i'm assuming you're on windows). You can do that by hitting win + r then type in cmd and hit enter
Then you write ssh [email protected]. Replace ratos.local with whatever hostname you've given your machine.
It'll ask you for a password, the default password is raspberry
when you're in, you type htop and press enter
It'll show you a resource monitor, i need a screenshot or a video of that once you've started a print, preferably before or right around the time when you get the error on screen.does not look right. What I am doing wrong?
seems like you've connected via ssh before but have since reinstalled RatOS so it's gotten a new fingerprint
if you write
notepad C:\Users\armin\.ssh\known_hosts notepad should open, delete the line that has vc4.local in it and save it. Then try again.There are 2 lines with vc4.local. Delete both?
Yep delete both
In fact delete everything in that image (word wrapping is on 😄 )
write
yes hit enterI can not type the password 😄 as if keyboard is not working 😄
that's on purpose
so people around you can't see your password
just type it in and hit enter
jesus, I feel like a hacker now.
okay I am in. What now? Numbers keep changing a bit
excellent, then record this while you start a print that causes problems
Also obligatory
😂
you should be able to hear the fan sound after the MCU shutdown
mmm, looks like that htop screen is locked, I can not scroll that window 😄
and not even one number or line has changed
I am no expert, bet previously at least there were some numbers movement 😂
oh wait
there was some kind of bug
I will upload a new video that will show you something. Even I can see that it's overloading
You lost the connection here, that's why the interface isn't updating.
one sec
here you go
Thank you! Swap of death confirmed.
We're working on a new post processor that fixes this. Is this IDEX or non-IDEX?
non idex
hybrid
so that means I can not use the printer until this thing is fixed?
Well, at least not for the big parts printing?
No, it works with smaller files, and we have a workaround coming for non-idex in the meantime. Just a sec.
@armearme. Put this into your printer.cfg:
Then try the file again
It worked. Print started the same moment I pressed "start print" Before, I had to wait 40 seconds until the shutdown.
what is wrong with that tolerances...
PLA is oozing a little bit at 150 C, how do I lower the nozzle temp on the startup of print?
it is all out of whack, it's off by 42.5 microns between each probe.
It should not be oozing at 150 (unless the hotend was left too cool under pressure, heat it up and do a small retract, like 2mm and try again).. It could be a rapido 2 thermistor issue though.
You can change the preheat temp using the
variable_preheat_extruder_temp variable: https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/macros.md#heatingGitHub
RatOS/site/docs/configuration/macros.md at documentation_v2.1 · Hel...
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - HelgeKeck/RatOS
When I get home I'll try the config edit to see if that fixes it for me too- mcu issues as them, just without probe issues.
...do rapido 2's have a known thermistor issue?
Though for clarification, I'm a normal v3.1 running ROS 2.1
Not really, but the wire is fragile and prone to breaking and in some cases people did not have them screwed in all the way
I've replaced mine already but it's erratic at times.
there was a bad batch a good while ago. That coupled with an unfortunate amount of metal on those thermistors exposed to external air streams (such as cold air from the hotend heatsink) made it a bit wonky. Most of that should be remedied now.
No dice for me. Still got a timer too close error
is this a IDEX printer?
Okay I have the first layer done, will see how it goes 😄
That's how it goes now. Does this look okay?
No, regular 3.1
oh yes, it's bored now
Then your problem is unrelated, please open a new thread with the following details:
1. Exactly when does the problem occur, is it reproducable and repeatable?
2. Upload a debug-zip downloaded right after the problem has occured.
Posted!