[BUG] MK3S+ WITH REVO fails to calibrate new thermal model

[darraghbr]

Printer type - MK3S+ WITH REVO
Printer firmware version - 3.12.0-BETA1

Describe the bug
Attempting to start the new thermal model calibration WITH REVO (M310 A F1) results in an immediate THERMAL ANOMALY error with a warning tone and the calibration stops.

To Reproduce
Have a MK3S+ with REVO SIX installed, ensure RPi port is disabled, send M503 over USB with Pronterface, then send M310 A F1 and the printer almost immediately gives a THERMAL ANOMALY error and the calibration process stops.

I attempted the calibration both with and without filament loaded, with the same end result.

Expected behavior
This was not unexpected, and serves as feedback for the developers.

[darraghbr]

M503 response:

M503
SENDING:M503
echo:Steps per unit:
echo: M92 X100.00 Y100.00 Z400.00 E280.00
echo:UStep resolution:
echo: M350 X16 Y16 Z16 E32
echo:Maximum feedrates - normal (mm/s):
echo: M203 X200.00 Y200.00 Z12.00 E120.00
echo:Maximum feedrates - stealth (mm/s):
echo: M203 X100.00 Y100.00 Z12.00 E120.00
echo:Maximum acceleration - normal (mm/s2):
echo: M201 X1000 Y1000 Z200 E5000
echo:Maximum acceleration - stealth (mm/s2):
echo: M201 X960 Y960 Z200 E5000
echo:Acceleration: P=print, R=retract, T=travel
echo: M204 P1000.00 R1250.00 T1000.00
echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
echo: M205 S0.00 T0.00 B0.00 X10.00 Y10.00 Z0.40 E4.50
echo:Home offset (mm):
echo: M206 X0.00 Y0.00 Z0.00
echo:PID settings:
echo: M301 P16.80 I3.20 D22.04
echo:PID heatbed settings:
echo: M304 P126.13 I4.30 D924.76
echo:Retract: S=Length (mm) F:Speed (mm/m) Z: ZLift (mm)
echo: M207 S3.00 F2700.00 Z0.00
echo:Recover: S=Extra length (mm) F:Speed (mm/m)
echo: M208 S0.00 F480.00
echo:Auto-Retract: S=0 to disable, 1 to interpret extrude-only moves as retracts or recoveries
echo: M209 S0
echo:Filament settings: Disabled
echo:Arc Settings: P:Max length(mm) S:Min length (mm) N:Corrections R:Min segments F:Segments/sec.
echo: M214 P1.00 S0.50 N25 R20 F0
echo:Temperature Model settings:
echo: M310 I0 R20.50
echo: M310 I1 Rnan
echo: M310 I2 Rnan
echo: M310 I3 Rnan
echo: M310 I4 Rnan
echo: M310 I5 Rnan
echo: M310 I6 Rnan
echo: M310 I7 Rnan
echo: M310 I8 Rnan
echo: M310 I9 Rnan
echo: M310 I10 Rnan
echo: M310 I11 Rnan
echo: M310 I12 Rnan
echo: M310 I13 Rnan
echo: M310 I14 Rnan
echo: M310 I15 Rnan
echo: M310 P38.00 C12.10 S0 B1 E1.74 W1.20 T-7.00

[darraghbr]

M310 A F1 response:

M310 A F1
SENDING:M310 A F1
LCD status changed
TM: autotune start
TM: cooling down to 50C
echo:busy: processing
TM: initial C estimation
echo:busy: processing
TM: error |1.280376|>1.200000
LCD status changed
TM: error |1.501300|>1.200000
LCD status changed
TM: error |1.709649|>1.200000
LCD status changed
TM: autotune failed
TM: error |1.874828|>1.200000
LCD status changed
TM: error triggered!
Received command cancel
// action:cancel
Error:Printer stopped due to errors. Supervision required.
[ERROR] Error:Printer stopped due to errors. Supervision required.

TM: error |2.014009|>1.200000
LCD status changed
tmc2130_home_enter(axes_mask=0x04)
TM: error |2.131985|>1.200000
LCD status changed
TM: error |2.211606|>1.200000
LCD status changed
TM: error |2.236551|>1.200000
LCD status changed
tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x04
TM: error |2.213689|>1.200000
LCD status changed
TM: error |2.136456|>1.200000
LCD status changed
TM: error |2.017257|>1.200000
LCD status changed
echo:busy: paused for user
TM: error |1.880923|>1.200000
LCD status changed
TM: error |1.880923|>1.200000
TM: error cleared
echo:busy: paused for user

[oroz]

Same for me, MK3S with Revo Six

Send: M310 A F1
Recv: LCD status changed
Recv: TM: autotune start
Recv: TM: initial C estimation
Recv: T:41.7 /230.0 B:43.8 /0.0 T0:41.7 /230.0 @:127 B@:0 P:32.7 A:38.7
Recv: echo:busy: processing
Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
Recv: TM: error |1.244095|>1.200000
Recv: LCD status changed
Recv: TM: error |1.423390|>1.200000
Recv: LCD status changed
Recv: TM: error |1.588214|>1.200000
Recv: LCD status changed
Recv: T:53.7 /230.0 B:43.9 /0.0 T0:53.7 /230.0 @:127 B@:0 P:32.7 A:39.1
Recv: TM: error |1.739812|>1.200000
Recv: LCD status changed
Recv: echo:busy: processing
Recv: TM: autotune failed
Recv: ok
Recv: TM: error |1.886143|>1.200000
Recv: LCD status changed

[wavexx]

PTC-based heating elements (I'm aware of only the Revo using one at the moment) are known not to work in this beta (#3552 (comment) for extra details). Nevertheless, we hope to support this and having a few extra traces would be very useful.

In order to submit a trace you should log all the serial output from the printer, with timestamps, while running the calibration. Using octoprint would be the perfect solution as it does everything right out of the box. To initiate a calibration with full log, issue the following commands in sequence:

M155 S1 C3
D70 S1
M310 A F0

These will run a full calibration without self-check, it should always succeed (and produce copious output). You can save all the output (from M155 to the final result) and attach it here (as a zip file) along with the details of the printer (revo model and any other mods on the printer if any). We have just two samples at the moment from a revo hotend, but it would be great to have around ~20.

[darraghbr]

In order to submit a trace you should log all the serial output from the printer, with timestamps, while running the calibration. Using octoprint would be the perfect solution as it does everything right out of the box. To initiate a calibration with full log, issue the following commands in sequence:

M155 S1 C3
D70 S1
M310 A F0

These will run a full calibration without self-check, it should always succeed (and produce copious output). You can save all the output (from M155 to the final result) and attach it here (as a zip file) along with the details of the printer (revo model and any other mods on the printer if any). We have just two samples at the moment from a revo hotend, but it would be great to have around ~20.

serial.zip

Is it just the serial logs that are required? I have uploaded mine please let me know if you want anything different.

Standard MK3S+ E3D Revo Six no other modifications.

[oroz]

serial.zip

[arekm]

Log for a newer 24V revo heater (one with blue thermistor wire):

M310
M155 S1 C3
D70 I1
M310 A

Obviously later M310 S1 and hotend to 200 degree -> error.

newrevo.log.txt.gz

(copy of #3552 (comment))

[theloukou]

Here to confirm the same issue, only difference is i have a beta testing unit of the Revo (then V7), hence why i don't post any serial logs. If you think they would help though, even if i don't have an actual production spec Revo, let me know!

[madproducts]

Same issue. Getting THERMAL ANOMALY message ion LCD.
Standard MK3S+ with original E3D Revo Six and no other modifications to the printer.
Serial log from Octoprint. SD card inserted. No MMU installed.
LCD display during logging was "Temp. model autotune" . Stopped logging when display returned to "Prusa i3 MK3S OK" and temperature started dropping back down.

PrinterDetailsatBoot.txt
M503.txt
serial.zip

[wavexx]

@theloukou Might still be useful, if you don't mind please the post as well, writing that's a beta unit. I doubt the heating core changed in betas, and I can still use the log to see if that would pass the calibration.

[theloukou]

Here are my logs as well. if any more info/measurements are needed, please just ask ^_^
MK3, running a beta version of Revo (E3D v7 then)
serialLog.zip