Help! lost communication with MCU & other errors
So everything started while trying to do a
BEACON_CREATE_SCAN_COMPENSATION_MESH because I was getting sometimes an error where it says the beacon isn't getting any measure. If i try to restart firmware nothing happens. Every time I try to do a home just after I turn on the printer, I get the MCU 'mcu' shutdown: Timer too close message:
9:24
MCU 'mcu' shutdown: Timer too close
9:24
MCU 'mcu' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
Now I was trying to home and I got the following message, and now I can't even restart my printer:
Lost communication with MCU 'mcu'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
I attach the klippy.log.
What should I do? I checked the beacon because it seems it was failing (I was getting a sample exceeds the tolerance error after some measures like when you do the BEACON_CREATE_SCAN_COMPENSATION_MESH). Checked the gantry, also the beacon connection (the cable looks fine). I have been trying to setup my printer for several weeks, please, help me!19 Replies
Timer too close means the pi is trying to do too much, and lost communication is usually a flaky or loose USB. Double check all your power wiring and USB cabling, and unplug anything not strictly necessary from the pi like webcams
I'll double check everything. I don't have anything extra like webcams, just the plain IDEX system and the HEPA filter
What Pi are you using?
The one that came with the kit, I think it's the 4 B. I'm getting the same error after checking the cables. I attached a photo and the klipper log in case it's needed. All of this start happening after installing the IDEX kit (from hybrid, it worked well before).
After that I have to reset the printer completely (switching it off and then on) in order to be able to connect again, but it keeps happening over and over again as once I try to home the axes
Is the pi getting really hot maybe?
No, the temp seems normal. Also this happened just as soon I turn the printer on
Checked the temp. The pi is at 45 degrees
could be a software problem?
okay things are getting worse. Now it doesn't start. This is the message I got:
mcu 'beacon': Unable to connect
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
Even if I restart the firwmare, it doesn't start. I'm going to try to reinstall the RatOS to discard it's a firmware issue.
Okay, nothing. Any ideas @TheTik ?
Something is quite wrong. Maybe check voltages?
From software? I changed the current in some motors from 1.6 to 1.3 because the drive overheats. Changed it back to 1.6 but the beacon still failing. Which voltages should I check?
Take out multimeter and check that everything is getting the right voltage
Checked the power supply. 24V. Checked the raspberry power, it's 4.94V. Also checked the motherboard, it's 24V too. Any other ideas?
Other than replacing components one at a time, nope :/
I hope not, I'm flashing again everything to see if the firmware is corrupt
Bon chance
Thanks! I'll post what I'm doing to see if someone can help me, because right now I can't do anything with the printer
Are you still having this problem? I started having it out of the blue as well. I have to wait for about 10 minutes before I can do anything after powering on the printer. Being Summer, I have been printing much so been turning it off/on as needed. I am not 100% positive, but believe this started after I updated to RC3. Had not seen any errors since had to replace the thermal fuse on the bed heater.
What kind of SD card you using and how old is it? High CPU usage can sometimes come from IO waiting if the SD isn't up to the task or is getting old