Printer Model: Ender 5 plus
MCU / Printerboard: skr pro 1.2
Host / SBC: linux mint on fujitsu e765
log and config files config-20240930-113244.zip (11.0 KB) klippy (26).log (1.1 MB)
hello all,
i’m getting kinda crazy here. i have an ender plus with an skr board, turned to coreXY.
the issues with disconnecting have been crazy, sometimes not even able to home X, and, no new cable (at 6th one), no new host, no new update, no new psu, no new internal cables, no attaching any other usb device, no changing port nor disabling autosuspend for usbs in linux, no changing from by-id to by-path, no disconnecting internal wires one by one to see if that particular wire was shorting have fixed my issue.
yes the psu is totally new, same voltage just 600w instead of the classic 500w from creality. the issues were present also with the old creality psu.
It’s already a pair of weeks i’m troubleshooting it with new parts and new ideas on config.
new psu:
i have bought 6 cables in total but i have not thought of cleaning the connections as the board is 2 months old and still looks new as it was in its enclosure.
I really cannot understand what is goin on but the next thing i’m goin to try and put back the old psu.
Can I suggest that you try something like a Raspberry Pi 4B as your host instead of your Fujitsu e765?
I can understand the rationale for using a laptop that has no other use (your Fujitsu e765 is at least six years old) but getting Klipper to work on a laptop reliably is a challenge at best.
I would give it a try. We are talking about Chinese (skr pro 1.2) boards, so they use Chinese (maybe cheap) connectors. Nothing against Chinese goods, no offense at all.
The board lays (for how long?) in a storage. Nobody knows about the storage conditions. All could lead to connection problems.
And, how old is your fujitsu e765? First tests are from 2017
Blockquote You may consult your Linux system logs and dmesg to see if there is anything shown on this level.
Just issued a sudo dmesg and this is what i see:
definitely gonna try because yes is old, but another odd thing is that sometimes it just tells me it disconnects, sometimes it tells me that other error with the timer set in the past and the mcu receiving more steps that it can process.
it was working at 128 microsteps for 2 months. i put it down to 16, hell even to 8 and sometimes i still receive that precise message about the steps.
in all of this is weeks i can’t print.
this new psu also has a rheostat and trying to move it just doesn t make anything
Well, if it is a connection failure, what do you expect? Klipper can tell you anything if it get’s faulty data. But if the data is not too bad to throw an error, you’ll get funny errors (just guessing).
BlockquoteWell, if it is a connection failure, what do you expect? Klipper can tell you anything if it get’s faulty data. But if the data is not too bad to throw an error, you’ll get funny errors (just guessing).
It’s sad. I’ve stopped drinking and my klipper is drunk (and apparently dirty too🤣)
When I suggested that you consider a Raspberry Pi, it had nothing to do with processing power but execution consistency.
Commercial PCs/laptops running mainstream OS’s (and I consider Mint to be one) have a lot of things going on as well as install various applications that run as processes which is fine for a human user and most applications - but not for Klipper that requires reasonably precise timing of data packets they can cause unexpected delays that lead to “Timer Too Close” and MCU disconnects.
You can spend time studying your system and looking for processes to kill to see if that improves the situation but it will be a lot of work with a poor probability of success (I’ve been down this road with an old Asus laptop running Mint).
Looking over the thread, it sounds like you’ve dropped a few bucks trying to nail down the problem (new power supply, multiple USB cables), could I again suggest that you get yourself a $40 USD Raspberry Pi and try it in place of your Fujitsu and see if things improve?
Blockquote could I again suggest that you get yourself a $40 USD Raspberry Pi and try it in place of your Fujitsu and see if things improve?
Is not my day one of running this build. it sustained hours and hours of printing, goin for successful 16h prints too. This what i described happened from a day till now but before that the laptop was dealing with 10+h prints like a champ.
will try a pi eventually, but i have another very little test to do that is goin around my mind. and if that works, i don t need a pi.
but, what about mainsail OS or forcing a raspian on that fujitsu?
I’m trying my chance flashing the latest raspiOS on a netbook that initially was running my klipper. had some prints with it but then said “why don’t i use that fujitsu?”.
as of now it has mint too and i have the exact same errors
lil update: cleaned ports, changed OS in ubuntu desktop on the fujitsu, same errors.
I’m starting to think is on a printer side…
in a while i should receive a pack with some spares in order to finish an ender pro with skr 1.4 turbo. will try it and update again.
One thing i’ve noticed, is that since i switched to corexy, i’ve been starting to have way more disconnections. i’ve made the upgrade, i had a benchy and another 4h print and then the situation i’m in now. when it happens, the controller fan makes a huge increase in spin for half of a second and then the mcu disconnects.
Looking at the above comments I want to add that many Linux distros use different USB and canbus polling. So using an x86 Linux version on a laptop can afe t anything requiring tight timing with no to little ecc (like klipper) or certain gaming mice / controllers. games - Modifying the polling rate of usb devices - Unix & Linux Stack Exchange.
Also as a note the kernel version / patches can change these values reset them or affect interactions. So can system services which is why mainsailos and rasbian use a very lightweight overhead distro base.
