Overriding Nozzzle Prime Start in RatOS macro won't work

Hi, I have a vcore3.1-500 and I use sensorless homing. All is fine except I need the the prime blob to be placed at 0 / 0 - instead it will happen at -7 / -2 Y=-2 is no problem. X=-7 will bump the head against the pysical end the X axis. So set x endstop to -7 with [stepper_x] dir_pin: x_dir_pin # Add ! in front of pin name to reverse X stepper direction rotation_distance: 40 # 40 for 20 tooth 2GT pulleys, 32 for 16 tooth 2GT pulleys position_endstop: -7 # Adjust this to your setup this will place the blob left of the build plate. The bolob won't work reliably this way so I tried to override the xy position of the blob with: variable_nozzle_priming: "primeblob" variable_nozzle_prime_start_x: 3 variable_nozzle_prime_start_y: 0 While the config recognizes changes to the variable_nozzle_priming it will ignore variable_nozzle_prime_start_x - x will remain -7. What am I doing wrong? Thanks in advance!
4 Replies
beejayf
beejayfOP•2y ago
Am I the only one to notice the override has no effect or am I the first to try to override? 🤔
blacksmithforlife
blacksmithforlife•2y ago
@miklschmidt maybe you can help
miklschmidt
miklschmidt•2y ago
i'm currently using this myself so i know it works. Can you post your printer.cfg? PAM also uses it actually But PAM also overrides the prime macro's so.. 😄 Oh i know what's wrong. Was just reading through your post again and noticed how you claimed the default was to put it at -7 if position_min is -7. First of all, it would be -2 (it adds 5). Second of all, RatOS v2 puts "min" at 5. Third, you're on RatOS v1 and reading the docs for RatOS v2. v1 doesn't have those primeline variables. You can choose the docs version from the dropdown in the top right of the docs page 🙂
beejayf
beejayfOP•2y ago
Hmmm... I might have drifted off to some V2 documentation there. Thanks!
Want results from more Discord servers?
Add your server