First I’d build a new image on a NEW sd card and retry the Pi3B
Do you have a touch screen (or other hardware) that locks you into RPi?
I run my 2 printers off a Microsoft Surface Go ($65 used from eBay) and have had zero issues and I adore the 10" touch screen. Requires a USB hub (only 1 port on machine) and a accelerometer with a USB interface.
@cardoc I’ll try to build a new card, even if i think there shouldn’t be any problem with the current one (hi quality samsung high endurance).
I have a touch screen connected via DSI display port.
I have a couple of old android tablets (Samsung S2 8” and a Nexus7 2.0) but i tried the klipper stuff on android in the past and wasn’t reliable enough.
Also, i have an old windows tablet with touch screen, but to say the truth i’d prefer sto stay on raspberry (it served me very well until now).
I have no knowledge about the USB hardware RPi models use. I find it shocking that the MCU firmware change results in a USB signal that crashes your Pi. But seeing is believing.
If I were you I’d examine your upgrade budget and consider if getting rid of the GigaDevice MCU makes more sense than a Pi upgrade.
As I see it you have 2 issues:
Going forward is the next Klipper firmware change going to elevate more compatibly issues in the GD MCU?
I’ll try with a new SD.
I’m a tinkerer but sadly i don’t have anymore too much time to start even thinking to replace the printer board with something less cheap (and, expecially, how to do it without getting crazy before i can have a printer… printing again).
My Flsun is ok for my needs but it’s also getting older.
If i have to think about replacing it, well, i may aswell replace the whole printer (snapmaker or bambu), wich would also mean abandoning klipper (wich i’m not so keen to do).
Yes, i can keep printing with an outdated version of klipper, but usually i want to be up to date.
I’ll try with a new SD and let you know.
TY.
Well, re-did the SD and it looks now it’s working.
What’s even wierder is that, when i installed on the new SD 572 i had 349 on the MCU.
It didn’t complain about the “‘mcu’ has deprecated code (it is missing feature ‘STEPPER_STEP_BOTH_EDGE’ Recompiling and flashing is recommended”.
Doing a backup of the SD now, i’ll try to print something soon to see if it hangs during printing.
For now, thanks everybody 
UPDATE: it was the USB port in the RPI.
I tried again the ‘old’ sd, but switched the USB port on the RPI: connecting it to the one close to the ETH, it works.
This was even weirder.
So, i did some prints.
While it doesn’t have the startup problem anymore with 572, after a while it crashes again.
Going back to 349.
Klipper 573 MCU 349 (on another SD) = Crash while printing after a while.
Klipper 573 MCU 573 (on another SD) = Crash while printing after a while.
Klipper 349 MCU 349 (on another SD) = Ok (always).
If it was a sketchy USB cable it would happen always.
I agree.
Do you have klippy.logs of both scenarios? If yes, please post.
Hi,
I posted them multiple times in this thread.
With 573 they’re exactly the same.
Here’s a klippy.log with klipper 573 mcu 573 (it crashed the PI nearly immediately).
(temp is set to 190 because i ran the test without filament, i had enough of wasting it for tests).
For logs with 549 you can get the other ones in the thread.
Thanks.
klippy.zip (98.0 KB)
No, it’s Git version: ‘v0.13.0-349-g3215e3a2a’
Why don’t you rename the klippy.logs with the version number? Easier to find the right one.
Just upload the two logs with a better naming.
It starts with 349 but then continues with 573 after upgrading klipper and mcu firmware.
Line 976:
Git version: ‘v0.13.0-573-g644cda5ec’
Line 2819:
Loaded MCU ‘mcu’ 147 commands (v0.13.0-573-g644cda5ec / gcc: (15:12.2.rel1-1)
Tried on:
Klipper 349 MCU 349: works
Klipper 579 MCU 579: works
on an RPI4.
Same story on RPI2.
So, same SD, same OS version (RPI3 and RPI3), same printer, same cables, same MCU with same firmware.
RPI3B fails in versions over 349, the others don’t.
RPI3B ok with 349.
That tells me that something in Klipper after 349 broke working in RPI3B leading to crashes.
Can’t say in wich exact commit, i can’t run a 30 minutes print simulation for over 230 times.
MCU is ok.
This is all i can do to spot the weak point.
Said that, i’ll order an RPI5 and that’s it. I need everything to work.
I still think (without a sample to test on) that your primary issue is compatibility with the GigiDevices MCU.
I’ll be interested if the new Pi runs reliably.
You may be right, no idea. I’m not skilled enough on the matter.
In those cases i rely on tests and results.
I ran hours long tests on all three RPis, the results are what i reported: 3B crashes almost immediately (and in multiple tests on the same print, it always crashes at the very same point).
PI2 and PI4 just keeps going without a problem.
Beside, what’s crashing is the RPI3, not the MCU. I don’t think there’s a way for the remote MCU to crash the raspberry. That’s software on RPi side.
Maybe PI3 is failing? I ruled that out because it’s working fine (same print) with 349.
Of course i tried different prints.
So, that’s it (for me at least).
Thanks.