#3dprinting @[email protected] @[email protected] does anyone have experience with the manta m8p motherboard and canbus? I’m pulling my hair out trying to work out what’s going on with mine and could really use a little help
#3dprinting @[email protected] @[email protected] does anyone have experience with the manta m8p motherboard and canbus? I’m pulling my hair out trying to work out what’s going on with mine and could really use a little help
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