Traded my Raspberry Pi 4 for a Rpi 5

[NoGuru]

I know its not a needed upgrade but I think it was worth it.

It was pretty easy to just move my config over and reinstall packages. For example I use Shake n Tune for my input shaping, I just copy my config over and go to the Github page and reinstall, and it all works.

The Pi 5 uses, MORE POWER BABY, so I bought a meanwell DIN PSU and use that to power it. I just put double side sticky tape and slapped it to the bottom of the printer for now.

It boots way faster but I also added an M.2 tophat to it and run klipper off the SSD.
Running input shaper sends my results way faster like 10 seconds instead of taking minutes to calculate.
what else...oh, it was just fun to do.

If anyone has questions I would be happy to try and answer.

 

[NoGuru]

One thing I lost and I have not looked into much is my Klipperscreen. I use one of the BTT screens with a ribbon cable and PI5 has mini HDMI or something. I need to figure out how to get that back up and working.

If anyone has suggestions let me know?

 

[Yaaj]

This ?
Came with a Waveshare 4.3" (not a great fan of this BTT display and its stupid potentiometer !)

 

[NoGuru]

This ?
Came with a Waveshare 4.3" (not a great fan of this BTT display and its stupid potentiometer !)

It's close to the same. I have the TFT50, but it's the same. I think I am just going to delete the screen for now. I know BTT has the HDMI5 or whatever, but I really never use the screen.

 

[Andy3D]

Algo que perdí y que no he revisado mucho es mi Klipperscreen. Uso una de las pantallas BTT con un cable plano y la PI5 tiene mini HDMI o algo similar. Necesito averiguar cómo recuperarla y que funcione.

Si alguien tiene sugerencias ¿me lo puede hacer saber?

Tenes que comprarte un cable plano de 22 a 15 pines para poder conectar la pantalla a la pi5

 

[akp55]

why not just use an intel mini pc instead? cost is pretty much the same once you factor in the m2 ssd

 

[NoGuru]

why not just use an intel mini pc instead? cost is pretty much the same once you factor in the m2 ssd

I could and I have a few of them but I also had the Pi5 on hand and I like the small form factor.

 

[negativeone13]

Bringing up an old thread... did you have to do anything to get your Pi5 to see the NH36?

I have tried everything and still can't get it to see.

Not found in usb-devices or lsusb, even as only device plugged in
Tried a few different USB cables
Reflashed Katapult
Put in boot mode
dmesg and moved around USB ports
Verified 5.1xV at buck converter
10A on supply, get-throttled reports back 0x0 always.

Nothing registers it as even being seen. I can literally plug it into my Pi3 and sees it no issue.

edits: add things I've tried.

 

[NoGuru]

Bringing up an old thread... did you have to do anything to get your Pi5 to see the NH36?

I have tried everything and still can't get it to see.

Not found in usb-devices or lsusb, even as only device plugged in
Tried a few different USB cables
Reflashed Katapult
Put in boot mode
dmesg and moved around USB ports
Verified 5.1xV at buck converter
10A on supply, get-throttled reports back 0x0 always.

Nothing registers it as even being seen. I can literally plug it into my Pi3 and sees it no issue.

edits: add things I've tried.

I don't recall doing anything other then having to reload some of the repos.
I will link you to my backups in case you wanted to look through them. https://github.com/NoGuru2/VoronV2.4

 

[negativeone13]

I don't recall doing anything other then having to reload some of the repos.
I will link you to my backups in case you wanted to look through them. https://github.com/NoGuru2/VoronV2.4

Thank you, I don't even see it when I connect after freshly installing PiOS, both lite and full. I don't think it's a Klipper thing, rather board/Pi driver package.

I just don't know, it's frustrating.

 

[StefanT]

Run `dmesg -w` and plug in the NH36. It should print some diagnostics messages if it is detected at all.

 

[negativeone13]

Run `dmesg -w` and plug in the NH36. It should print some diagnostics messages if it is detected at all.

On the pi5, dmesg -w sees nothing of the NH in all 4 USB ports. It sees the octopus in every port like it should. Fresh full 64 PiOS, updated and upgraded.
On the pi3, dmesg -w sees the NH on all 4 ports, and sees the octopus on all 4 ports.

This is what the pi3 sees when plugged in.

 

[negativeone13]

This has been solved by the help of KB-3D, they are a bunch of great folks. I want to add this in case someone else comes along this.

LDO had a tech note about the R7 resistor causing the boards not to be seen. This applies to version 1.5 USB adapter boards. Removing the R7 resistor allowed it to see it properly. Run ls -l /dev/serial/by-id/ and you should now see the device. I have attached the actual publication if needed.

 

[3dCase]

@NoGuru I recall you ran a beacon, is this still correct?
If so does it give you a klippy log where the version ends with "dirty" or not?
I use cartographer, as you know, and since my latest update of klipper it gives me stepper.error something to do with step compression. It always mentions the error lays with my scanner.py, which is what klipper does not like because it is one of the files that it mentions as "untracked".
now I have an almost dead Voron 2.4 which I have to watch like a hawk during the homing, QGL and the bedmesh since it does not abort on the error and jolly well will slam de carriage into the frame if the error pokes up its ugly head.
for reference:
https://klipper.discourse.group/t/stepper-error-internal-error-in-stepcompress/24571/23

Very annoying and since I value klipper more then the cartographer, I think I will be buying something else.

P.S. nice to see a pi5 in action. I have one laying about which I might use on my zero instead of the cheapo replacement that came from formbot.
P.P.S I read interaction with cartographer users and the support and unfortunately they seem a bit blasé about it all and unwilling to accept it is their responsibility to rectify the dirty repo. Not sure what I can expect from them, if anything?