#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
I’ve got a Manta M8P running with the CB1 - what problems are you having? Need a little bit more detail, explained here in your original post - so that we know what we’re dealing with.
@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
#3dprinting #3dprintingbug
So upon reboot, is the CB1/Pi seeing/activating the CAN0 interface? First thing is to check is if the ID is changing, or if something is changing between power cycles.
The other thing I’d be concerned about is maybe the boot/programming button being sticky and when you’re rebooting it’s putting the board into programming mode each time? You could be flashing it, and it firing up after the flash, but power cycle putting it back into programming mode.
@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.