Section 'ratos_homing' is not a valid config section
Installed on laptop, not pi. Copied the the config files from the github, working my way through errors Klipper is reporting. This one seems to have a lot of the same answer when googling, "Run the ratos configurator to fix the symlinks" but I am not finding what files aren't being symlinked correctly nor where they are/should be.
13 Replies
Wish klipper would report what it didn't like about the section, not just that it was invalid but oh well 😄
As I mentioned in #ratos-development you can't just copy the Rat-OS directory. You need to follow each module's install script. You probably never ran it so you probably need to do https://github.com/Rat-OS/RatOS/blob/v2.x/src/modules/ratos/start_chroot_script#L40
GitHub
RatOS/src/modules/ratos/start_chroot_script at v2.x · Rat-OS/RatOS
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Rat-OS/RatOS
Do those modules edit the cfg files?
Sorry, I may not be asking the right questions. I can figure out pins and the nested includes, but I'm unclear on what those modules are actually doing
I'll look at those scripts and try to figure it out, thanks
I didn't copy the ratos directory, just the ratos-configuration as I figured I could get by with just the config part as I was able to flash the MCU just fine. I have the two talking, and home on X and Y, but had to comment out the
ratos-homing line in printer.cfg to get that far
Like, I don't think I care about the configurator at this point? But that's naive
Looking at the setup.sh script referenced on L40 it only seems to install the configurator service and logrotatorThose modules are what install and configure the Rat-OS image. There are interdependencies so you can't just take certain things
I would recommend understanding all the steps that happen when the Rat-OS image is built, follow them step by step yourself on that laptop. Then after understanding all the different pieces, you will understand what parts you can skip over
disappointing, but understandable. I'll update this thread if I make any progress 🙂
I mean, it's pretty easy. You go in order(left to right) of modules as defined in https://github.com/Rat-OS/RatOS/blob/v2.x/config/raspberry/default#L9
Then find the module in https://github.com/Rat-OS/RatOS/tree/v2.x/src/modules and then run the same commands as in the start and end scripts
GitHub
RatOS/src/modules at v2.x · Rat-OS/RatOS
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Rat-OS/RatOS
GitHub
RatOS/config/raspberry/default at v2.x · Rat-OS/RatOS
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Rat-OS/RatOS
I looked at.that last night and didn't find the very first.module.on the line 'base'.
Realized this isn't where I want to spend my brain power learning and ordered a pi.
Yeah easiest is to use supported hardware
Yeah. Figured I could bypass a few things, but as it is becoming more difficult decided to buy my way out and spend my (and yours!) time wiser 😄
If the module isn't in RatOS, it's a native CustomPiOS module
The configurator keeps track of klippy extras and moonraker plugins, plugins are registered with the configurator during the custompios image compilation.
ratos_homing is a klippy extra
ahhh, i was theorizing that ratos-homing needed registered due to its section not having
gcode_macro in the section name. Glad to hear that confirmed 😄Yeah the section name would've been
gcode_macro ratos_homing in that case