Cant get RatOS working on a Voron2.4 with Euclid Probe to Set Z height
I recently bought a used Voron 2.4 that had a Spider 3.0 board. My main printer is a Vcore3.1 running RatOS and I love the configuration and Software updates that go with it.
Since the Spider 3.0 is not supported by RatOS, I decided to purchase an Octopus Pro 446 to put in the Voron and set it up with RatOS.
I have most everything working; motors, fans, heaters, temp probes, end stops, etc; but I am stuck and having problems with setting the Z height and getting the Euclid probe to work. Whenever I try to home the Z axis, it first tries to do something the Euclid probe and then errors out when it doesn't see the probe. This might be the right procedure with a VCore but on a Voron there should be no interaction with the Euclid probe until the Z height is set as the gantry and the probe do not start on the same Z level. I know that there is a slim chance that someone else has the same configuration but could someone explain to me how I can disconnect the homing of the Z axis from interacting with the Euclid probe
Since the Spider 3.0 is not supported by RatOS, I decided to purchase an Octopus Pro 446 to put in the Voron and set it up with RatOS.
I have most everything working; motors, fans, heaters, temp probes, end stops, etc; but I am stuck and having problems with setting the Z height and getting the Euclid probe to work. Whenever I try to home the Z axis, it first tries to do something the Euclid probe and then errors out when it doesn't see the probe. This might be the right procedure with a VCore but on a Voron there should be no interaction with the Euclid probe until the Z height is set as the gantry and the probe do not start on the same Z level. I know that there is a slim chance that someone else has the same configuration but could someone explain to me how I can disconnect the homing of the Z axis from interacting with the Euclid probe
8 Replies
There's unfortunately not an easy solution to this, it requires modifying some fundemental homing logic in RatOS. RatOS has sort of poor support for homing with a z-endstop instead of a probe, but that is what you want in this case - only grabbing the euclid for guad gantry leveling and bed mesh. You can override the
HOME_Z macro and implement your own logic though.
(ie, go to x/y, then home Z, using the z-endstop pin)
Furtermore you'll want to modify the stow / deploy mechanisms of the stowable-probe.cfg config, to also take the Z position into account.I was able to modify the macros RATOS, HOME_Z, DEPLOY_PROBE, and STOW_PROBE to separate the interaction between the z endstop and euclid probe. Setting the Z height and Quad gantry leveling now work; at least well enough for me to get a test cube printed.
My next challenge seems to be the PRINT_START macro that is causing some issues that I haven't had time to figure out; my brain hurts too much. That has got to be the LONGEST macro I have ever seen. Obviously the result of all the goodies that have been added to the RatRig over the years.
For now, I turned off bed meshing and adaptive mesh to simplify things but something is still happening with START_PRINT expecting the probe to be deployed rather than stowed in the beginning and some batch mode parameter that I need to figure out.
Before I dive into this much further, are there any other suggestions as to what to look at? The ones you gave me were extremely helpful. ps, i also discovered that the Z axis was moving at 1/5th the expected distance. I needed to add setting to the Z steppers motors to account for this as the RatOS configurator did not take into account the gear ratio of 80:16. I'll probably add this as a separate issue.
Before I dive into this much further, are there any other suggestions as to what to look at? The ones you gave me were extremely helpful. ps, i also discovered that the Z axis was moving at 1/5th the expected distance. I needed to add setting to the Z steppers motors to account for this as the RatOS configurator did not take into account the gear ratio of 80:16. I'll probably add this as a separate issue.
My next challenge seems to be the PRINT_START macro that is causing some issues that I haven't had time to figure out; my brain hurts too much. That has got to be the LONGEST macro I have ever seen. Obviously the result of all the goodies that have been added to the RatRig over the years.It's grown way out of control. And there are already tons of logic split out into separate modules. IDEX support complicates everything a lot.
For now, I turned off bed meshing and adaptive mesh to simplify things but something is still happening with START_PRINT expecting the probe to be deployed rather than stowed in the beginning and some batch mode parameter that I need to figure out.Yeah, take a look at the batch mode stuff in stowable_probe i imagine that may have died with your overrides. the start print macro enables batch mode so that it doesn't stow the probe in between homing / z-tilt or quad gantry leveing / meshing
ps, i also discovered that the Z axis was moving at 1/5th the expected distance. I needed to add setting to the Z steppers motors to account for this as the RatOS configurator did not take into account the gear ratio of 80:16. I'll probably add this as a separate issue.Oh that's odd. Could be a bug or something is missing in the definition. Would you mind creating an issue on the configurator repo so i can look into this?
Sure has! You're welcome! thanks for helping with the voron 2.4, i only get pieces of feedback here and there, and i don't know how much people end up working around issues that shouldn't be there 😄
I think I got everything working. I can now home_z, do a quad gantry level, do a standard and adaptive mesh, and print a piece with all the all of them working together as expected. I reworked the macros by adding 2 ratos variables and accounting for these in standard code . I attached the code as separate files so you can do a difference report. Someone might take a look to see if they are mergeable in the future.
It is surprisingly satisfying to see standard RatOS running on a Voron24
It is surprisingly satisfying to see standard RatOS running on a Voron24
I need to put this somewhere so that i don't lose it. Thanks for doing the work!
I will give you a ping once i have it integrated 👍
Its only about 12 lines of code spread about 4 files, so it shouldn't take too long to merge. Only tested on the Voron and not my Vcore3 so far.