Error during homing contact on repeated prints
I am receiving an error message "Error during homing contact" inconsistently. In this case, I printed two objects and the third gave the error. In particular, the second and third object are near identical (extrusion multiplier tests). I also ran into this issue yesterday under similar circumstances. (Three prints succeeded and all after the third failed like this)
The carriage is parked in the extreme front left position every time. The nozzle tip is beyond the range of the bed magnet. It happens after rehoming after z tilt.
This is using a beacon and on ratos 2.1
![No description](https://cdn.answeroverflow.com/1262192503356919898/Screenshot_2024-07-14_at_7.40.03_PM.png)
![No description](https://cdn.answeroverflow.com/1262192503839395840/Screenshot_2024-07-14_at_7.40.45_PM.png)
69 Replies
I can take more pictures if the position is not illustrated enough
![No description](https://cdn.answeroverflow.com/1262192734131978241/PXL_20240714_232845982.jpg)
is it beacon based printer it looks like? If so do you have performance mode enabled (assuming RatOS 2.1). It can sometimes error out like that on homing if the Z does not come up quickly enough. Performance mode makes it home quicker and typically takes care of it. Otherwise just start the print again and you should be fine.
It is beacon based,
right now I did not enable performance mode in the configurator. don't currently have cooled drivers
I can retry the print, but yesterday this happened consistently after the first few two prints
![No description](https://cdn.answeroverflow.com/1262196540282241146/Screenshot_2024-07-14_at_7.57.26_PM.png)
Though now I wonder if I can work around it by turning off the motors in between each print
which isn't really a "fix" but a way to narrow down the cause
Without turning off the motors, but letting it cool down, it worked
Immediately trying again it failed in the same way
third time right way also failed same way
fourth time: cut power to motors, did not let cool down. failure
I do not think keeping exact track of the temps will matter but this is right after the fourth failure
![No description](https://cdn.answeroverflow.com/1262205285842288651/Screenshot_2024-07-14_at_8.32.21_PM.png)
So for starters, you'll want to fix this
That's what's causing the error (there's no contact event detected when it is expected)
I assumed as much, but toying with the value of
[beacon] y_offset: 22.5
didnt seem to move where it probed
and it only tried to move that far on the prints that failed. the ones that did not fail tested within the range of the magnet on the build plateIt will move the toolhead so that the coil is over the nozzle coordinates, that's what the offset is used for. That is not the problem here though. You're homing in a bad spot. It's just poorly (or not at all) calibrated x/y limits.
you want 0,0 to be 5mm within the print sheet (it's 10cm wider / longer than the build area)
Just noticed someone posted a guide to doing this, you can give that a shot: https://discord.com/channels/582187371529764864/1261800913547558964
I will test this in just a moment, thank you
I think those steps exactly are incorrect for the y axis on vcores
Setting the position_endstop and position_min to the negative values as they describe causes it to move forward (away from the y endstop) during homing
e: may have figured it out, if the nozzle tip was inside the plate at 15mm, then I think i want to set
[stepper_y]
position_endstop = 485
(that is, 500 - 15)Yes on V-Core 3 you home at the back which naturally is a positive endstop value near position_max
how did you know that i just started the next test print litterally One minute ago
But yea, I think those instructions linked assume the endstop is at 0 for both X and Y,
the same process can be used for Y, just modifying a different value
It's assuming everyone uses a voron š
Huh, first two prints after changing that worked fine. but just as before, the third failed with the carriage parked in the corner
This time within the bounds of the sheet, but same corner
Still getting failures in the same way unless I let it sit for a long time
I dont think the offsets were directly the issue