Firmware installation problem
I'm hoping for some help with troubleshooting my RatRig v300.
I have a Pi 4 controlling a BTT Octopus v1.1, running RatOS with klipper.
After good operation for about 18 months I recently had issues where I felt the MCB was failing (motors seemed to loose power) so I got a replacement and decided to update everything. The Pi updated well, and all Ratos modules updated but I can't get the MCB to flash automatically. I've tried SD flash also, but I keep getting back to the 'board detected but unresponsive' message.
I tried the original board again and same thing. Great care taken will all jumpers etc, and the fact that the old board is behaving similar to the new one suggests I'm doing something dumb when I try flashing, rather than it being a hardware issue. I reformatted the SD card fully, got the firmware binary from Mainsail (firmwar-btt-octopus-11.bin) and it turns into FIRMWARE.CUR after my attempts.
Software, firmware is not my strong suit so any suggestions what could be going on would be much appreciated.
#ratos-support
#klipper
#fix-my-printer
8 Replies
you need to flash the board with klipper, not mainsail I believe. When you're running through the ratos configurator and get to the flashing step, there should be a button labeled something like "generate .bin file for sd card". Hit that, get the file, and burn that to the SD card for your mainboard.
Yes, I've tried that as well. Just tried again but same unresponsive message.
And you confirmed the change from .bin to .cur with that file ?
Yes, in all cases so far I get FIRMWARE.CUR after the attempt. I have just tried flashing by DFU (whatever that means) but still get "Octopus V1.1 detected but is unresponsive" 😩 In this instance DFU the firmware was not changed to .cur
Try moving past that step in the configurator. I've had at least one person find that it worked fine in actual use, just that the configurator couldn't "see" it for some reason. I still don't understand why
How do I do that? I can't see how to move past the flash step in the configurator.
off the top of my head, edit the URL to be the next step
That worked! Thanks for your help. I guess the configurator doesn't like my configuration! :chefkiss: