RatOS-v2.1.0-RC2 How do I set configuration that is not included in the "Configurator"?
I just upgraded to the latest pre-release. I went through the Configurator. I have a handful of configurations I need to set. Things like neopixel, beacon y offset, adding additional temperature sensors, additional fan control, fan kick start time, etc.
I'm wondering, what is the prescribed method for these things?
I'd happily read the docs if they exist; it seems like the os.ratrig.com/docs is mainly 2.0? I realize this is a pre-release; I'm just trying to be self-sufficient and would gladly read the docs if they exist.
19 Replies
I assume the answer is updating the
printer.cfg as we did previously?
For some reason as soon as I add my neopixel config:
I get "Lost communication with MCU 'mcu'"
Maybe I'm missing some other configuration that I don't remember previously setting up. I assume this:
Correct, add your custom stuff to printer.cfg.
I had started updating my printer.cfg with adding just the neopixel section from my previous config. This immediately broke, which led me to ask here.
I'll go back through the neopixel documentation which seems to be here: https://www.klipper3d.org/Config_Reference.html?h=temper#neopixel
2.1 isn't released yet, it and the documentation continues to be worked on.
Is the documentation that is being worked on somewhere like in a branch in GitHub?
Honestly not sure
Looks like maybe here. Branch is
2.1.x and there is a docs folder. https://github.com/Rat-OS/RatOS/tree/v2.1.x/site/docsGitHub
RatOS/site/docs at v2.1.x · Rat-OS/RatOS
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Rat-OS/RatOS
Would be nice if there was an option on the https://os.ratrig.com/docs for
2.1.x with something at the top denoting that the docs are not complete.
Something super weird is going on. When I leave color_order to default (GRB) at a chain_length of 30 things work fine; but if I increase the chain_length by too much or switch color_order to GRBW, I just into an error saying Lost communication with MCU 'mcu'. This previously worked fine before I upgraded from RatOS v1.x.
I just realized I left the power supply for the control board off. I wasn't wanting to listen to the part cooling fan during setup. Oof.womp womp
No the pi is already configured, you don't need this
"lost communication" is when the connection is lost after it has already been established. It's a loose connection (or electrical issues).
I just into an error saying Lost communication with MCU 'mcu'Well that's interesting.
This previously worked fine before I upgraded from RatOS v1.x.Might have been an error introduced in klipper. I don't know. I believe chain_count (there's no chain_length) is limited to 32 in klipper though
I remembered wrong 😂
Ah .. my memory was just outdated by 4 years, and it was 18 😄 https://github.com/Klipper3d/klipper/commit/2bb30265b513269f5e749f87a424bf6772f7fc11
lol
I was also having an issue with one z motor, turns out the connector wasn't fully plugged in. I'm guessing it has wiggled some over time. Things seem better now. I'm currently running through
BEACON_RATOS_CALIBRATE.
I'm also super happy to see that with these new RatOS changes, things seem to be backward compatible. I've been adjusting my z on almost every print, so I'm hoping Beacon Contact will help.
Also is this all I need to set to adjust the y offset for the Beacon? Previously I had to also set the serial property and I also had mesh_main_direction and mesh_runs.
Yep that's it. On a v-core 3 you still want to change the bed mesh and z_tilt settings however, as that didn't ship with the beacon as default. Currently can't automate bed_mesh min/max, z_tilt points or printer limits as we don't have enough info about whatever toolhead design (and associated mods) you may be using.
Good to know, thanks for the information.
With Beacon Contact needing to have a clean nozzle to work correctly, is it going to become common to have some way or automating cleaning the nozzle on RatRigs? I've seen stationary wire brush and servo + wire brush solutioin on other machines, I assume something like this is needed?
I guess I'm seeing an explanation that there is a wipe that occurs at some point that should clean the tip before the step that needs it removed (calibration?). Seems like that should be in the documentation, I have a feeling I'm not the only person that will be worried about it and if it is already handled, some clear documentation would ease the nerves.