Internal error on commands: "HYPERLAPSE" and "UPDATE_DELAYED_GCODE"
Vooks916 opened this issue · comments
When defining the autotune_tmc sections for each motor, I am getting an error related to timelapse? This only occurs when using the autotune on motors z2, z3, and extruder on a V2.4. If I only define autotune for any combination of z0, z1, x, and y, no errors are thrown. Klipper, along with everything else on my printer, is fully up to date.
klippy(7).log
Similarly, on my Trident config, Klipper will not start if I have all 3 Z motors defined, giving that same error. If I disable Z1 or Z2, it at least starts successfully.
#--[Klipper TMC Autotune Extension ]----------------------------------------------------------------
[autotune_tmc stepper_x]
motor: ldo-36sth20-1004ahg
[autotune_tmc stepper_y]
motor: ldo-36sth20-1004ahg
[motor_constants ldo-42sth40-1684cl350et]
# LDO Trident 300 Kit
resistance: 1.65
inductance: 0.0041
holding_torque: 0.45
max_current: 2.0 # 1.68
steps_per_revolution: 200
# [autotune_tmc stepper_z]
# motor: ldo-42sth40-1684cl350et
# [autotune_tmc stepper_z1]
# motor: ldo-42sth40-1684cl350et
# [autotune_tmc stepper_z2]
# motor: ldo-42sth40-1684cl350et
[autotune_tmc extruder]
motor: ldo-36sth20-1004ahg
#===================================================================================================
It conflict with moonraker-timestamp
https://github.com/mainsail-crew/moonraker-timelapse
Writing the configuration after [include timelapse.cfg] will solve this problem.