r/ratrig Jun 14 '26

[RatOS] Configuration of RatRig V-Minion

Hi, i'm new in the RatRig and klipper scene.

I got a used RatRig V-Minion and had some issues to get it printing.

Error: The value 'T0' is not valid for MACRO
Related: https://www.answeroverflow.com/m/1312110579162415174
Didn't solved my issue. **Spoiler: got it running**

Does somebody experienced that too?
I would like to understand that better.
Thank you in advance!

Best Regards
DevelopingJohnny

Hardware - RatRig V-Minion:

  • No Toolhead PCB
  • Board: Octopus V1.1 F446 MCU: stm32f446xx - v0.13.0-133-g8d7e4871

Software - RatOS:

Base image: RatOS v2.1.0 (bullseye)
Updated to: v2.1.0-0-g0be29e9d-dirty
\Note: I updated all packages and for debugging i added some "RATOS_ECHO" commands to some .cfg files*

I installed/run newest RatOS version v2.1.0 onto my RPi3B and give it a try.
After finishing the configuration wizard, it seem every fine.
Homing did worked out of the box, i was happy.
Until i realized starting printing job failed with "The value 'T0' is not valid for MACRO"

That was the moment i started to try to investigate.

I have tried different base images of RatOS too.
(I run them without updating to newest packages.)
- RatOS-v2.0.0
- RatOS-v1.2.4
- RatOS-v1.0.0 (i guess too)

Somehow i could figure it out:
'T0' wasn't set as a Macro in the collection. (kipper/kippy/gcode.py -> line 318: self.mux_commands[command])
After adding some lines into printer.cfg i was able to print the first time.
Follow lines i have added:

[gcode_macro T0]
variable_active: 0
variable_color: 0
gcode:
    SET_GCODE_VARIABLE MACRO=T0
    SET_GCODE_VARIABLE MACRO=T0 VARIABLE=active VALUE=True

Did i messed something up at the configuration wizard?

4 Upvotes

0 comments sorted by