I have some professional experience with CANBUS. I’m not sure if that will help or hurt me. Sometimes knowing a little can make you take the wrong path because you “know better”. I’m probably over thinking it. It is probably just going to be flashing the mcu and configuring klipper to use it.
heheheheee…
We’re dealing with PPP at work right now. The engineer working the project is discovering the hardware we’re wanting to use is using a bastardized implementation of the protocol. It’s hilarious listening to him on calls discussing what he’s “discovered” today (only because I’m not the one doing the work). To be fair, the engineer is a little younger than the rest of us. One of the more senior engineers offered to send him his college text book on it.
3 Likes
It’s really funny when you start thinking, “Why the heck did they do it this way?” and inevitably you later figure out there was a good reason, or you decide that they made one terrible decision and it cascaded into a bunch of dumb compromises.
Honestly, I feel like this whenever I look at code I wrote that is more than 6 months old. It’s long enough for me to forget the motivation for the weird choices I’ve made.
All the code I make for V1 is perfect though. I’ve never done anything weird or wrong with that stuff 
3 Likes
The plot thickens on my klipper issues. One of the klipper members built be a klipper.bin from the same code and it builds and runs fine. So something is wrong with my build environment on the pi. I’m trying to spin up a docker container to build it again. But at least the trouble is academic now.
Okay, I hope this doesn’t come off wrong but thank goodness this happened to you and not me. I would be lost.
2 Likes
Not to state the obvious, but is your OS up to date? Is it possible a library changed causing issues with the compiled firmware?
1 Like
I know Klipper changed to python 3 recently. @niget2002 might be on to something
That shouldn’t have anything to do with the firmware being built. That should all be UI/Pi side.
1 Like
I agree completely!! Even when I think I know a little bit I quickly find out I don’t LOL
2 Likes
I updated my apt packages before starting. I still don’t know what happened. I built it in a docker container and that version is working. Maybe I had trouble flashing it, IDK.
I wish it had happened to one of the Klipper developers instead. 
1 Like
I can follow along with most of it until you say…
and then poof I’m lost LOL
1 Like
How are you passing the usb to docker?
Agreed!
2 Likes
You can build the package in docker, but have the final image saved to the core OS. Then use the normal flash utility to flash the image. Docker itself doesn’t need to handle the flashing.
2 Likes
This is an skr, so I need to copy the firmware.bin to the sdcard.
I used docker cp to copy it from the container before I closed the terminal. I know docker is overkill, but I don’t like installing dependencies on my host. It is a rule I follow to make my computer more stable. There is a perfectly good dockerfile in the scripts folder of klipper. So it wasn’t bad. I put the commands I used in the klipper forum post.
I do the same. I just typically volume mount the directory so I don’t have to worry about moving anything.
1 Like
Printing Petg test cube. If this is successful, then I’ll print a Petg cooling fan.
Then I’ll either print a Petg core for the v4, or try printing Asa directly on this machine.
I’d rather print the Asa on the v4 as it has the enclosure, but this machine is all metal, so it might handle it better. I could do a caedb box enclosure.
1 Like
Looks great so far!! Should have printed this cube…
https://www.printables.com/model/416565-v1-engineering-calibration-cube
I didn’t even know it existed till I was looking for something else yesterday lol
1 Like
