

@j4k3 actually sorry, I just saw that my changes here on mastodon don’t reflect on Lemmy :( sorry… Feel free to delete it from your instance if it’s causing trouble
Freelance Nerd
Website development
Network administration
Learning #docker and various other systems
@j4k3 actually sorry, I just saw that my changes here on mastodon don’t reflect on Lemmy :( sorry… Feel free to delete it from your instance if it’s causing trouble
@j4k3 I wouldn’t say it’s useless, the bot boosted my post for extra visibility, but I’ve removed it for you
@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
@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
@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
@thantik ok so the manta is all wired up and itself seems to be working well. I had all it running for a couple of days getting various things working which meant it was rebooted or power cycled a lot and always reconnected using the ID
But then I went to setup the Hotend canbus which is using the ebb sb2240
Flashed both the ebb and the manta to use canbus, changed the printer.CFG to use their canbus IDs and klipper connects and works fine
After a reset or power cycle though, it won’t connect again and won’t recognise the board until I reflash it
Google comes up with a number of posts of similar issues, most just with answers saying how to flash it correctly or no answers at all
This is my first self built printer, it’s a voron 2.4, but I’ve heavily modified my old ender 3 with klipper, just never anything with canbus so I’m probably just messing something up
@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