Bed heater tuning algorithm failure 3.2
-
Just installed 3.2 and decide to re PID tune both printers. The cartesian tuned fine. The delta heater 1 also tuned fine but the bed heater just runs the tuning algorithm (M303 H0 S70) for about 40 minutes and then displays M303
Heater 0 tuning failedForgot to add that it sat at Heater 0 is being tuned, phase 4 of 4 for a long time before failing.
I ran an M122 and I can't find any specific error regarding PID tuning. Is there any way to get more detailed error information? It would be nice to know why it's unhappy. Sorry that I don't remember when I last did a tune prior to 3.2.
1/5/2021, 4:00:24 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet Ethernet 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F4-3S06R-9LXVW
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 68352 of which 248 recycled
Never used RAM 20020, free system stack 110 words
Tasks: NETWORK(ready,180) HEAT(blocked,145) MAIN(running,470) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 01:45:45 ago, cause: software
Last software reset at 2020-12-27 17:01, reason: User, GCodes spinning, available RAM 20020, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 44.4, current 47.6, max 48.0
Supply voltage: min 12.0, current 12.2, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 36162, standstill, SG min/max 0/412
Driver 1: position 36162, standstill, SG min/max 0/368
Driver 2: position 36162, standstill, SG min/max 0/409
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-01-05 16:00:23
Cache data hit count 4294967295
Slowest loop: 15.76ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 13.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 4631035ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 66, completed moves 66, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 50], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 13.47ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex -
The tuning can take a long time for some heaters. Can you give us some details on the heater that failed?
-
@Phaedrux Nothing special. It's a stock 12 volt bed heater from what was an Anycubic Kossel Plus. Not much left of the old gal other than the bed and aluminum extrusions. Duet 2 Ethernet with SmartEffector and Flex3Drive direct extruder.
-
Do you happen to have the tuning results from the previous firmware?
-
@Phaedrux I think so.
This is the current M307 that's running on the printer now and seems to control the bed well.
M307 H0 R0.196 C734.056:734.056 D0.65 S1.00 V12.1 B0This is config-override.g from a backup I made in June, 2020
M307 H0 A172.9 C784.9 D0.4 S1.00 V11.9 B0At the fourth try the tune returned a result:
Warning: heater behaviour was not consistent during tuning
Auto tuning heater 0 completed after 3 idle and 25 tuning cycles in 3280 seconds. This heater needs the following M307 command:
M307 H0 R0.223 C738.8 D0.64 S1.00 V12.1The values appear to not be very much different from the current M307.
I captured a portion of the temperature chart. The whole tune cycle looked like this portion. A gentle sawtooth moving between 65 and 70 degrees. I never saw anything that looked inconsistent.
