MPC tune aborts with "Temperature error" #784
Unanswered
nelis10000
asked this question in
Q&A
Replies: 2 comments
-
Please try with latest firmware version. Also try with the latest Marlin bugfix. Report MPC issues in Marlin's repository. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi mriscoc, I wasn't sure where to post this issue. Thanks for the pointers! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm having problems tuning the MPC on my Ender 3S1 with an all-metal heating block.
This heating block has a 24V/40W heating element (measured cold resistance 14.8Ω) and a bi-metallic heat break.
Firmware used is Ender3S1-F1-UBL-MPC-20221222.bin.
In the octoprint terminal, I can see "Temperature error" followed by a "MPC Autotune finished!" (all MPC variables are 0).
To troubleshoot this problem, I've attached an LED to the heater to get a visual indication of the heater PWM.
What I see is this:
(I did change the code to "hotend.target + 30.0f" but the result is the same, only 30C overshoot instead of 15C)
I compiled a new firmware, same as 20221222 above, but with the two debug blocks enabled (temperature.cpp, at lines 1088 and 1479).
This produces a lot of extra data on the Octoprint terminal, most of which I don't understand but this part looks odd to me:
Tune ok: Recv: asymp_temp 895.12
Tune fail: Recv: asymp_temp 4294967295.42949672954294967295
Attached is the terminal output for:
Anyone who knows what's going on and (optionally but much appreciated) how to fix it?
Thanks,
Niels
newblock-no_heatsock-dbg-OK-03.txt
newblock-heatsock-dbg-FAIL-03.txt
origblock-heatsock-dbg-OK-03.txt
Beta Was this translation helpful? Give feedback.
All reactions