MCU 'Toolboard t0' shutdown: Timer too close.
This error happened often on my v-core 4 500 IDEX, at first i thought it was my ssd, then the underpowered pi, so i switched the ssd and have given it a direct power supply.
it's been more than a month, i don't know what to do anymore, please help me...
Solution:Jump to solution
i switched the usb to a new one and the problem didn't come back, probably the usb had gotten damaged somehow... I had one of the rat-rig provided ones with the nylon coating.
54 Replies
my only guess is that it could be the ram, since it has only 700MB for normal operations of which it looks like 50% is used at idle
probably the two cameras are part of this problem
2025-01-21 00:27:06,679 [update_manager.py:_handle_auto_refresh()] - Klippy is printing, auto refresh aborted
2025-01-21 01:27:06,679 [update_manager.py:_handle_auto_refresh()] - Klippy is printing, auto refresh aborted
2025-01-21 02:03:13,637 [klippy_connection.py:_process_status_update()] - Klippy has shutdown
2025-01-21 02:03:13,643 [websockets.py:on_close()] - Websocket Closed: ID: 4085405728 Close Code: 1000, Close Reason: None, Pong Time Elapsed: 5.21
2025-01-21 02:03:13,644 [proc_stats.py:_handle_shutdown()] -
i see this, howether it looked like the actual shutdown came at 3:03 maybe it has the wrong time set
Klipper Version: v0.12.0-396-gb7233d119-dirty i also see this over that few messages
thank you in advance for all the help you will provide
what did i forget?
To read 😛
the files asked in rules
Oh, sh*t… just saw them… sorry :/
Will take a look later today
thank you 🙂
btw the error comes something like a at least 12 hours into the print, sometimes after two days
if you have a better sd card to suggest, i'm happy to hear, in the meantime I've ordered a raspberry 4B 8GB
Have you considered it may be overheating? Add active cooling on the pi?
now I got this error while printing the same gcode but only after 3 hours of printing
raspberry was 45 deg before error, it has some passive solutions and the air blowed by the fan in the cabin onto the drivers should also be getting to it
@ctbjdm_04135
after first time i hit firmware restart it gives this error, but then it resets fine:
i don't know why but i think this may be important
I had that error when the power feed to the toolboard was loose (umbilical feeding power to the ebb42). Check the pins, make sure they are solid and the connector is good. My connector was loose, ended up adding a drop of CA glue and that solved it.
can you highlight the part you refer to? @ctbjdm_04135
please
i've tried dragging the black and red cables but i can't recreate in any way the error, so i'm not sure that's the source of the problem. What do you think abot this?
Yeah I was referring to the molex connector, black and red wires
I’ve had this issue at the start, i had forgotten to crimp them… but now they seem fine
@MDFPereira not trying to rush you but if you could possibly give me a feedback in the next 3 hours it would be perfect for me, since later I’ll not be able to be close to the printer
Timer too close is a generic klipper error. Basicaly, not even klipper knows what is going on.
The disconnect can be more than 1 thing.
Bad cable strain causes either the USB and/or the power lines to loose connection.
Too much temp on the toolboard mcu.
Looks like you checked the power (24v) lines and nothing happened.
Try having the USB plug with good relief on the toolboard mount. The usb plug in the toolboard has kinda weak solder points. Any movement can cause it do loose connection.
Also, check the toolboars temp when this is happening
What are you printing and at what temps? Enclosed or open?
I’m printing open, 90* bed 245* hot end
Never had issues with t1, once while i was printing with t1, it was still t0 loosing connection, and once the beacon. However that was before correcting the undervoltages
I can try changing the passive cooling solution on the EBB42
I’ve had some problems with that heatsink at the start
I will check klippy.log later for the temps.
If any of the mcu passes the config max temp, they disconnect.
I’ve also tried shaking the usb-c that also didn’t re create the problem
I’ll try changing the cable
Should not be the cable.
The stock cable is quite good
However temps don’t seem to be too high while printing, it’s 50 deg at the start of the print, but at the start the fan is off and the plate is quite hot
The plate is what is passing heat to any toolboard or beacon… Even with the fans on, the fan air flux does not go near the toolboard
I,ve printed at way higher temps (PPS-CR). But nothing that long. 3 or 4 hours max
Like 310/120
I’ll try printing on a 70 buildplate for now
No need.
Just keep an eye and open a door for 10/20 seconds every hour. Just to circulate the air
@MDFPereira did you have a chance to take a look?
rn I’m printing with t1, didn’t get any errors yet, but I would like to try to understand what’s the reason behind these errors…
Checking it now.
How many points do you have the bed mesh set to?
I can't see any error other than some error on klippy scripts...
try ssh and runing just
ratos doctor
your klipper instance should be restored and no longer show dirty.
did you install anything else onto the rpi? maybe any external script for anything?
the only thing i have is octoeverywhere
it's a 500 and i have it set to the default
i'll try when the print finishes, rn the printer has managed to go without errors for more than a day, probably because i'm using t1, i'll still switch the cables just to be sure
may be it's gone bad because of something
Should not mess klipper installation…
Try ratos doctor
before i had a hybrid, may be i damaged something in the switch to idex
i'll do it in about an hour, when the print is finished, thank you very much for your help
✓ Fixing potential RatOS issues...
✓ Repaired RatOS configurator
✓ Restarted RatOS configurator
✓ Repaired RatOS configuration
✓ Restarted Klipper
✓ Restarted Moonraker
Done!
Running: $ sudo systemctl restart moonraker
done, is this what i should have expected as an output?
Yes
Refresh updates and check if klipper is no longer dirty
where do i check if the version is dirty easily?
Refresh updates and check the klipper version. If it is dirty it will say dirty at the end
ok, in the update manager it's fine, i thought it was dirty just in the EBB42, since it's the only one causing problems...
not sure about how klipper works in detail, i thought every board had an independent installation
What could be dirty is the klipper installation on the raspberry.
What is in any board or toolboard is the compiled firmware. When not compiled correctly, it will not connect.
But RatOS compiles it for you with the correct settings
Basicaly, boards or toolboards act as an interface. The Raspberry deals with everything.
oh ok, now i get it, it should be fine now in that sense. however this is strange i've reinstalled twice the firmware... may be the bad installation came from underpowerage
now i've given the raspberry an independent power source, in that sense it should be fine.
Will see 😉
thank you very much in the meantime
same thing again unfortunately. after having done successfuly two or three full day prints with t1 decided to try again with t0 to see if what we did fixed the problem... unfortunately it didn't
what should i do next? i'm thinking about replacing cable and then if that doesn't solve the problem the ebb42... do you agree or should i try something different?
I would bet on the USB plug solder joints on the EBB…
You can try with the new cable too but I kinda doubt it is the cable
i have a spare board, but i'll have to unsolder the endstop cables... unfortunate, i hope this at least solves my problem
Unsolder? Why? No dupont connectors?
on the endstop they kept slipping out, I had to push them in to make a contact, couldn't make a proper crimp, so i decided to ask my electrician to solder and insulate...
now that i think about it i should check that with certain movements of that soldered cables the board doesn't get shorted...
just checked on the printer and the soldered board is t1, so i'll just switch out everything, cable and board. I just have to flash the new one in the configurator right?
Yes, it needs to be flashed.
And both are soldered. Maybe t0 has any issue…
yeah i meant soldered connections done by me
And I mean the solder on the usb plug. They are weak
Solution
i switched the usb to a new one and the problem didn't come back, probably the usb had gotten damaged somehow... I had one of the rat-rig provided ones with the nylon coating.
this seems to have solved the issue
same problem occoured again.... probably shouldn't have spoken that soon. It occured while printing a bridge so it should have had any vibrations... I highly doubt at this point it has anytng to do with the actual mobo on the toolhead
i notice the raspberry has a question mark at the start of its version, not sure if that's normal...
do you still think i should swap ebb42 or could it be that the raspberry has too little ram?
However the fact that t1 doesn’t have any problems leads back to the Ebb42….
Got timer too close on t0 while printing with t1…. This was the first time