Printer Model: Voron 2.4
MCU / Printerboard: BTT Octopus
klippy.log
klippy2.txt (748.9 KB)
About 2 weeks ago, I added bed fans to my Voron 2.4. Everything was working perfectly for about 1500hrs of print time except for some minor warping of prints. I figured bed fans would increase the chamber temp and solve the warping. It did. But I started getting some cryptic stepper driver errors and the printer would shut down mid print. The first error was this:
TMC ‘stepper_x’ reports error: DRV_STATUS: 001903c3 otpw=1(OvertempWarning) ot=1(OpenLoad_A!) olb=1(OpenLoad_B!) t120=1 t143=1 cs_actual=25
Sometimes it would show on stepper_y as well. I figured they were overheating so I increased the fan speed for my electronics bay. Same thing happened. I turned off the bed fans. Same thing happened. I replaced the wiring from the X and Y motors. Same errors. Tried replacing SD cards in the Octopus and the Pi. Same thing. At this point I also started seeing a new error:
TMC ‘stepper_x’ reports error: GSTAT: 0000001 reset=1(Reset)
I started to think something was wrong with the drivers so I swapped the X and Y drivers with 2 of the Z drivers to see if the error followed the drivers. Also figured that the Z drivers are used less than the X and Y so maybe it would just work. Now, the only error I get is this:
MCU ‘EBBCan’ shutdown: Missed scheduling of next digital out event
I still thought maybe this had something to do with my drivers so I replaced the X and Y drivers with brand new ones and moved the Z drivers back to the Z motors. Still getting CAN errors. Currently this is the only error that I am seeing, but I wanted to provide the other errors for context.
There was recently a considerable amount of drywall dust in the room and I thought maybe that had something to do with it so I blew out all of the electronics with an air compressor. Same thing happens. I did realize that the 120 ohm resistor was not jumpped on the CAN board so I added that. I’ve reflashed the firmware on the CAN board. Also set up CanBoot. Everything is updated with the latest version of everything. I have not reflashed the U2C board as it doesn’t seem that there is a new version of the firmware since I last did it. Currently I am testing increasing the baud rate from 250k to 500k on the CAN to see if that helps. The error only happens randomly mid print. The only way I’ve been able to test and replicate it is to run a long print. Total print time should be 7hrs. Sometimes it happens after 2hr, 5hr, 6hr. Never know when it’s going to happen. I’ve been running the bed cold and with no filament to save electricity and filament. Should also note that this is v1.1 of the U2C board. Apparently there is an issue with v2 that does exactly this, but this is not the v2 board.
If increasing the baud rate does not work, I plan to try reflashing the U2C and if that doesn’t work, I plan to try using the build in CAN transiever in the Octopus and just ditch the U2C all together. But I’m beyond frustrated and running out of ideas… Please help…
Update: after changing the baud rate from 250k to 500k, I’m back to the driver overheating error. FML
Just an FYI, I did edit out the middle of my log file as the file was too big to upload, but I think all of the important stuff is there.