MKS-PI
MKS-PI copied to clipboard
makerbase-mks
MCU shutdown: Timer too close
I keep getting dropouts on one of my MKS Pi units (I have two of them). At first, I thought it was a cooling issue, so I installed fans, then I thought it was a voltage issue because I was running off of my PSU, so I connected to a dedicated 24v/2a power supply, then I thought it was armbian/klipper firmware versions, so I updated those, then I thought it was a broken HDMI cable, so I replaced that. Nothing I do stops one unit from shutting down while the other one goes along merrily. I have two identical setups on two almost identical printers (same brand, similar motherboards, etc). I ran side by side tests with the same program and machine A fails while machine B chugs along quietly. I then hooked up a BTT Pi4B/CB1 that I've got, using the same connections (7" hdmi screen, UART to the MCU) and I just keep running the same program over and over at 300% with zero failures which leads me to believe that something is wrong with one of the Pi units. The pi in question also runs 10 degrees hotter than the the one that works fine routinely (at idle and while running)
Here are the specs of my setup: MKS Pi V1.1 emmc module latest release (3/1/2023) MKS Pi Armbian latest klipper/moonraker/fluidd/klipperscreen releases as of today
it's now happening on both of my MKS Pi units, but the most recent shutdown is a Rescheduled timer is in the past alarm
Try a ferrite on the USB cable next to the board USB connector it helped me a lot as it removed the disconnects completely to my printer.
I was running UART on a 4" long cable
On Tue, May 30, 2023, 9:40 AM jmmacip @.***> wrote:
Try a ferrite on the USB cable next to the board USB connector it helped me a lot as it removed the disconnects completely to my printer.
— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-PI/issues/47#issuecomment-1568456255, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARUZ2LKVAHHKJDQDYSFH57LXIX2EDANCNFSM6AAAAAAV3GSIUI . You are receiving this because you authored the thread.Message ID: @.***>