search

prusa3d / Prusa-Firmware

Firmware for Original Prusa i3 3D printer by PrusaResearch
GNU General Public License v3.0
2.02k stars 1.05k forks source link

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

Closed darraghbr closed 1 year ago

darraghbr commented 2 years ago

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.

PXL_20220929_220803698 MP

darraghbr commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

PTC-based heating elements (I'm aware of only the Revo using one at the moment) are known not to work in this beta (https://github.com/prusa3d/Prusa-Firmware/pull/3552#issuecomment-1229441032 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 commented 2 years ago

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 commented 2 years ago

serial.zip

arekm commented 2 years ago

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 https://github.com/prusa3d/Prusa-Firmware/pull/3552#issuecomment-1263200210)

theloukou commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

@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 commented 2 years ago

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

Yornik commented 2 years ago

REvo six heated up first and then ran the calibration

Send: M310 A F1
Recv: LCD status changed
Recv: TM: autotune start
Recv: TM: cooling down to 50C
Recv: T:215.0 /0.0 B:61.1 /60.0 T0:215.0 /0.0 @:0 B@:0 P:24.7 A:32.7
Recv: echo:busy: processing
Recv: T:213.0 /0.0 B:61.0 /60.0 T0:213.0 /0.0 @:0 B@:2 P:24.8 A:32.9
Recv: echo:busy: processing
Recv: T:209.6 /0.0 B:60.9 /60.0 T0:209.6 /0.0 @:0 B@:22 P:25.0 A:32.9
Recv: echo:busy: processing
Recv: T:206.3 /0.0 B:60.9 /60.0 T0:206.3 /0.0 @:0 B@:27 P:25.1 A:32.8
Recv: echo:busy: processing
Recv: T:202.4 /0.0 B:60.8 /60.0 T0:202.4 /0.0 @:0 B@:30 P:25.1 A:32.6
Recv: echo:busy: processing
Recv: T:198.5 /0.0 B:60.8 /60.0 T0:198.5 /0.0 @:0 B@:35 P:25.1 A:32.8
Recv: echo:busy: processing
Recv: T:195.2 /0.0 B:60.6 /60.0 T0:195.2 /0.0 @:0 B@:52 P:25.2 A:32.8
Recv: echo:busy: processing
Recv: T:191.3 /0.0 B:60.6 /60.0 T0:191.3 /0.0 @:0 B@:38 P:25.2 A:32.9
Recv: echo:busy: processing
Recv: T:187.9 /0.0 B:60.6 /60.0 T0:187.9 /0.0 @:0 B@:38 P:25.1 A:32.8
Recv: echo:busy: processing
Recv: T:184.1 /0.0 B:60.6 /60.0 T0:184.1 /0.0 @:0 B@:27 P:25.2 A:32.8
Recv: echo:busy: processing
Recv: T:180.5 /0.0 B:60.6 /60.0 T0:180.5 /0.0 @:0 B@:32 P:25.2 A:32.8
Recv: echo:busy: processing
Recv: T:177.4 /0.0 B:60.6 /60.0 T0:177.4 /0.0 @:0 B@:22 P:25.1 A:32.8
Recv: echo:busy: processing
Recv: T:173.8 /0.0 B:60.6 /60.0 T0:173.8 /0.0 @:0 B@:18 P:25.1 A:32.6
Recv: echo:busy: processing
Recv: T:170.2 /0.0 B:60.6 /60.0 T0:170.2 /0.0 @:0 B@:18 P:25.0 A:32.5
Recv: echo:busy: processing
Recv: T:167.1 /0.0 B:60.7 /60.0 T0:167.1 /0.0 @:0 B@:0 P:25.1 A:32.8
Recv: echo:busy: processing
Recv: T:164.0 /0.0 B:60.6 /60.0 T0:164.0 /0.0 @:0 B@:8 P:25.0 A:32.7
Recv: echo:busy: processing
Recv: T:160.5 /0.0 B:60.6 /60.0 T0:160.5 /0.0 @:0 B@:11 P:25.1 A:32.6
Recv: echo:busy: processing
Recv: T:157.8 /0.0 B:60.6 /60.0 T0:157.8 /0.0 @:0 B@:16 P:25.1 A:32.6
Recv: echo:busy: processing
Recv: T:155.0 /0.0 B:60.5 /60.0 T0:155.0 /0.0 @:0 B@:31 P:25.2 A:32.6
Recv: echo:busy: processing
Recv: T:151.8 /0.0 B:60.5 /60.0 T0:151.8 /0.0 @:0 B@:16 P:25.0 A:32.7
Recv: echo:busy: processing
Recv: T:149.0 /0.0 B:60.3 /60.0 T0:149.0 /0.0 @:0 B@:45 P:25.2 A:32.5
Recv: echo:busy: processing
Recv: T:146.1 /0.0 B:60.3 /60.0 T0:146.1 /0.0 @:0 B@:29 P:25.0 A:32.4
Recv: echo:busy: processing
Recv: T:143.4 /0.0 B:60.2 /60.0 T0:143.4 /0.0 @:0 B@:50 P:25.1 A:32.7
Recv: echo:busy: processing
Recv: T:140.3 /0.0 B:60.2 /60.0 T0:140.3 /0.0 @:0 B@:45 P:25.1 A:32.7
Recv: echo:busy: processing
Recv: T:137.9 /0.0 B:60.2 /60.0 T0:137.9 /0.0 @:0 B@:46 P:25.0 A:32.5
Recv: echo:busy: processing
Recv: T:135.6 /0.0 B:60.2 /60.0 T0:135.6 /0.0 @:0 B@:26 P:25.0 A:32.5
Recv: echo:busy: processing
Recv: T:132.8 /0.0 B:60.3 /60.0 T0:132.8 /0.0 @:0 B@:12 P:24.9 A:32.6
Recv: echo:busy: processing
Recv: T:130.4 /0.0 B:60.3 /60.0 T0:130.4 /0.0 @:0 B@:12 P:25.1 A:32.7
Recv: echo:busy: processing
Recv: T:127.9 /0.0 B:60.3 /60.0 T0:127.9 /0.0 @:0 B@:5 P:24.8 A:32.6
Recv: echo:busy: processing
Recv: T:125.7 /0.0 B:60.4 /60.0 T0:125.7 /0.0 @:0 B@:0 P:25.1 A:32.6
Recv: echo:busy: processing
Recv: T:123.5 /0.0 B:60.3 /60.0 T0:123.5 /0.0 @:0 B@:8 P:24.8 A:32.3
Recv: echo:busy: processing
Recv: T:121.0 /0.0 B:60.4 /60.0 T0:121.0 /0.0 @:0 B@:10 P:24.8 A:32.7
Recv: echo:busy: processing
Recv: T:118.8 /0.0 B:60.2 /60.0 T0:118.8 /0.0 @:0 B@:37 P:24.9 A:32.4
Recv: echo:busy: processing
Recv: T:116.6 /0.0 B:60.2 /60.0 T0:116.6 /0.0 @:0 B@:41 P:24.7 A:32.2
Recv: echo:busy: processing
Recv: T:114.6 /0.0 B:60.1 /60.0 T0:114.6 /0.0 @:0 B@:53 P:24.9 A:32.3
Recv: echo:busy: processing
Recv: T:112.4 /0.0 B:60.1 /60.0 T0:112.4 /0.0 @:0 B@:37 P:24.8 A:32.5
Recv: echo:busy: processing
Recv: T:110.4 /0.0 B:59.9 /60.0 T0:110.4 /0.0 @:0 B@:63 P:24.9 A:32.5
Recv: echo:busy: processing
Recv: T:108.6 /0.0 B:60.0 /60.0 T0:108.6 /0.0 @:0 B@:49 P:24.6 A:32.5
Recv: echo:busy: processing
Recv: T:106.5 /0.0 B:60.0 /60.0 T0:106.5 /0.0 @:0 B@:47 P:24.6 A:32.5
Recv: echo:busy: processing
Recv: T:104.7 /0.0 B:60.0 /60.0 T0:104.7 /0.0 @:0 B@:43 P:24.6 A:32.5
Recv: echo:busy: processing
Recv: T:102.7 /0.0 B:60.1 /60.0 T0:102.7 /0.0 @:0 B@:18 P:24.6 A:32.7
Recv: echo:busy: processing
Recv: T:100.9 /0.0 B:60.2 /60.0 T0:100.9 /0.0 @:0 B@:1 P:24.6 A:32.5
Recv: echo:busy: processing
Recv: T:99.0 /0.0 B:60.2 /60.0 T0:99.0 /0.0 @:0 B@:0 P:24.5 A:32.6
Recv: echo:busy: processing
Recv: T:97.4 /0.0 B:60.3 /60.0 T0:97.4 /0.0 @:0 B@:0 P:24.5 A:32.6
Recv: echo:busy: processing
Recv: T:95.7 /0.0 B:60.4 /60.0 T0:95.7 /0.0 @:0 B@:0 P:24.6 A:32.4
Recv: echo:busy: processing
Recv: T:93.9 /0.0 B:60.3 /60.0 T0:93.9 /0.0 @:0 B@:8 P:24.6 A:32.3
Recv: echo:busy: processing
Recv: T:92.4 /0.0 B:60.2 /60.0 T0:92.4 /0.0 @:0 B@:27 P:24.4 A:32.4
Recv: echo:busy: processing
Recv: T:90.7 /0.0 B:60.1 /60.0 T0:90.7 /0.0 @:0 B@:36 P:24.6 A:32.2
Recv: echo:busy: processing
Recv: T:89.2 /0.0 B:60.1 /60.0 T0:89.2 /0.0 @:0 B@:36 P:24.4 A:32.3
Recv: echo:busy: processing
Recv: T:87.5 /0.0 B:59.9 /60.0 T0:87.5 /0.0 @:0 B@:60 P:24.3 A:32.2
Recv: echo:busy: processing
Recv: T:86.1 /0.0 B:59.9 /60.0 T0:86.1 /0.0 @:0 B@:58 P:24.4 A:32.5
Recv: echo:busy: processing
Recv: T:84.7 /0.0 B:59.9 /60.0 T0:84.7 /0.0 @:0 B@:58 P:24.3 A:32.3
Recv: echo:busy: processing
Recv: T:83.1 /0.0 B:59.9 /60.0 T0:83.1 /0.0 @:0 B@:55 P:24.4 A:32.3
Recv: echo:busy: processing
Recv: T:81.8 /0.0 B:59.9 /60.0 T0:81.8 /0.0 @:0 B@:49 P:24.1 A:32.4
Recv: echo:busy: processing
Recv: T:80.4 /0.0 B:60.0 /60.0 T0:80.4 /0.0 @:0 B@:17 P:24.2 A:32.6
Recv: echo:busy: processing
Recv: T:79.1 /0.0 B:60.1 /60.0 T0:79.1 /0.0 @:0 B@:14 P:24.2 A:32.3
Recv: echo:busy: processing
Recv: T:77.6 /0.0 B:60.1 /60.0 T0:77.6 /0.0 @:0 B@:8 P:24.3 A:32.3
Recv: echo:busy: processing
Recv: T:76.4 /0.0 B:60.2 /60.0 T0:76.4 /0.0 @:0 B@:0 P:24.1 A:32.5
Recv: echo:busy: processing
Recv: T:75.1 /0.0 B:60.3 /60.0 T0:75.1 /0.0 @:0 B@:0 P:24.0 A:32.4
Recv: echo:busy: processing
Recv: T:73.9 /0.0 B:60.3 /60.0 T0:73.9 /0.0 @:0 B@:0 P:24.1 A:32.2
Recv: echo:busy: processing
Recv: T:72.7 /0.0 B:60.2 /60.0 T0:72.7 /0.0 @:0 B@:15 P:24.2 A:32.5
Recv: echo:busy: processing
Recv: T:71.5 /0.0 B:60.2 /60.0 T0:71.5 /0.0 @:0 B@:12 P:23.9 A:32.4
Recv: echo:busy: processing
Recv: T:70.4 /0.0 B:60.2 /60.0 T0:70.4 /0.0 @:0 B@:20 P:24.0 A:32.5
Recv: echo:busy: processing
Recv: T:69.3 /0.0 B:60.0 /60.0 T0:69.3 /0.0 @:0 B@:64 P:24.2 A:32.2
Recv: echo:busy: processing
Recv: T:68.1 /0.0 B:59.9 /60.0 T0:68.1 /0.0 @:0 B@:69 P:23.8 A:32.3
Recv: echo:busy: processing
Recv: T:67.0 /0.0 B:59.8 /60.0 T0:67.0 /0.0 @:0 B@:73 P:24.1 A:32.2
Recv: echo:busy: processing
Recv: T:65.9 /0.0 B:59.9 /60.0 T0:65.9 /0.0 @:0 B@:47 P:23.8 A:32.3
Recv: echo:busy: processing
Recv: T:64.9 /0.0 B:59.8 /60.0 T0:64.9 /0.0 @:0 B@:60 P:23.9 A:32.3
Recv: echo:busy: processing
Recv: T:63.8 /0.0 B:59.8 /60.0 T0:63.8 /0.0 @:0 B@:47 P:23.8 A:32.2
Recv: echo:busy: processing
Recv: T:62.9 /0.0 B:59.9 /60.0 T0:62.9 /0.0 @:0 B@:32 P:23.7 A:32.4
Recv: echo:busy: processing
Recv: T:62.0 /0.0 B:60.0 /60.0 T0:62.0 /0.0 @:0 B@:10 P:23.6 A:32.2
Recv: echo:busy: processing
Recv: T:61.1 /0.0 B:60.1 /60.0 T0:61.1 /0.0 @:0 B@:6 P:23.7 A:32.2
Recv: echo:busy: processing
Recv: T:60.3 /0.0 B:60.1 /60.0 T0:60.3 /0.0 @:0 B@:4 P:23.6 A:32.3
Recv: echo:busy: processing
Recv: T:59.3 /0.0 B:60.3 /60.0 T0:59.3 /0.0 @:0 B@:0 P:23.5 A:32.3
Recv: echo:busy: processing
Recv: T:58.3 /0.0 B:60.3 /60.0 T0:58.3 /0.0 @:0 B@:0 P:23.6 A:32.3
Recv: echo:busy: processing
Recv: T:57.4 /0.0 B:60.3 /60.0 T0:57.4 /0.0 @:0 B@:0 P:23.6 A:32.1
Recv: echo:busy: processing
Recv: T:56.6 /0.0 B:60.2 /60.0 T0:56.6 /0.0 @:0 B@:19 P:23.5 A:32.1
Recv: echo:busy: processing
Recv: T:55.7 /0.0 B:60.2 /60.0 T0:55.7 /0.0 @:0 B@:25 P:23.5 A:32.1
Recv: echo:busy: processing
Recv: T:54.8 /0.0 B:60.0 /60.0 T0:54.8 /0.0 @:0 B@:48 P:23.6 A:32.1
Recv: echo:busy: processing
Recv: T:54.1 /0.0 B:60.0 /60.0 T0:54.1 /0.0 @:0 B@:53 P:23.4 A:32.2
Recv: echo:busy: processing
Recv: T:53.3 /0.0 B:59.9 /60.0 T0:53.3 /0.0 @:0 B@:52 P:23.4 A:32.1
Recv: echo:busy: processing
Recv: T:52.6 /0.0 B:59.8 /60.0 T0:52.6 /0.0 @:0 B@:62 P:23.4 A:32.4
Recv: echo:busy: processing
Recv: T:51.9 /0.0 B:59.8 /60.0 T0:51.9 /0.0 @:0 B@:57 P:23.4 A:31.9
Recv: echo:busy: processing
Recv: T:51.3 /0.0 B:59.8 /60.0 T0:51.3 /0.0 @:0 B@:53 P:23.2 A:32.3
Recv: echo:busy: processing
Recv: T:50.7 /0.0 B:59.9 /60.0 T0:50.7 /0.0 @:0 B@:34 P:23.6 A:32.1
Recv: echo:busy: processing
Recv: T:50.0 /0.0 B:60.0 /60.0 T0:50.0 /0.0 @:0 B@:13 P:23.2 A:32.4
Recv: echo:busy: processing
Recv: T:49.4 /0.0 B:60.2 /60.0 T0:49.4 /0.0 @:0 B@:0 P:23.2 A:32.3
Recv: echo:busy: processing
Recv: T:48.6 /0.0 B:60.3 /60.0 T0:48.6 /0.0 @:0 B@:0 P:23.3 A:32.4
Recv: echo:busy: processing
Recv: T:48.1 /0.0 B:60.4 /60.0 T0:48.1 /0.0 @:0 B@:0 P:23.2 A:32.3
Recv: echo:busy: processing
Recv: T:47.7 /0.0 B:60.4 /60.0 T0:47.7 /0.0 @:0 B@:0 P:23.2 A:32.4
Recv: echo:busy: processing
Recv: T:47.4 /0.0 B:60.4 /60.0 T0:47.4 /0.0 @:0 B@:0 P:23.0 A:32.3
Recv: echo:busy: processing
Recv: TM: initial C estimation
Recv: T:48.1 /230.0 B:60.3 /60.0 T0:48.1 /230.0 @:127 B@:16 P:23.4 A:32.2
Recv: echo:busy: processing
Recv: TM: error |1.370570|>1.200000
Recv: LCD status changed
Recv: TM: error |1.587287|>1.200000
Recv: LCD status changed
Recv: TM: autotune failed
Recv: ok
Recv: TM: error |1.812604|>1.200000
Recv: LCD status changed
Recv: TM: error triggered!
Recv: // action:cancel
Cancelling on request of the printer...
Recv: Error:Printer stopped due to errors. Supervision required.
Changing monitoring state from "Operational" to "Error"
Send: M112
Send: N2 M112*35
Send: N3 M104 T0 S0*34
Send: N4 M140 S0*97
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor

And without preheating it fails directly.

Send: M310 A F1
Recv: LCD status changed
Recv: TM: autotune start
Recv: TM: initial C estimation
Recv: T:18.8 /230.0 B:18.3 /0.0 T0:18.8 /230.0 @:127 B@:0 P:18.9 A:26.6
Recv: echo:busy: processing
Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
Recv: TM: error |1.447402|>1.200000
Recv: LCD status changed
Recv: T:30.3 /230.0 B:18.7 /0.0 T0:30.3 /230.0 @:127 B@:0 P:19.0 A:26.7
Recv: TM: error |1.637214|>1.200000
Recv: LCD status changed
Recv: TM: autotune failed
Recv: ok
Send: M113 S2
Recv: TM: error |1.877606|>1.200000
Recv: LCD status changed
Recv: TM: error triggered!
Recv: // action:cancel
Cancelling on request of the printer...
Recv: Error:Printer stopped due to errors. Supervision required.
Changing monitoring state from "Operational" to "Error"
Send: M112
Send: N2 M112*35
Send: N3 M104 T0 S0*34
Send: N4 M140 S0*97
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor
theloukou commented 2 years ago

@Yornik Your fail condition is still the same, you are just waiting for the first cooldown, since you heated up. As far as i understand, actual data collection starts the heating starts.

zbig-t commented 2 years ago

Please see my dataset. Retail Revo Six (blue thermistor wires), filament loaded, no other mods that could affect thermal performance.

serial.zbig-t.log.zip

wavexx commented 2 years ago

@Yornik see https://github.com/prusa3d/Prusa-Firmware/issues/3636#issuecomment-1262926997 and see if you can attach a log.

wavexx commented 2 years ago

Is there anything regarding the thermistor wire colors I should be aware of since it has been mentioned a few times?

zbig-t commented 2 years ago

Is there anything regarding the thermistor wire colors I should be aware of since it has been mentioned a few times?

If anything, it's an indicator of whether the Revo Six specimen in question was made quite early after the Revo product launch or is a part of one of the later batches. As per https://e3d-online.com/blogs/news/heatercore-update-wire-they-blue , E3D has changed the wires from white to blue at some point. There were some initial reports of early Revos failing on people with inconsistent/inaccurate thermistor readings and there seem to be less of these as of recently. That might or might not be correlated (not caused, obviously) to the wire colour change.

AliceGrey commented 2 years ago

Brand new Revo Six with otherwise stock MK3S+ - Both were purchased in the last month. Revo has the new colored cable.

prusaLog.zip

AliceGrey commented 2 years ago

Somewhat related question: Is it ok for us to use the new beta firmware with the revo six even though the new thermal model isn't working? Or is that not a safe idea?

wavexx commented 2 years ago

@AliceGrey still perfectly safe. The thermal protection is just a safety feature on top of everything that was already available.

darraghbr commented 1 year ago

First indications are good on 3.12.0-RC1 my printer goes through the entire TM calibration process when activated through the UI.

I will do it again while capturing the serial output and then I will try some printing and see what I find.

darraghbr commented 1 year ago

Here is the serial log with the apparently successful TM calibration.

serial_RC.zip

Unfortunately after the calibration finishes now when I go to heat up the nozzle to load filament it gets to about 55°C and then gives me a Thermal Anomaly error and stops heating. Serial log for that incoming.

darraghbr commented 1 year ago

Ok here is the serial logs when I try to heat to 230°C, the first one I call the command from Octoprint, the second one I do through the printer itself (Preheat / PETG)

serial_when_heating.zip

In order to disable the thermal model you just need to run M310 S0 (S1 if you want to re-enable it) unfortunately this seems to get set back to 1 on restart.

wavexx commented 1 year ago

@darraghbr yes, M310 S0 just sets the value, then you need to use M500 to save it.

darraghbr commented 1 year ago

@wavexx Ah of course, I knew I was forgetting something stupid.

ulab commented 1 year ago

Thanks for the hint on how to disable it again. Same issue with a Revo Six (old model) here.

Initial calibration works, any heating then fails with a thermal anomaly.

QR4rigs commented 1 year ago

I have the same issue, Revo six blue wires and Revo six white wires. Thermal Anomaly on heat or cool request, however initiated after a successful cal.

gregsaun commented 1 year ago

Very useful feature and thanks for the hard work! serial.zip

Config:

QR4rigs commented 1 year ago

@Prusa-Support do you need any more logs for Revo Six, I have the white and blue wired versions on different Mk3s+ printers.

wavexx commented 1 year ago

If you have some extra, yes please. Just label well the type.

QR4rigs commented 1 year ago

So sorry, I thought it would be a simple process, but I need a degree in coding it seems to get a logged output. I don't have octoprint nor raspberry pi (yet). I do have Pronterface on Mac (which I'm a newbie on, but it is the only way to get a laptop to the remote printers currently). I have 3 Revo Six installations currently. 1 printer that has a MAXTEMP ERROR even with the stock hotend at anything over 240 degrees so is running 3.12 rc1 with the new thermal model disabled due to the Thermal Anomaly and one that works fine on 3.11 which I can update to 3.12 rc1 quickly.

I really would like Revo Six supported as there is another Mk3S+ incoming next month and the stock hotend is not an option for me with all the nozzle size changes I have to do for various orders.

If anybody has a readme/howto on how to get a logged output with my limited resources, I'm happy to provide them. TIA Paul

wavexx commented 1 year ago

@QR4rigs are you on windows or linux?

We have several scripts for logging that we used during development, @3d-gussner can help with these. On windows I cannot help much.

QR4rigs commented 1 year ago

unfortunately, the laptop to hand is on Mac OS, so neither Linux nor Windows :)

ggppjj commented 1 year ago

I am also having this issue and should be able to contribute logs. Is there a way to disable the hard error tone temporarily for the sake of my neighbors?

catadiel commented 1 year ago

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.

MK3S+ with MMU2S and Revo Six (Original Version). Printer inside enclosure. serial.log

ulab commented 1 year ago

I hope this helps. I wasn't sure when to stop the log :).

tempcal-revo6-Balu.txt.zip

One thing that irritated me was that I tried doing the calibration from the menu and received a "temperature model error".

BootsSiR commented 1 year ago

Prusa MK3S w/Revo Six (blue heatercore wire - just installed this month)

log from Octoprint running the three commands below and then waiting for cooldown to room temps. Long log but better to have more info than not enough. If you need/want anything else to help troubleshoot, I'm more than happy to help.

M155 S1 C3
D70 S1
M310 A F0

serial.zip

alienryes commented 1 year ago

serial.zip MK3S+ with Revo Six original. Printer in enclosure.

BootsSiR commented 1 year ago

@darraghbr yes, M310 S0 just sets the value, then you need to use M500 to save it.

so if I do the following, this will bypass this bug until it's resolved in firmware and then I can just do S1 to re-enable it?

M310 S0
M500
alexander-akhmetov commented 1 year ago

serial.zip

MK3S+ with MMU2S and Revo Six (blue wire), no enclosure

ksipple commented 1 year ago

@darraghbr yes, M310 S0 just sets the value, then you need to use M500 to save it.

so if I do the following, this will bypass this bug until it's resolved in firmware and then I can just do S1 to re-enable it?

M310 S0
M500

I've done this to disable the feature, but when the printer is turned on or reset it tells me thermal calibration needs to be run. It then waits for me to press the button before OctoPrint can connect. Is there a timeout or way to turn the message off?

darraghbr commented 1 year ago

@ksipple

I haven't found a way to disable that message but I've raised an issue about it here #3894

joshuacant commented 1 year ago

Here's the log from my MK3S with a Revo that I purchased the day it came out, so it's from the first batch. Printer is in an enclosure, but in my cool (~10c) basement.

If additional information is needed, let me know. Will be rolling back to the previous FW until the thermal model works with Revo or the message on boot can be bypassed.

serial.zip

fridge-cat commented 1 year ago

Brand new Revo Six HeaterCore on MK3S+. Printer inside enclosure.

serial.zip

cnlson commented 1 year ago

@wavexx @QR4rigs 1) do you have enough serial outputs now? do you need more? 2) can i execute a gcode to perform the commands to disable? in other words after reset or turn off and on my printer can i just run a gcode file with those commands or will i need to execute them by terminal only? 3) can i revert to 3.11 from 3.12 if it becomes enough of an annoyance.

I have a mk3 upgraded to s+ with a revo, purchased in october, w/ white (original?) thermistor.

also any way to backup and restore live z for all stored plates?

wavexx commented 1 year ago

do you have enough serial outputs now? do you need more?

If you ware willing to submit more, please do. I can use each run to test the model offline, so strictly speaking the more the better.

can i execute a gcode to perform the commands to disable?

See https://github.com/prusa3d/Prusa-Firmware/issues/3891#issuecomment-1379287828 (and the rest of the thread). After a M310 S0 and M500 you can keep using 3.12 as before.

can i revert to 3.11 from 3.12 if it becomes enough of an annoyance.

Yes, also possible.

also any way to backup and restore live z for all stored plates?

Not in a nice way yet :( #2201 You can save the entire saved state of the printer using D3. If you're familiar with command line tools, see https://github.com/prusa3d/Prusa-Firmware/tree/MK3/tools (dump_eeprom in combination with update_eeprom will effectively save/restore everything)

cnlson commented 1 year ago

@wavexx

Not in a nice way yet :( #2201 You can save the entire saved state of the printer using D3. If you're familiar with command line tools, see https://github.com/prusa3d/Prusa-Firmware/tree/MK3/tools (dump_eeprom in combination with update_eeprom will effectively save/restore everything)

but, will it restore and cause null pointers for the thermal or other settings?

See #3891 (comment) (and the rest of the thread). After a M310 S0 and M500 you can keep using 3.12 as before.

people are posting that this is not retained after a reset or power off/on. if so i would like to automate it

is the problem with the revo that it heats much faster and detects the heat better than the v6?

looked at the eepromdump, do i need to compile that or is there a downloadable for windows?

wavexx commented 1 year ago

people are posting that this is not retained after a reset or power off/on. if so i would like to automate it

See https://github.com/prusa3d/Prusa-Firmware/issues/3891#issuecomment-1379287828 again: you can run a D3 gcode to disable the startup prompt for calibration.

When the model checking is disabled, FW 3.12 with the revo will work just in the same mode as 3.11 did. Also, downgrading to 3.11 will not clear your settings if that's what you're worried about.

wwsean08 commented 1 year ago

24v Revo nozzle (revo six prusa edition), my room temperature is around 21c and the printer is in an enclosure, with no other mods in place on my mk3s+.

serial.zip

RampentPotato commented 1 year ago

Printer type: MK3S+ WITH REVO6 Firmware: prusa3d_fw_MK3S_MK3S+_3_12_0_5672

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 results in an immediate THERMAL ANOMALY error with a warning tone and the calibration stops. Reset printer and Pronterface connection. Dismiss calibration warning. Send M310 A F1 and the printer almost immediately gives a THERMAL ANOMALY error and the calibration process stops.

Recovery Re-flashed with previous firmware prusa3d_fw_MK3S_MK3S+_3_11_0_4955

Calibration attempted with filament loaded, filament sensor disabled since new.

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

Serial output from pronterface: Connecting... start Printer is now online. echo: 3.12.0-5672 echo: Last Updated: Jan 10 2023 11:12:40 | Author: (none, default config) Compiled: Jan 10 2023 echo: Free Memory: 2592 PlannerBufferBytes: 1792 TM: stored calibration invalid, resetting echo:Stored settings retrieved adc_init CrashDetect DISABLED FSensor DISABLED Sending 0xFF echo:SD card ok

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 P1250.00 R1250.00 T1250.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 P23.25 I4.43 D30.48 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 R18.40 echo: M310 I2 R16.70 echo: M310 I3 R15.20 echo: M310 I4 R14.10 echo: M310 I5 R13.30 echo: M310 I6 R12.70 echo: M310 I7 R12.10 echo: M310 I8 R11.70 echo: M310 I9 R11.30 echo: M310 I10 R11.00 echo: M310 I11 R10.80 echo: M310 I12 R10.60 echo: M310 I13 R10.40 echo: M310 I14 R10.20 echo: M310 I15 R10.10 echo: M310 P38.00 C12.10 S1 B1 E1.74 W1.20 T-7.00

Printer reset and Pronterface disconnected and reconnected, calibration warning dismissed

M310 A F1 SENDING:M310 A F1 TM: calibration start LCD status changed TM: initial C est. echo:busy: processing TM: error |1.367377|>1.200000 LCD status changed TM: error |1.549419|>1.200000 echo:busy: processing TM: error |1.689983|>1.200000 TM: calibr. failed! echo:Temperature Model settings: echo: M310 I0 R20.50 echo: M310 I1 R18.40 echo: M310 I2 R16.70 echo: M310 I3 R15.20 echo: M310 I4 R14.10 echo: M310 I5 R13.30 echo: M310 I6 R12.70 echo: M310 I7 R12.10 echo: M310 I8 R11.70 echo: M310 I9 R11.30 echo: M310 I10 R11.00 echo: M310 I11 R10.80 echo: M310 I12 R10.60 echo: M310 I13 R10.40 echo: M310 I14 R10.20 echo: M310 I15 R10.10 echo: M310 P38.00 C12.10 S1 B1 E1.74 W1.20 T-7.00 TM: error |1.834112|>1.200000 TM: error triggered! // action:cancel Error:Printer stopped due to errors. Supervision required. [ERROR] Error:Printer stopped due to errors. Supervision required.

TM: error cleared tmc2130_home_enter(axes_mask=0x04) tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x04 echo:busy: paused for user echo:busy: paused for user echo:busy: paused for user Disconnected.