Step 13.5 — Prove the 350 mm config edits are live¶
Step 5 of 54 with a helper · Chapter 13 — Initial startup
(no image — see text)
Parts: none.
Do: Do not trust the file on disk; ask the running instance. In a browser open:
http://voron.local/printer/objects/query?toolhead=axis_maximum
Check
The browser shows "axis_maximum": [350.0, 350.0, 330.0, 0.0] from the running config; 250 or 300 in the first two slots means the wrong size pair is live.
Helper Reads the four axis_maximum numbers off the browser and checks them against 350, 350, 330, 0.
What you're looking at
Nothing to see on the machine. You are asking the running Klipper instance what it believes the machine's dimensions are, rather than trusting the file on disk. Moonraker answers that in a browser; Mainsail has no panel for the limits, and GET_POSITION prints positions, not limits.
Then confirm in Mainsail's config editor that these are uncommented: [stepper_x] position_endstop: 350 and position_max: 350; [stepper_y] the same; [stepper_z] position_max: 330; [quad_gantry_level] gantry_corners: -60,-10 / 410,420 and points: 50,25 / 50,275 / 300,275 / 300,25; [gcode_macro G32] park line G0 X175 Y175 Z30 F3600; [resonance_tester] probe_points: 175, 175, 20.
Tip
with every size commented out Klipper refuses to start, so if it is running one pair is live. Step 13.23 proves it: M114 must read X:350.000 Y:350.000. (survey §5.2 W14)
Source: leviathan-printer-rev-d-sbv2.cfg · leviathan-printer-rev-d-sbv2.cfg · Voron startup wizard § Preparation · Moonraker API § Query printer object status