It would be nice to have an 8-driver version of the 6 pack. Unlike most other controllers, the 6 pack can be easily upgraded to a newer/faster mcu. The esp32 currently supports marlin, grbl, rrf and klipper firmware could be compiled for the esp32 via platformio.
Still with extremely limited IO, as far as I know there is no way to run 6 TMC drivers with enough IO to also plug in everything to 3D print. I would love for that and I spent a ton of time looking, but I donât think it can happen. Pretty sure you can not run the 6 pack with Marlin for 3D printing.
Yeah, that is very low on my list. Passing thousands and thousands of boards through my hands each year I have learned that takes a dedicated company to manage that sort of thing.
Well maybe with Klipper but that just adds another board to deal with.
Agreed, the 5 existing expansion modules are for CNC functions only such as spindle control. There are no module designs to support 3D printing such as heaters, thermistors, bltouch and fans. I counted 12 gpio pins dedicated to CNC expansion modules in addition to endstops so it is possible enough gpio pins are available to support 3D printing. Might be worth discussing with Bart Dring.
I did discuss some of this with him and another board manufacturer. The TMCâs are pin hogs so if you add one more driver you might as well add 3 I think, but that kills another 3-4 pins if I remember right.
We just need an esp32 v2 with more IOâs and we would be set!
What I think is a good option here and what I am trying to work out, is finding a great base board that is inexpensive and adding something like the esp32-cam board to enable headless and SD for a few bucks. I am not really seeing any practical differences in boards these days as long as it has enough drivers, and a few extra IO.
The game changer recently is finding out that GRBL runs on these current boards with no compromises. That is my bad for sure, John worked that out 2 years agoâŠI am just now catching up.
So now my board search has changed a bit. Price/cross âplatformâ/headless. That headless option is for price mainly but I am hoping that esp32cam makes all board headless capable. Just not sure if we can use the micro SD on it for reading files. My test boards show up Saturday to find out, then figure out how to connect them to the SKR and RamboâŠthe Octopus would be plug and play.
Ah, I see where you are going with the esp32cam. I have a stack of cheap esp32cam boards to experiment with interfacing with mks boards. I was about ready to start working with these boards for another project anywayâŠ
The esp32 doesnât have many IO. And the bart 6x board uses the shift register to handle a bunch of extra IO. It is easy to say that ESP32s run Marlin, but can Marlin talk to the shift register? If there was a marlin focused ESP32 board, would the chip they use to expand the IO be usable by FluidNC? And then RRF, and KlipperâŠ
They are excellent options, and not by accident. You have been selling the rambo for years now. The Skr Pro was a deliberate choice when you couldnât find enough rambos (Before the skr, there were archims, and you couldnât buy them). The Skr Pros are not going to be available forever either. Thatâs why there was a board search in the first place.
I donât miss the mini rambo, but I would like to have a board with just 5 drivers in a small package that can run reliable, quick CNC/Laser firmware. Some of these smaller skr boards are very useful looking.
The only problem with Klipper will be with a laser module, as it has been described on github Klipper Docs under Limitations
It does, see:
Fluidnc:
Klipper would need to be modified to support i2s pins.
The issue is still we canât get eh 6 pack in quantity and with all the modules we would need it would be very expense. Until there is a specific board set up as needed with a good price I donât see any reason to pursue the 6 pack, or any other esp32 based board.

The only problem with Klipper will be with a laser module, as it has been described on github Klipper Docs under Limitations
That is nuts! Thanks for that info. So we still need to just focus on GRBL, RRF, and Marlin. How Is RRF with the Raster laser? I guess I could run that test, I have a new project on my table currently though so no promises to do that right away. Heck if RRF works better than Marlin, that is a pretty easy switch I think just provide the config files right?
P.S. I love this I feel like we are getting somewhere quickly!
Sounds like someone needs to badger Espressif for an ESP64âŠ
Iâm waiting for my MKS TinyBee board to arrive.
This is a 5x board though.
This board is supported by Bartâs FluidNC and Marlin also.
I actually bought it because recently Iâve added a few more MCU to ”CNC (including basic support for the ESP32).
I want to run deeper tests on the ESP32 and try out my module for the 74H595 shift register but need I the board for that.
Iâve recently added SD card support and I am currently doing an additional module for the Reprap Full discount graphic displayâŠbut is still being developed.
Just one question. Is there a specific reason to opt for the 6x boards?
That Tinybee is neat. Will it talk uart to tmc 2209 drivers?
Iâm also worried about the number of endstops for 5x. I see a few extra ports, but they arenât labeled as endstops.
I donât know if Marlin or FluidNC will talk to the TMC2209 drivers. The TX2 RX2 available pins are there to be used by the TFT (2,4" or the 3,5") I believe.
It is possible though. A single IO pin could be used to address the TMC in multislave mode, but I believe that would mean that it would be an MCU to TMC one way communication only.
The endstops are designed as X Y Z and probe.
The thing about the ESP32 and the 74HC595 is that the latest can only be used as an output IO expander and not an input IO expander. For that you still need ESP32 free pins.

Just one question. Is there a specific reason to opt for the 6x boards?
The MP3DP v4 with hardware leveling. Not really needed for CNC unless you want to be able to still 3D print and having dual squaringâŠwhich could be cool for something I am dreaming of making.
As much as I like the esp32 people seem to put in a lot of work to try and make it work. In terms of bare processor costs is it that much better than anything else? I get they are amazing hobby boards but we need more IO for 3D printers, and it can barely do a CNC.

In terms of bare processor costs is it that much better than anything else?
Yes they are dirty cheap and they are a dual core MCU running @ 240Mhz with Wi-Fi and Bluetooth.
The other side of the coin is that you are forced (as far as I can tell) to use an RTOS with it. The level of indirection on the ISR level is very trippy⊠Itâs easy to make the one of the processes blow up and get a reset. And Yes very little IO. Some IO drivers are even done via internal libraries software (like the I2C or PWM on the Esp8266 I think)
Iâll be honest. In this aventure I became a big fan of Stm32 chips.
Very cheap and very well designed. All the IO and IO drivers you need⊠If you want wireless or BT then you can team it up with an ESP.
I donât know whatâs required to reliably control steppers via TMC2209 drivers using ESP32. But, to shed light on what IOâs possible, Iâve previously supplemented ESP32 to drive 192 individual 9g Servos using a bunch of I2C based IO breakouts like PCA9685. But that was just to mess around for a tech art project. I wasnât trying to create highly available production quality machine.
Is there good documentation of which versions of GRBL fit which systems. For example, I have a bunch of old RAMPS 1.4 and 1.6 from old 3D printers, but when I looked into getting GRBl to run on those the documentation was near impossible to follow.
Similarly, I have an old MKS Smothieware clone board and couldnât easily figure out what to run on it.
Just reading this thread it still isnât clear which GRBL versions to even explore.
You have several ports of Grbl for specific boards and/or applications.
For ramps the ones I know are:
- Grbl-Mega (from the maintainer of Grbl)
- Grbl-Mega-x5
- Grbl-L-Mega (this is aimed at lathe control)
- ”CNC (not a Grbl port but is based on the same protocol)
For the MKS smoothieboard maybe:
- grbl-LPC
- grblHAL
- ”CNC (may support it by creating the respective board map file)
I think only grblHAL and ”CNC are âwide spectrumâ projects as in multiple MCU/BOARDS cover.