VAOC T1 x not lining up
I'm stuck. I line the two tool heads up in the VAOC config but then when it comes time to calibrate the z offsets T1 on the x doesn't line up with the probe. It's about 10mm off on the x. When I try to start over I get "Error evaluating 'gcode_macro _VAOC_CALIBRATE_TEMP_OFFSET:gcode': gcode.CommandError: Unexpected VAOC y-control point detected! Please run '_VAOC_RESET' to roll back to default values"
Also when I start the config the gantry hits the back of the machine. I think it's about 1mm off
33 Replies
please post a debug zip
So I figured it out but leaving the post up for others. You can change the y control point under Ratrig varables. When the gantry was hitting the back it was moving the heads out of alignment. I think Ratrig should change the default y control point to something lower
It's set to 533 on the 500, I changed it to 531
When the gantry was hitting the back it was moving the heads out of alignmentThis seems like a problematic y endstop installation or no endstop limits calibration. the y control point won't be your only issue y-control point on all v-core 4's is size + 30.5 btw Not 533, but 530.5 on a 500.
the controlpoint variables change when you align the nozzle in VAOC.
So you set it to 533 yourself
Maybe I messed something up on my first try and it registered it 533 in the ratos_varables. Where the saved varables section you just posted
You wold think it would go back to default when doing a VAOC_reset
VAOC reset?
You're changing the values saved to disk. The defaults are no longer there when you've told it where your nozzle is (by dragging the picture).
AFAIK there's no "reset".
it was in an error message so I did _VAOC_RESET
I see it in your message now, missed that part.. It doesn't exist in the code, did you get another error when you ran that?
@Helge Keck Are we supposed to have a
_VAOC_RESET?I kept getting that message and couldn't try again until I sent that command
Jesus.. i was looking in the wrong codebase 😂
I see what's going on now
And they're only set when you run _VAOC_RESET
mystery solved, it seems to be working now
Removing those variables from the static config and putting the into the configurator so they'll always have the correct values.
where do I find the static config? Is that the file that says ratos_varables
GitHub
GitHub - Rat-OS/RatOS-configuration: The RatOS modular klipper conf...
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
the configurator dynamically renders
RatOS.cfg and ratos_variables.cfg (and others)Thanks, found it
And by "remove" (typo) i meant "removing" as in "i'm removing"
You don't need to do anything 🙂
Other than update
Just pushed the fixes
I did the update and the first thiing I got was this " Error evaluating 'gcode_macro _START_VAOC:gcode': gcode.CommandError: Unexpected VAOC x-control point detected! Please run '_VAOC_RESET' to roll back to default values."
Did you update the configurator as well?
It takes a few minutes to compile
so you may have been a tiny bit too fast 😅
I'll do that now, thanks
yes, why?
I did the updates and now I'm getting this "Option 'gcode' in section 'gcode_macro VAOC' must be specified"
I found out i was just being a dumb dumb and looking in the wrong repository 😂
omg
sec
Hmmm.
Can you post a debug zip please?
ah it's _VAOC :facepalm:
@spacebaby0695 update compiling, ready in 10. Sorry, that was stupid... again 😂
You're doing a lot, it happens
Seems to be working again, thanks
I am also getting this error now, what was the fix?
Solution
update everything, run _VAOC_RESET again.
then redo VAOC calibration
Ok that worked, thank you! And when I have them on target I just exit?
you click the stop button on the top left
Perfect thank you! Looking forward to my first print