Argh. Lost Comms with MCU is back

General Discussion
1

Basic Information:

Printer Model: Ender 3 Pro - well just the frame…
MCU / Printerboard: 4.2.7
Host / SBC: Pi 4 and Pi 5
klippy.log

I thought I’d solved the problem - but it is suddenly back.

I added 4 x Klippy logs in the Zip - I’m hoping someone can look and possibly find an answer?

4.2.7 Board - 2 weeks old

Pi 4 and pi 5 - tried both still errors

Mean Well PSU - 1 week old

4 different USB cables

Pi powered from original supply

reinstated Klipper multiple times on Pi and flashing MCU

I’ve triple checked all wiring between printer and MCU

I’ve completed all the regular ‘fixes’ that I’ve found online, the ‘Got EOF’ stuff, and the official klipper troubleshooting advice - none of it has solved the issue.

Prints always start, they just suddenly stop after an hour or so.

klippy.zip (6.8 MB)

2

Please do not use file servers, upload your klippy.log here:

Upload

BTW: Dropbox can behave strange on browsers.

1 Like
3

Which version of the OS are you running? I found issues with the 64 bit versions of Pi OS and CanBus, and going to 32Bit made a huge difference.

It might help with USB connected MCU’s too.

5

64 bit bookworm.

Since I can’t find any other faults I might as well try a 32 bit OS - at least removing it from the equation will be beneficial

1 Like
6

I tried but it wouldn’t accept it.

I’ll try again

7

If it is too huge, you have to compress (zip) it.

8

it is a zip. but when i use that upload it won’t accept zip files…

9

Just tried, works for me. Curious.

10

ahhhhh I used 7z … :person_shrugging:
klippy.zip (6.8 MB)

1 Like
11

ok interesting.

I grabbed the Pi 4, threw a fresh 32 bit OS on it, fresh klipper etc.
Flashed the MCU.

It’s just completed a 4 hour print…

I’ve got another long one ready to go, so fingers crossed.

1 Like
12

That is interesting, I’ve heard most of Klipper is 32 bit, but I’m not a dev, so I can’t confirm that.

@koconnor is this the case and should it make any difference?

Edit: thinking about it, these little arm chips we use for these additional MCU’s are 32 bit eg the STM32G0B1 etc. So I wonder if the issue has anything to do with mixing and matching 32 bit and 64 bit software causing the timing issues?