Move Out of range but not
The problem: After the print fails because of "Move out of range" I can still move the printhead manually (stilled homed). The position is at 1.77mm in X (where it failed) but if I tell it to move 0.1mm to the left (just did this in the picture) it says again out of range. But it clearly is not. Accoriding to the error message + 0,1mm the real current position is 0,046mm and not 1,77mm.
There seems to be an offset but I dont know from where?
Background: I want to print a keyboard filling nearly the complete x length of my vCore 3.1 400mm. It is 405mm long, but I increased the x length in the firmware and Orca Slicer to 408mm. I doublechecked and there is enough clearance to move the head this far. I printed several keyboards before with this setup a few months ago. But now it doesnt work anymore. Orca Slicer does not give a warning of a move outside the printbed.
I did some more tests and got it to work like this: increase X in the Slicer to 410mm but keep it at 408mm in the printer.cfg (otherwise the fan duct collides). But thats not a good solution.
Also tried to disable exclude and name object since Helge said it might have bugs, but did not solve the problem.
Also updated to the latest everything and did not solve it.
(the print in the picture is just a small part of the complete print at the same position, for testing)
9 Replies
my printer.cfg
I printed one successfully but now the second one (with slightly different gcode) failed at 96 Percent :dunkelheit:
Move out of range: -0.019 263.662 23.287 [140557.543]
My best guess is that these z-hop movements caused it, but why the top one and not the other two (exact layer were it failed shown)? they worked fine for some reason although this is a straight 90° wall, not tilted.
from the topIt seems to be a slicer issue, not Klipper, at least this sounds exactly like my problem: https://github.com/SoftFever/OrcaSlicer/issues/3107
GitHub
Spiral Z-Hop can carry nozzle outside of printable area · Issue #31...
OrcaSlicer Version 1.8.1 OS version Windows 11 Additional system information Ryzen 7 5800X 32GB RAM Printer Voron Trident 300mm How to reproduce Load up an object with less than 1-2mm of clearance ...
…or not. Was not able to reproduce it with a cutout of the same exact model at the same position :shrug: Worked fine
This happens because of you skew correction settings
Skew correction is a gcode transform that dynamically applies an offset to account for skew in your print. That means 0 isn't always 0, it's 0 +/- whatever is needed to make your printer square at that Y coordinate.
You cannot print up to min / max with skew correction enabled, but you can lower you position_min on x.
Solution
@Technofrikus this should solve your problem.
Skew! Ohhh. I also thought about filament shrinkage, which I also "use" to get an accurate size. With this enabled the model is not 405,00 mm but 405,89mm in length during printing. But then there is still ~1mm left on each side (408mm total length available). But with the skew enabled it is not enough maybe?
Thanks! Will try that!
If skew being the reason, I think this would explain why it did not trigger with just a small cutout of the big file? Maybe, not sure how this is calculated.
actual_x = commanded_x * skew_factor(y)
Confirmed working, now! Let the same gcode run dry over night and no problems. Thanks a lot! :pray: