klippy (59).log (3.4 MB)
Well, the printer was printing well for more than 400 hours and suddenly printer started to shutdown during print, when i look at the log it shows bytes_retransmit is climbing just before the error.
I have changed the power source, the cable between mcu and raspberry, the mcu itself and the sd card of the raspberry and I installed an EMI filter but nothing changed, I have uploaded the klippy log please help, I can’t figure out what is wrong
If the printer has worked flawlessly so far and now suddenly throws this error, this suggests a failure of an electrical component. Either a component itself or the wiring to it.
See Timeout with MCU / Lost communication with MCU
I have changed the motherboard, tmc drivers, most of the cables, removed the chamber and filament thermistors, changed the power supply, tried using different sd card but nothing solved the issue so far, only thing I didnt changed is the raspberry itself
Not sure what you are expecting now for a machine that we do not know or own.
Working turned into not working == something probably changed.
Taking extraterrestrial influence out of the equation, the known reasons for this kind of error are listed in the link I provided above. Unfortunately, we cannot provide any more guidance on this.
I will change all the cables and raspberry and continue trying, thank you for trying to help
Maybe you can enlighten us by giving us detailed information on the hardware you use.
I am using Octopus pro with 4 tmc5160 and 2 tmc2209 motor voltage is 48 volt and both power sources is 350w meanwell, I am using 2 ssr’s one for table one for controlling the power sources, and raspberry is getting its power by its official power supply. All power supplys are connected with an EMI filter and whole system uses 19 fans. I have an internal filament dryer which has 100watt ptc heater and bme280 sensor, the printhead has adxl345 and filament sensor is madde with diameter sensor which has ss49e’s. Printer also has neopixel. Both mcu and raspberry has active cooling, whole electrical system also has active cooling. And also i have an active carbon filter with 3 fans.
Furthermore if I measure the voltage coming out of outlet it moves between 207 and 225 volts.
You’re running the TMC22209s at 48V?
Maximum voltage for them is 29V as per the datasheet:
TMC2209_datasheet_rev1.09.pdf (1.8 MB)
1 Like
Do you have this problem with different 3D models?
nope, 2209’s is running 24 volt
Model independent problem, First thing I assumed was data corruption, tried using different models, even different slicer
1 Like
edit
Since you almost changed everything except your SBC
I think your RPi is faulty.
I run your attached klippy.log through Sineos excellent graphstats tool https://klipper.discourse.group/t/advanced-trouble-shooting-graphing-klipper.
Actually, I used the latest version Graph Klipper Stats (@Sineos, you might update that in your Knowledge Base).
graphstats.pdf (447.3 KB)
Have a look at the temperatures of your RPi shortly before the error occurs.
The temperature increases just a few degrees, but it’s significant and in my eyes suspicious. From more or less linear into an exponential curve.
I would try another RPi or other SBC…
…or could your OS on the RPi cause the problem?
Good luck, hcet14
Well, it turns out somebody crashed their car to our local transformer that caused the voltage fluctuations. When measured directly from wall power outlet it was randomly dropping below 200V and jumping to 238V. After they fixed the transformer everything went back to normal. I will buy an UPS just in case.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.