Is your feature request related to a problem? Please describe
When printing in an environment that leans to wards the hotter end of things, as bed temps approach 120-130, even with no chamber heating enabled, the heat soak routine causing the ambient heat from the bed to cook the beacon sensor. This results in occasional failures during the Beacon contact auto calibration, which runs right after the bed heat soak.
Describe the solution you'd like
This logic for the heat soaking macro here:
# park toolhead in the center at Z=2 for heat soaking
...
RATOS_ECHO MSG="Heat soaking z probe..."
_MOVE_TO_SAFE_Z_HOME
# Always soak close to first layer height.
G0 Z2 F{z_speed}
It would be really great to add some variables that could override the position here. Just like I can override the safe_home x and y coordinates, maybe having something like soak_home for x, y, and z which could be changed so the printer could work more successfully in a broader range of environments.
Describe alternatives you've considered
For now, the only solution is to rewrite RatOS macros. While it's easy enough to do, the deviation from RatOS is not good (to my understanding) as it will have issues when updating RatOS packages or upgrading versions.
Additional information
No response
Is your feature request related to a problem? Please describe
When printing in an environment that leans to wards the hotter end of things, as bed temps approach 120-130, even with no chamber heating enabled, the heat soak routine causing the ambient heat from the bed to cook the beacon sensor. This results in occasional failures during the Beacon contact auto calibration, which runs right after the bed heat soak.
Describe the solution you'd like
This logic for the heat soaking macro here:
It would be really great to add some variables that could override the position here. Just like I can override the safe_home x and y coordinates, maybe having something like soak_home for x, y, and z which could be changed so the printer could work more successfully in a broader range of environments.
Describe alternatives you've considered
For now, the only solution is to rewrite RatOS macros. While it's easy enough to do, the deviation from RatOS is not good (to my understanding) as it will have issues when updating RatOS packages or upgrading versions.
Additional information
No response