tinkergnome 927
12 hours ago, gr5 said:Where did he get the witbox hex file?
Because you asked: "MarlinWitbox.hex" is included in the Cura firmware resources. It's there for ages and the comment says:
==MarlinWitbox== The MarlinWitbox.hex firmware is build from https://github.com/bq/Marlin and released under GPLv3
No more details though 🤷♂️
Recommended Posts
gr5 2,224
Yikes. Where did he get the witbox hex file? Ultimaker firmware is for Ultimaker printers only. It will not work on any other printer - not even clones of ultimaker printers as even the clones are slightly different. Just one change in one pin is enough to keep the display from working.
So... your printer is not exactly bricked - you need the witbox hex file and then you can upload within Cura using a "custom hex file". There are many many other programs that can update the hex file. Any arduino IDE can do it or (better) you can use pronterface. Or stick with Cura - it worked last time - it should work again.
But you need to find the correct hex file that is meant for your exact printer. There may even be a few different versions of your printer with a few different hex files but probably only one.
Contact witbox or google around.
If I misunderstood you and you already used the "correct" witbox file then try using pronterface instead of cura. It's a little more dependable (not a lot). Also try powering up the printer just about the same moment you start the upload. And vary the timing until it works. The arduino inside the witbox is more receptive when it first powers up. That's my experience anyway.
Link to post
Share on other sites