RatOS initial setup and configuration
I followed the steps for initial configuration and after that, I am getting an error. Since there isn’t much information about the troubleshooting, I hope to find the solution here. Where do I start?
117 Replies
which ratos version? upload your printer.cfg please
Sorry I will be able to provide this info next week, I am out of country.
RatOS-v2.1.0-RC2, latest one.
Can you upload your RatOS.cfg then please
which octopus board do you have? Did it flash correctly in the configurator?
Octopus V1.1. In the configurator it says that it is F446 or something like that. At first I was getting an error that mainboard firmware does not match, and the difference was the last letter in the code. I have reflashed the firmware but the same error was allways there. Same issue with toolbard firmware mismatch.
have you updated ratos? That issue has been fixed
I have followed the installation giude https://os.ratrig.com/docs/installation , the last thing I did is "prepare your control board" and then I followed the configuration process via the web interface. After that, I got the errors. Did I miss something about the RatOS update?
Installing RatOS | RatOS
Raspberry Pi Installation
And I have updated all the files through the "machine" tab and "update manager"
Not sure if I have updated the RatOS package first, as it states in the online guide. Could this be the case?
that documentation is for 2.0. But you are using 2.1. Mikel is still working on the new documentation
Is there a guide for 2.1? How other people are installing all the firmware and etc. for their Vcore 4 hybrids?
I also used the 2.0 guide and had the same error with the version at the beginning. But it disappeared after the update. I would advise you to do it again from the beginning. did you set up the internet connection on the pi before flashing? i just saw the warning in the instructions.
Yeah I did set up the internet connection on the pi before flashing. It also disappeared for me, but I have other errors now 😄
What errors do you have now?
As soon as you flash everything do an update. There has been some updates pushed that will elminate the errors. Don't try to fix them manually in the software.
this is the first one.
Another one is something with beacon probe
The configurator will never tell you what board do you have. That info is always introduced by user, board type can not be detected by the system.
Check the board processor for the model numbers.
My flow is always flash a new card, setup wifi, open the webUI, update everything (always starting with RatOS and then the others) and last run the configurator.
That's exactly what I did. So to start over, I should format the SD card and do it all again?
well, I am not really sure if I have updated RatOS first, or everything all together
Easier to start clean…
What RatOS-*.img.xz file version should I use? 2.0 or 2.1 RC1?
well not 2.1 RC1 as that is really old and latest is RC3 (https://github.com/Rat-OS/RatOS/releases/tag/v2.1.0-RC3).
but 2.0 vs 2.1 - 2.1 still needs the documentation updated and published but has a lot more features and is required if you have a vcore4. 2.0 is still the last official full release
I have a vcore4. Basically it should be like this - I flash the RatOS image into micro sd card > insert it into raspberry > connect to the raspberry via wifi in my case > go through the setup page > update the RatOS in the update configurator > then update all other files?
Or what do I do with the RC3 zip file?
Do I miss something or people who purchased vcore4 hybrids somehow install all the firmware by themselves? 😄 I do not see any step by step tutorials
this is what I get
How do I know what version EBB Toolboard I have?
Same with toolboard
I have purchased a whole kit that RatRig suggest with hopes that it will be easier to set it up. Is it that hard for RatRig to prepare a normal guide?
I have also noticed that there are no files on the mainboard sd card after the installation process. Is this normal?
the octopus SD card?
yes
how are you checking for files on the SD card?
I take out the sd card and insert it on laptop.
I assume windows - do you have your computer setup to show hidden files and file extensions?
Yes. I am not sure if I do everything in the correct order. I do flash the firmware in the "setup wizard". After the setup wizard I go to the machine update manager, update the RatOS in the first place and everything else after that
What does this message means?
if you are using the SD for flashing, after a successful flash it should change the filename from FIRMWARE.bin to FIRMWARE.cur
I am flashing the firmware automatically, not with SD. Would you mind write a short step by step guide what has to be done and in what order? So I can compare with what I have done and what could possibly be wrong?
the configurator should step you through everything
Yeah but something is clearly not okay 😄 Do you have an idea what can cause these two errors?
and how to fix it
well, we haven't gotten past flashing the boards yet, so that needs to be fixed before klipper can talk to them
Just to make sure - I can identify the octopus board type by the numbers written on the microcontroller? It’s written stm32f446. But how can I tell if it’s Pro or 1.1? I assume it’s 1.1 because it looks like that in a photos 😄
the board silkscreen will say what board it is and version
Update before going through setup page, but otherwise yes.
This is an old bug that would be fixed if you updated
RatOS can not be updated. Update manager shows that there is an update from 2.1 RC2 to RC3, but it can not complete the update
Okay. silly question - do I need to insert the micro SD card into the octopus board or not? I am asking because it does not contain any files after the setup.
Also, I am doing all the firmware flashing thing with all the wiring done. Could this be an issue? I have seen that it's recommended to flash everything while all the wires are disconnected, except raspberry.
but it can not complete the updateWhat does that mean?
Screenshot attached. progress failed
God damnit, i think this happens because the RatOS image generation via custompios clones the repository with all branches when it shouldn't, gotta find i fix for that, that's an actual bug. Only one way to fix this, in the update manager run
hard recovery (the one i always tell you to avoid 😂) then SSH in and run the update script like this:
Now you should be updated and ready to go 🙂Okay, so I have set up the wifi via raspberry, updated the RatOS to the 2.1 RC3, but I still get the firmware incompatibility error during the setup wizard while flashing the firmware
You need to update everything, the configurator as well
This is still old code
Am I using the correct image file?
Yes, there's a newer one you can try that has much never code baked in, gimme a sec.
https://github.com/Rat-OS/RatOS/actions/runs/11301673501
this also contains a potential OS performance fix.
GitHub
Performance: isolate cpu 3 and pin klipper to it · Rat-OS/RatOS@50a...
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Performance: isolate cpu 3 and pin klipper to it · Rat-OS/RatOS@50ab37e
Okay, so I have flashed the image into the micro SD, I have set up the wifi, I have updated the RatOS, have updated the ratos configurator (everything else is up to date). Now I can go to the "configurator" and "setup wizard"?
yessir!
Now I have the same firmware mismatch, but this time the difference between firmwares as not the last digit/letter, but the whole code is different
Shall I just flash the firmware again?
Okay that helped
But this time I have the raspberry and octopus on the table (I took it out of the printer and disconnected all wires). Shall I skip the toolboard flashing step? Since it is not connected
Yep, newer klipper because you didn't update the last one 🙂
yes (this was for the "shall i just flash the firmware again", stupid widescreen made me misclick 😂
Doesn't matter 🙂 you can't flash it without connecting it obviously 🙂
So after I place the raspberry and octopus back in the printer and wire it all up, I will have to repeat the setup wizard in order to flash the toolboard, yes? Sorry for such a dumb questions, I have 0 experience with octopus and klipper things 😄
Yes 🙂 All good my man!
Okay, so the setup wizard then through without errors, but once I go to the mainsail after the setup wizard, I see this:
Click firmware restart
Or just wait, (this happens when klipper is starting up, can take some seconds)
Okay, klipper startup error is gone, but here is the second one:
Is your beacon connected?
no. So now I should wire everything up and see what's next? 😄
Yes
I have plugged in the beacon usb to the USB2.0 on the raspberry - same error:
Okay, problem solved for now
Looks like it works, thank you 🙂
Okay - I have turned on the printer, moved the toolhead a bit, and I got some errors about all the drivers (x,y,y1,y2,z0,z1,z2) and the printer restarted. All drivers are very very hot. What did I do wrong?
Enabled performance mode and forgot the driver cooling i assume?
i would appreciate it if you posted the actual errors
I did not place the electronics cover with a fan at the moment, so yeah, there were no cooling. Do I have to choose one of 3 modes? If yes, which one is the safe one?
I did not have time to make a screenshot, I have turned off the printer asap 😄
If you’re talking about the motion section, no those are features, you can enable/disable each of those individually. Read the description for what they do.
That’s what logs are for, also please don’t just cut power, your raspberry pi should be properly shut down to not cause filesystem corruption
When you get an error all steppers and heaters are disabled, so no reason to panic
which log should I download in order to see the errors?
Debug zip from the configurator contains everything. In this case klippy.log.
Ok, I will keep that in mind. Controller fan does not work. I have configured it to be allways on, jumper is on 24 V, 3rd slot from the bottom (as per instructions).
And what is this:
and this one
Multiple people have noticed this, it doesn't seem to cause any actual problems, i'm not sure why they've started appearing. Probably some new klipper "feature" that confuses more people than it helps.
okay, What macros do I have to do now?
What do you mean?
to calibrate everything. I see there are macros for beacon calibration and etc. Should I run all of them?
and how to do a tilt calibration?
Follow the rat rig comissioning guide 🙂
happens automatically when you print. Outside of a print you can do it with the z tilt button in the toolhead panel, or by issuing
Z_TILT_ADJUSTI have done an initial beacon calibration. It says that bed should stop in distance of about 10 mm. But in my case nozzle touched the bed
How do I shut down the printer properly?
mainsail, top right corner menu
initial beacon calibration uses contact
Is it possible to use beacon contact all the time? I want to place a glass bed on the aluminum, but it's 5 mm in thickness and I assume that nozzle will crash into the glass
https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/beacon_contact.md
GitHub
RatOS/site/docs/configuration/beacon_contact.md at documentation_v2...
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - HelgeKeck/RatOS
specifically under the "RatOS configuration" section
you can enable contact for homing, bed meshing and z_tilting
that should cover everything (if you enable all of those)
I think you're the first one to use a glass bed in here though, so be careful.
Hello! I don't really understand where should I put that text block copied from your link. It says in "printer.cfg", but does it matter where exactly?
there's alrady a [gcode_macro RatOS] block, either put it there or add a new one at the end.
Also you only need the specific parameters you're interested in
Don't copy the entire thing
like this?:
Yessir
should I perform an initial beacon calibration again?
I have saved the config file, but it still does bed mesh with scanning, not contact
okay I see that in beacon.cfg file these values has not changed. I am starting to get better with RatOS and klipper 😄 I can change these values in "beacon.cfg" file?
I have tried to perform a hotend PID tuning but got an error. Could this be something else than broken wire?:
No everything is done in printer.cfg, klipper merges all included files in order, section and parameters that appear last take precedence
How are you testing?
Broken wire / bad wiring or bad thermistor configuration
I just ran a bed mesh.
Thermistor is working, it shows the room temperature and if I heat up the bed while nozzle is near the bed, thermistor shows increase in temp. Heater has continuity, I checked it with multimeter. I think it's something with config. If I try to heat up the nozzle, temp readings does not change for a few seconds and then printer shuts down.
yeah that doesn't do it, only the mesh created in start_print
if you're running it manually you need to run
BED_MESH_CALIBRATE PROBE_METHOD=contact USE_CONTACT_AREA=1
Did you plug it in correctly?
Unless you changed the config or selected the wrong board etc, the config isn't wrong,
You can send a debug-zip and i can checkYeah I will send the debug-zip shortly. I did another test - I turned on nozzle heating and tried to measure voltage on the toolboard heater pinout with multimeter - it shows 0.00 V while "heating"
Here it is
There are too many points to probe. How can I lower the number of points?
This stuff is all documented in the klipper config reference (there's a link to that in the top bar when you edit a config file in mainsail)
Nothing seems to work what I change in printer.cfg file. I have inserted "[bed_mesh] probe_count: 15,15" there, saved the config file, send a command "BED_MESH_CALIBRATE PROBE_METHOD=contact USE_CONTACT_AREA=1" and it is still measuring 224 points
15 x 15 = 225
lower to your liking
probe_count: 15,15 means 15 points in X and 15 points in Y.
the defaults for beacon are much higher (because scan takes seconds to complete). 20x20 for 300, 30x30 for 400 and 40x40 for 500.
Is there a particular reason you insisted on glass? It's very old school.I haven’t found anything better and more reliable. Flex plates are nightmare.
What would you recommend? 😄
Based on my experience, magnetic flexplates can not hold large prints. Parts warp and lift the flexplate up.
Even small parts on Prusa printers are never flat.
maybe you had time to check the debug-zip? I think it's something with config or toolboard. I measured 0 voltage while the heater was turned on.
Powder coated PEI, unless your print nylon. In that case there's always Dimafix.
Parts warp and lift the flexplate up.The flex plate isn't the problem, the warping is. Higher chamber temp and/or less cooling is the only actual fix for that. Alternatively, get carbon fibre or glass fibre filled filaments, the fibres significantly reduce warping. The ones used on RR printers are a quite strong, if you're lifting those up, you've got print problems not flex plate problems Which heater are we talking about, bed or hotend? You're mentioning your toolboard so i'm assuming your hotend. Show me how you connected it. @armearme. you picked the ebb42 1.1, that's probably a mistake and why it doesn't work If you got it from the kit, it's a 1.2 the 1.1 is a fire hazard
yeah it's hotend heater.
I purchased kit. Are there any physical differences between 1.1 and 1.2? I know it's written on the side that is not visible unless I will unplug everything and remove the toolboard
yes the pins are different 😄
You don't have a 1.1 if you bought the kit
It's a 1.2
Use the configurator to flash it properly as EBB 42 1.2
Rat Rig has never and will never sell the 1.1
F me... You are right. I need to be more respective to details. Do you have a patreon or something? 😄
Why is there even an option to flash ebb 1.1 board 😄
There are details in my profile 🙂
because we support a ton of boards, not just what's default on RR printers 🙂
i believe we're close to 50 different boards at this point
If I’m stuck here also after flashing again, can I try something other?
Yes. If you're having problems please open a new thread (this is unrelated to the original question in this thread)