April 27, 2020 at 6:19 pm #1189
I’m upgrading my rumba to a rumba32 mks board.April 28, 2020 at 3:51 am #1536 never mind, I figured it out 🙄April 28, 2020 at 3:51 am #1537 never mind, I figured it out 🙄June 4, 2020 at 3:56 pm #1538 I finally received the MKS Rumba32 board from China. There are a few things that need fixing. It came without an eeprom chip installed. [attachment=2]Rumba32.jpg [/attachment] I installed one with advice from the board designer here. [attachment=1]no_eeprom.jpg [/attachment] https://github.com/Aus3D/RUMBA32/issues/12 [attachment=0]eeprom.jpg [/attachment]June 4, 2020 at 4:10 pm #1539 I’m upgrading to tmc5160 drivers with the board. Unfortunately there is another problem, Marlin only supports SPI with the tmc drivers and there is a bug in the board design detailed here https://github.com/Aus3D/RUMBA32/issues/23, and here https://github.com/makerbase-mks/MKS-RUMBA32/wiki/About-RUMBA32-TMC-SPI-%22CONNECTION-ERROR%22-FAQ https://github.com/makerbase-mks/MKS-RUMBA32/issues/2. I’m trying a the mod I outlined in the last post in the last link. The tmc driver comes with several of the legs snipped off on the top of the driver. I removed the snipped pin-6 [attachment=2]stock_snipped.jpg [/attachment] and added a full length pin back in [attachment=1]remove_pin.jpg [/attachment] and then jumpered pin-6 to pin-5. This accomplishes what the mods outlined in the links above but without making any permanent changes to either the drivers or the board so switching drivers won’t involve any soldering, just a jumper on the driver. I won’t be able to do any testing until next week to see if this actually works. [attachment=0]add_pin.jpg [/attachment]June 4, 2020 at 4:25 pm #1540 jumpered [attachment=0]jumper_pin.jpg [/attachment]June 16, 2020 at 6:54 pm #1541 the mods did not work So I did this. I got 8 pin stackable sockets
plugged the drivers into them
jumped the the pins under the drivers and plugged the drivers into the board
This enabled me to fix the board layout bug without any soldering and has the added benefit of moving the driver into the air stream of the fans…both the top and bottom of the drivers are being cooled now.June 29, 2020 at 1:33 pm #1542
Sorry I missed your post. For some reason I’m not getting notifications. Bloody expensive board you’re whacking in there. I’d be interested to see what your experience with it is. Having used a number of other 32 bit platforms, I’m particularly interest to see if you have any reliability issues, dead pins, USB connectivity and random firmware crashes.July 23, 2020 at 1:59 am #1543 It’s not that expensive, $28 US for the MKS Rumba32. It does have some problems and there’s not a lot of support for it…yet. I’ve had a bear of a time trying to get various firmwares to run. Repetier V2 got it running except the heater kept halting the firmware, never got it printing. Got it running MK4duo but the printer would halt about 15 layers into a print because of a heater fault. Marlin 2.0 would print but I couldn’t level the bed, G29 would lock the printer. The latest Marlin 2.0 bugfix is finally working. I just got it running today, so the tuning/testing starts tomorrow.September 3, 2020 at 11:33 am #1544 Hmmm. Curious about your issues with MK4Duo. I found the firmware pretty good. Just dont like the crappy selection of available touch TFT displays. Got some Nexion thing which was a waste of my life.
Marlin 2 bugfix is the go. Been using ever since.
Super want to try out Repetier 2.September 3, 2020 at 11:36 am #1545
By the way. Should have got a Bigtreetech GTR. SPI and UART drivers – plug and play.
Bloody good board. 6 drivers – has a daughter board which supports another 5 With that, you could easily add full motor bed leveling.January 2, 2021 at 4:51 pm #2171
I changed the motherboard to a the BTT GTR because I was having issues with connecting to the MKS Rumba32 board in DFU mode to upload firmware. I initially had some issues with this when I first installed the board but then it worked fine for months with no problems. Then I started to get a lot of thermal runaway errors (not a board issue) and I was doing a lot of firmware edits to try and sort the thermal issues and at some point I was unable to connect to the board to upload firmware…essentially a bricked board…time to move on.
- You must be logged in to reply to this topic.