Settings locations and priorities / hierarchy / overrides?
I have a RatRig V-Core 3 running RatOS on a raspberry pi and I use superslicer. Is there a diagram or chart that lists all the places that settings can be adjusted along with which ones override which. This includes the settings in superslicer and printer.cfg as well as all the other config/macro files. I am always wondering where I should make changes to various settings/configuration and questioning if they're being overridden somewhere else. One example, if I want to change PA for a new filament, and I change it in RatOS, does this override everything else? I think it's also set in my printer.cfg, my start G-Code in superslicer, maybe elsewhere too?
3 Replies
In order of precedence it goes:
Slicer > Printer.cfg > RatOS defaults
Things that can change from print to print (ie, things that are dependent on filament or the object that's printed) should go in the slicer. Things that are characteristics of the printer and should be the same on every print goes into printer.cfg (USER OVERRIDES is your friend).
List of macro variables: https://os.ratrig.com/docs/configuration/macros
Configuring RatOS Macros | RatOS
RatOS comes with a bunch of flexible predefined macro's that can be customized via variables and macro hooks.
Accelerations set in your slicer (results in M204) will override whatever is set in your printer.cfg. Max_velocity on the other hand is a hard limit that can only be overriden via SET_VELOCITY_LIMIT (see klipper gcodes documentation)
"Printer limits" in the slicer does nothing.
(not the slicers job)
Thanks, that's very helpful. When talking about RatOS, the UI has many settings that can be adjusted during the print. Many of them clearly override the slicer settings, e.g. temperatures, speeds. Is this true for all settings, like PA, and retraction? What if I set those values in the UI prior to starting a print? Will they still override the slicer settings, or do they take on the slicer values at the start of a new print? The speed multiplier seems to persist it's override between prints.