Rat Rig Community [Unofficial]

RRC

Rat Rig Community [Unofficial]

Join the community to ask questions about Rat Rig Community [Unofficial] and get answers from other members.

Join

ratos-support

fix-my-print

fix-my-printer

fix-my-resonance

fix-my-mesh

german-support

mcu 'beacon': Unable to connect

Im getting the mcu 'beacon': Unable to connect issue and im not sure if im missing a step but i am running ratos 2.1 and the beacon version says 2. I am upgrading from a v3 to a v4 and previously this worked fine. also it seems that in the devices menu that the beacon is the only usb device not recognized that is connected to the pi...

GuessWhatsThisParlor Error

Posting conversation here

NikoMan update issue

@Niko_Man Im going to move it to here so we can better keep track of the convo :) im pasting it below
Solution:
Hi I was able to finally ssh in and ran ratos doctor, it is better no packages show need of update but this is error keeps coming up, even though I have entered the "unsupported slicer" line to the printer.cfg Post-processing Error: slicer version not supported You can allow unsupported slicers by adding the following to printer.cfg. [ratos]...

toolhead variable_standby on print start T1 toolchange does not wait for T0

Just found out that when I use variable_standby for both T0 and T1 and variable_toolchange_standby_temp and start the print with T1, then ratos does not wait on toolchange for the heatup of T0 but throws the min_extrude_temp error (bot at the same second):
No description

Print Fail during beacon calibration after update - bug?

I'm running a Vcore 3.1 300 and upgraded from 2.0.2 to 2.1 RC 3 this past week. @miklschmidt Posted an update 3 days ago to Git. I updated the RatOS first. I had already been working on some first layer issues with beacon contact, and believed an update may flush out some of the bugs I was hitting. These first layer gcode files were produced and did print after the RatOS updates, where I did encounter some OS issues and notifications in that print via klipper screen, but couldn't catch them on the screen since I was so closely watching the first layer performance and beacon probe sequences. Those didn't occur frequently, and I only had to print about 5 first layer prints before was able to move forward....
No description

How do i fix this?

SAVE_CONFIG CORRPUT
Solution:
try deleting lines 129-134
No description

Warnings after updating and restarting

After updating i got all these warning for moonraker should i just dismis them ?
No description

RatOS missing from Software Updates

I turned my printer on today and got the notification bell that software updates were available. Following the link, there were ratos-configurator, mainsail, beacon and OS Packages indicating update available. I always check if RatOS needs updating before the configurator and do that first, however it isn't in the list of packages anymore. I went ahead and updated all the packages, starting with ratos-configurator, in the hope it would kick RatOS to reappear, but it hasn't. Any advice? Consider...
Solution:
Check #announcements , but yeah with rc3 the ratos package was merged into the configurator package. Your system is normal. And if everything else is working, no changes are needed.
No description

Sensorless ENDSTOP problem

I’m trying to use sensorless endstop on T0 and T1. On T0 I get the option to use sensorless but on T1 the option doesn’t show up. This is because my endstop of T1 broke, and I need my machine to be running but ratrig is taking too long to ship my endstop. ...
No description

RPICamv2 doesn't start as an VAOC cam.

Hi, i've did everything according to the information that i've found in this discord channel/available documentation , but i'm having troubles with VAOC, camera basically doesn't start as a VAOC cam, but is available in Webcam section without any issues. Ratos V2.1-rc2 It would be great if someone could support me in that issue. Adding crowsnest config in the attachment....
No description

Notifications integration in RatOS >= v2.1 - telegram-bot, Pushover, MQTT?

I've been looking for a way to have notifications sent from my printer. I've been using OctoPrint for my Ender 3 Pro for years, and have acclimated to the abilities. In that same sense, as I've been looking for more options for my VCore 3.1 300 that I just upgraded to RatOS 2.1 RC3, I noticed that KIAUH support has been removed (temporarily???). To that, telegram-bot, Octoprint, Pushover, or any g-code shell command interfaces, etc. are no longer available for a more daring hobbyist to utilize on thier printer.
My intent is to send a notification for when the printer is paused so I can change filament. I am currently building an ERCF (may actually switch over to a BoxTurtle), but all filament swaps are akin to sneakernet checking when an internet/text message would be more appreciated from any of my printers. What then, are the plans for KIAUH support to enable other Klipper add-ons? ...

RatOS for Raspberry Pi5 ?

I have a working Ratos/rPi/Klipper running on a rPi 4.
I plan to replace the rPi 4 with a new rPi 5 8GB The printer is a VCore3.1 I went to https://github.com/Rat-OS/RatOS/releases and downloaded the latest (2024-07-27 RatOS-v2.10-RC2) image file.
The file was '2024-07-27-RatOS-2.1.0-RC2-raspberry-rpi32.img.xz'...
Solution:

IDEX input shaper values not being set correctly

I had a heck of a time getting decent print quality out of my IDEX 500. It turns out that the input shaper values I set don't get applied on the toolhead switch. It's looking for a variable in the RatOS macro. I had to add the following lines to my printer.cfg in the RatOS macro: variable_shaper_x_freq: [52.2, 48, 52.2, 52.2] variable_shaper_y_freq: [42.6, 38.2, 42.6, 42.6] ...

My control interface stopped responding and simply exited the window!

Hi! i have a major problem. My control interface stopped responding and simply exited the window, however my print is still going, apparently whit the loss of all speed overrides inputted through the interface. All reconnection attempts failed! Did any of you met something like this before?

pin PC4 used multiple times in config

Hello, I have switched from 2209 drivers (selected in the inital RatOS configuration) to 5160 drivers. So I have added ...

Print stopping at lay 451 with move out of Range

vcore 4 400 IDEX setup Hello i am receiving a "Move out of range:459.804 227.625 92.395 [10419.313] added my slice that was presented on RatOS along with my config file and my ratos config. Unfortunately i dont have a debug file since i had shutdown my printer last night and didnt know to save it until earlier today where i spent hours trying to figure out to fix my issue....

No variable_adaptive_mesh in printer.cfg?

Hey, folks. Im missing the command for adaptive mesh on my printer.cfg (attached) Any help is greatly appreciated. Thanks...

Pin 'heater_bed_sensor_pin' is not a valid pin name on mcu 'mcu'

Hello, I have set up the RatOS for a Minion in the configurator and now I am changing the printer.cfg. RatOS.cfg is unchanged. I am not sure what causes the above error. ...

Configuration Bug Einsy

Hello, I tried to configure an old Einsy board for Klipper. I've done the bootloader stuff, and it worked out. Upon starting the Ratos Configuration, the first issue, though a minor one, was Ratos not being able to query the board successfully, but since the usb-connection is known to work, and you can skip this, I didnt give it much thought. During the printer configuration, I specced a basically standard mk3, except for a triangle labs bmg 3:1 extruder. For the part cooling and hotend fans I chose Input voltage pwm. When I wanted to complete the setup, it threw an error, that i can't circumvent. Changing the board settings to digital pwm for testing did nothing. It's worth mentioning, that I also got an error, when I tried to set X and Y Accelerometer to "none", however switching to host connected accelerometer solved that issue for now. I did WinSCP into the pi to see if the Pins are specced in the configfile, and there was a set pin for the fan. ...
No description

Nozzle expansion offset gets reset by an order of magnitude at the start of a print. VC4/500

I've gone through all the Beacon calibration and it comes back with a sane number. (e.g. T0 expansion coefficient 0.069375) and then when starting a print the Z offset will be wildly off either + or - by millimeters. So the prime blob will start in mid air, or in this case, it drove the nozzle into the textured PEI and the extruder was clicking because it was trying to extrude inside the PEI surface. I haven't tried setting the expansion to false yet. ...
Solution:
Doing the double "SAVE_Z_OFFSET" in the console while the print was going actually seems to have worked.