Basic Information:
Printer Model: LDO Voron 2.4 Rev. D
MCU / Printerboard: NHK?
Host / SBC Rpi
klippy.log.zip (2.3 MB)
klippy.log
Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
I am working through the setup of this machine and finding some issues. Of course one thing leads to another.
The start of this was horrible problems with the Beacon. Out of 20+ tries, one might succeed and get through the probing sequence. Standard deviation was larger than the limit. I adjusted to take five samples rather than three, and bumped the limit up a bit, and now that’s working reliably.
I noticed that at the beginning of probing the bed, the printhead moves to the right, but the Beacon is behind the printhead. Obviously this is not correct, and I was able to set the proper offset so that now the printhead moves forward such that the beacon coil is centered over the spot where the nozzle touched previously. (yay!) At the moment I’m using a Y offset of 15 because of a certainly related issue I’ll get to.
In working through the beacon config, the docs say that the Z offset is REQUIRED and yet putting in any Z offset gives me an error. So I’ll leave that for the moment though I would like to make it right.
At this point, I’m close to getting it working right, except that after running the tilt adjust, I’m getting an error: Move out of range 20, -10 2 [0] I assume it’s objecting to the Y move of -10?
So I suppose there’s a move buried in the call to Bed_Mesh_Calibrate?
I assume this has something to do with my correction to the Beacon settings, but how do I get past this?
I just confirmed that my Y offset was “causing” the problem, but without the right offset, the coil isn’t looking at the place where the nozzle was…??
My assumption (not seeing it clearly stated) that the purpose of those offset numbers is so that the beacon coil is centered over where the nozzle was when it probed using the nozzle. Am I wrong?
This machine is 300x300mm
LDO Leviathan controller
Voron Stealthburner (Is the beacon offset documented somewhere?)
I added a bunch of respond messages to get it debugged to this point.
*; --- Probe/level/mesh ---*
RESPOND TYPE=echo MSG="Probing"
BED_MESH_CLEAR
SET_GCODE_OFFSET Z=0
G28 Z
G0 Z2 F6000
G28 Z METHOD=CONTACT CALIBRATE=1
RESPOND TYPE=echo MSG="Tilt Adjust"
Z_TILT_ADJUST PROBE_METHOD=CONTACT
RESPOND TYPE=echo MSG="Bed meshing"
BED_MESH_CALIBRATE RUNS=2 ←— Error happens here
[beacon]
serial: /dev/serial/by-id/usb-Beacon_Beacon_RevH_BEC73BF45157355957202020FF0E2E17-if00
x_offset: 0 # update with offset from nozzle on your machine
y_offset: 15 # update with offset from nozzle on your machine
;z_offset: 10 # While the beacon documentation says that the z_offset is REQUIRED, uncommenting this line results in an error.
#****** DVH **************************************************************
autocal_sample_count: 5
# Number of samples used for each autocal.
autocal_tolerance: 0.01 ; Bumped this up because of excessive failures in probing.
# Acceptance tolerance for an autocal result.
autocal_max_retries: 5
# Number of retry attempts permitted when tolerance is exceeded.
;samples: 5 ; Increased from 3 to fix instability. Standard Deviation of 5 samples is more meaningful than 3
#*************************************************************************
mesh_main_direction: x
mesh_runs: 2
speed: 4
contact_max_hotend_temperature: 210 # increase to probe at print temps
home_xy_position: 150, 150 # update with your safe position
home_z_hop: 5
home_z_hop_speed: 10
home_xy_move_speed: 200
home_method: contact # use proximity for induction homing
home_method_when_homed: proximity # after initial calibration use induction
home_autocalibrate: unhomed # contact will calibrate beacon on first home
