FLSUN Q5 + Artillery Ruby 1.2: DELTA_CALIBRATE crashes into bed

General Discussion
1

Basic Information:

Printer Model: FLSunQ5
MCU / Printerboard: Artillery Ruby 1.2
Host / SBC: Raspberry Pi zero 2W
klippy.log

Describe your issue:

Hi everyone, I’m looking for some help with a Klipper setup on my FLSUN Q5, which I’m running with an Artillery Ruby 1.2 MCU. I swapped in this board after accidentally damaging the original one, and it was the only spare I had available.

The initial configuration went pretty smoothly:

• I generated the printer.cfg correctly.

• Endstops are working and detected properly.

• The probe works too — if I run the PROBE command, it triggers and stops as expected when it touches the bed.

The issue starts when I try to run DELTA_CALIBRATE: As soon as I start it, the printhead crashes straight into the bed. It seems like the probe isn’t triggering at all during the calibration. The same thing happens if I try DELTA_CALIBRATE METHOD=manual. I noticed that the Z movement is 4x greater than expected — for example, if I send G1 Z25, the head moves 100 mm instead.

Thinking it might be a rotation_distance issue, I tried reducing the value to 1/4, but then the motors just whine and don’t move at all.

My questions:

  1. ⁠⁠Could Klipper be interpreting the steps/mm incorrectly due to the Artillery Ruby 1.2 board?

  2. ⁠⁠Is there something wrong in my driver setup or rotation_distance values? 3. Why does the PROBE command work, but DELTA_CALIBRATE seems to ignore it completely?

Any suggestions or insight would be greatly appreciated. Thanks in advance!

2

Hi @link96 ,

Dividing your rotation distance by four will multiply the motor’s motion by four times.

Does multiplying the rotation distance by four work instead?

1 Like
3

It seems strange. The configuration appears to closely follow the defaults for this printer. Did you modify anything?

4

You’re right — I miscalculated my rotation_distance. After fixing that, DELTA_CALIBRATE seems to work fine without any other changes.

I honestly didn’t expect the probe trigger to stop working during calibration just because of incorrect movement scaling. Definitely learned something here — thanks for pointing me in the right direction!

The issue is resolved now. Thanks again!

2 Likes