Cannot configure new board
I installed a new Octopus 446 control board and cannot get past the configuration. Wifi is good and I can bring up RatOs, but every time I click on "http://RatOS.local/configure?step=1" I get a 500 internal servor error.:" I flashed the board by SD card successfully, but still get stuck at the above link. Update: Pulled the Pi's SD card and started from scratch. Got the Pi configured fine and in the RatOs confiurator, but again, am stuck at flashing the firmware for the control board. I've tried automatically and manually with an SD card but still the same error that "Klipper doesn't seem to be running in your board...". Tried redoing it with another 446 board and got same results. Also tried with a 429 board and still got the same results. I've been searching trying for a week now with no luck. What am I doing wrong?
17 Replies
If the configurator is saying it isn't running klipper, then it didn't flash using the configurator. Rat-OS expects a particular connection for the board to use, so if you flashed some other klipper firmware it won't work. You must flash it using the configurator dfu or using the compiled firmware on the configurator web page
Just continue onwards, and see if it works. If it detects the board (which it does, in order to fail at checking the version), at least the board is running klipper. There are some issues with the version checking in RatOS 2.0 related to missing c_helper, if klipper is restarted the first time it has an active internet connection, before it finish compiling.
"You must flash it using the configurator dfu or using the compiled firmware on the configurator web page" Yes, I know and that is what I've been doing for the past week. I've tried three cards now, two 446s and a 429. When I try to flash the 446's automatically I get a failure error. When I try to use an SD card, the configurator gives me the same error even though the SD card has changed to CUR. And I have only ever used RATOS on any of these cards.
Does the pi have internet access?
if you get "Klipper doesn't seem to be running in your board..." just continue to mainsail.
Yes, Pi does have internet access. In fact I just downloaded the latest updates to RATOS and Crowsnest and that seems to have unstuck everything. Will let you know in a few hours if it's fixed.
And smack right into another brick wall. Installed the Octopus 1.1 and flashed by DFU. Everything seemed to go fine, but after it finished I got "Octopus v1.1 detected but is unresponsive". The instructions, as usual, are vague as hell so I have no idea what jumpers should be on or off.
Solved.
Besides the misleading "unrensponsive" error report (it's actually not, it's the version checking script that's failing because of missing klipper dependencies - this should be fixed in 2.1), can you elaborate on what you find vague so i can improve it?
Sorry, I didn't see this until just now. The best way to address the "vagueness" is to always start by establishing a frame of reference. IE; instead of just saying "left motor" you need to first establish which side is left. example "The printer's left (standing behind the printer looking at the electronics panel). Now when you say 'left' the reader will always know what you mean.
Second example: When explaining something like the flash sequence, first start by laying out how the board needs to be configured. ie; is the pi plugged in, does it need to be connected to main power, what jumpers need to be in place, etc. Then after the procedure is done, you need to include any clean up instructions (pull this jumper, etc) so that the reader will be correctly oriented for the next step.
Yep, i get this, need a good way to clarify this without having to explicitly mention it everytime. We are consistent with this left/right denomination from the build guide to the software setup, so i assumed it would've been second nature when you get to the point of software configuration. It's a lot of text to add everywhere right/left is mentioned, will think about a good fix for this.
We already do all of this - there's a full step by step explanation on the page where you click "compile" and "flash", and a reminder about what to do afterwards. In 2.1 the jumper information is presented both before and after flashing, since the board won't boot into klipper correctly before a potential boot jumper has been pulled off, so that way you know that's needed before hand.
However the page where you pick the flashing method is currently just a bunch of buttons - that one is terrible and needs a proper design with descriptions of what each options does and when you might want it.
how do i flash my board
tried every thing
klipper does not communicate
You use the configurator, it'll tell you everything you need to do and detect that it's functioning correctly.
It's all in the documentation.
the configurator does not work
I believe you have your own thread, please continue in there (if i misremember, then create a new one). It works unless you break it by asking moonraker to do "Hard recovery".
didnot do hard recovery
Please start your own thread
Explain exactly what you mean by "does not work", include logs and screenshots.