That doesn’t mean it’s the board actually controlling the printer though. It could just be used as an interface component because they’re easy to use as the middle-man on network connected devices.
You’d be surprised how often the UART is already exposed for factory programming.
As well, what I gathered from that thread is that they aren’t supported, because it’s a bit of overhead, and because they aren’t supported no one makes ESP32 printer boards. I think if suddenly a whole bunch of folks with A1s wanted to replace the firmware that might be a good userbase to add support for?
Maybe, maybe not it’s hard to say. I think most BL printer owners don’t really care or don’t want to mess with soldering tiny wires to tiny pads on their board and mess with flashing the device. The people buying these are generally not the tech-fiddling type.
I’m the tech-fiddling type and I bought one, my housemate is the tech-fiddling type and she bought one, our friend is the tech-fiddling type and she bought one. We all bought them because we wanted to spend our tech-fiddling time on the projects themselves and not on the printer.
I think it says more about the echo chamber in this thread that no one can conceptualise why anyone (that’s a tinkerer) would want to limit tinkering on one thing, so they can enjoy tinkering on another.
Edit: Like, that was the case for me, but now they shit the bed so I’ve got to tinker with it to keep the features I prefer.
That doesn’t mean it’s the board actually controlling the printer though. It could just be used as an interface component because they’re easy to use as the middle-man on network connected devices.
I am fairly sure it’s what is controlling the printer.
Looking at the board, I think you’re right but it’s definitely a custom board so exposing the UART might be fairly difficult.
Although it looks like it wouldn’t do much good (no klipper support for esp32)
You’d be surprised how often the UART is already exposed for factory programming.
As well, what I gathered from that thread is that they aren’t supported, because it’s a bit of overhead, and because they aren’t supported no one makes ESP32 printer boards. I think if suddenly a whole bunch of folks with A1s wanted to replace the firmware that might be a good userbase to add support for?
Maybe, maybe not it’s hard to say. I think most BL printer owners don’t really care or don’t want to mess with soldering tiny wires to tiny pads on their board and mess with flashing the device. The people buying these are generally not the tech-fiddling type.
I’m the tech-fiddling type and I bought one, my housemate is the tech-fiddling type and she bought one, our friend is the tech-fiddling type and she bought one. We all bought them because we wanted to spend our tech-fiddling time on the projects themselves and not on the printer.
Great, then you can band together and make the klipper version and use it…easy peasy
Your own little bubble doesn’t say much about the general buyers of BL printers.
I think it says more about the echo chamber in this thread that no one can conceptualise why anyone (that’s a tinkerer) would want to limit tinkering on one thing, so they can enjoy tinkering on another.
Edit: Like, that was the case for me, but now they shit the bed so I’ve got to tinker with it to keep the features I prefer.