3DPrinting
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: or [email protected]
There are CAD communities available at: [email protected] or [email protected]
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is 
Moderation policy: Light, mostly invisible
view the rest of the comments
@thantik how do I go about that? The command the guide gave to get the serial ID only gives un adopted ones, so even on that first boot that works, they disappear
The cb1 itself is working fine on reboot as I can SSH to it and even load klipper, it just gets the MCU error.
The only way I can get any response from the board is to put it back into DFU mode and flash it again, when I do that, it gets the exact same id as the first time and connects again until reboot
Does your
ifconfigshow a can0 device? After flashing? After reboot?@thantik no, it does not. And I just realised that running the same canbus query script throws an error that I didn't see before, saying no such device
The /etc/network/interfaces.d/can0 file is there and correct though
And /etc/network/interfaces.d/can0 Looks a bit something like this?:
allow-hotplug can0iface can0 can staticbitrate 1000000up ifconfig $IFACE txqueuelen 128Sorry, Lemmy is mangling the shit out of formatting.
It sounds like the CANBUS board might have some sort of defect, tbh.
@thantik yup, it's identical other than the mangled mastodon indent haha
So just to check, when I reflash the board, it does show up in ifconfig but as soon as I make any changes in printer.cfg and hit save and restart, it's now not in ifconfig
Save and Restart should only be restarting the firmware for Klipper/Klippy -- ifconfig is part of the underlying Linux subsystem. It shouldn't disappear from there just because you restarted Klipper. I'd be willing to bet the canbus board is either flashed with some wrong firmware option (check which microcontroller is being used on it!) -- or that there is a physical defect with the board which is causing it to get stuck in programming mode on power cycle. I'm almost positive they aren't using an external eeprom on that board, which would be my next guess (bad eeprom).
From what I can discern, YOU aren't doing anything wrong.
@thantik the ebb is the rpi2040 so there's only the one option for the microcontroller
The issue happens with and without the ebb hooked up and the board works fine without canbus enabled so I'm sure that's the right microcontroller
Tomorrow I'll go back through and maybe start from scratch, reflash the bootloaders and then try fresh from there
In the mean time it all works if just using USB so I always have that fallback