Heaters Unresponsive, no Errors
-
Running 3.4.0.B7 on my Maestro, it is getting stuck where the heaters (bed and nozzle) will not respond to temp commands given through DWC or gcode. No errors shown, they just stay off.
I have tried cycling through active/standby/off
The behavior only seems to clear after power cycling the board.
I think this started after I ran the latest PID tuning. So, here are the before/after values in case it is related:
Bed: Old: M307 H0 R0.194 C896.8 D2.07 S1.00 V24.3 New: M307 H0 R0.190 K0.196:0.000 D2.03 E1.35 S1.00 B0 V24.3 Hotend: Old: M307 H1 R2.523 C231.0:134.5 D5.90 S1.00 V24.3 New: M307 H1 R2.324 K0.389:0.146 D3.76 E1.35 S1.00 B0 V24.3
Diag data when it is in the problem condition:
m122 === Diagnostics === RepRapFirmware for Duet 2 Maestro version 3.4.0beta7 (2021-12-16 12:23:42) running on Duet Maestro 1.0 Board ID: 08DJM-956DU-LLMS4-7J9F6-3SN6Q-KBM2Q Used output buffers: 3 of 24 (14 max) === RTOS === Static ram: 23572 Dynamic ram: 67716 of which 0 recycled Never used RAM 19696, free system stack 150 words Tasks: NETWORK(ready,99.8%,263) ACCEL(notifyWait,0.0%,349) HEAT(notifyWait,0.8%,342) Move(notifyWait,4.2%,310) TMC(notifyWait,14.8%,110) MAIN(running,82.2%,464) IDLE(ready,0.0%,31), total 201.8% Owned mutexes: W5500(NETWORK) === Platform === Last reset 13:58:32 ago, cause: power up Last software reset at 2021-08-11 20:47, reason: User, GCodes spinning, available RAM 19744, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 1866 MCU temperature: min 38.6, current 44.4, max 47.0 Supply voltage: min 24.0, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/90/90, gc cycles 0 Events: 0 queued, 0 completed Driver 0: pos 2399, standstill, read errors 0, write errors 0, ifcnt 21, reads 51725, writes 21, timeouts 0, DMA errors 0, CC errors 0 Driver 1: pos 3195, standstill, read errors 0, write errors 0, ifcnt 21, reads 51725, writes 21, timeouts 0, DMA errors 0, CC errors 0 Driver 2: pos 2392, standstill, read errors 0, write errors 0, ifcnt 21, reads 51725, writes 21, timeouts 0, DMA errors 0, CC errors 0 Driver 3: pos 0, standstill, read errors 0, write errors 0, ifcnt 29, reads 51461, writes 285, timeouts 0, DMA errors 0, CC errors 0 Driver 4: pos 0, standstill, read errors 0, write errors 0, ifcnt 6, reads 51740, writes 6, timeouts 0, DMA errors 0, CC errors 0 Driver 5: pos 0, ok Driver 6: pos 0, ok Date/time: 2022-02-04 11:14:09 Slowest loop: 408.62ms; fastest: 0.11ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 8 SD card 0 detected, interface speed: 10.0MBytes/sec SD card longest read time 3.4ms, write time 143.4ms, max retries 0 === Move === DMs created 83, segments created 27, maxWait 48395317ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 8, completed 8, hiccups 5, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0 Heater 1 is on, I-accum = nan === GCodes === Segments left: 0 Movement lock held by File HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is doing "M116 P0" in state(s) 0 23, running macro 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: 257.48ms; fastest: 0.02ms 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
-
Can you try with this beta release and retune the heaters?
https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0
-
@phaedrux Thanks!
Installed and run on the hotend
New values very similar: M307 H1 R2.459 K0.398:0.160 D3.91 E1.35 S1.00 B0 V24.3
I'll run the bed now, but that takes forever.
-
Okay, bed finally done. Sheesh that takes a long time! 1 hour 13 minutes.
Warning: heater behaviour was not consistent during tuning Auto tuning heater 0 completed after 3 idle and 25 tuning cycles in 4420 seconds. This heater needs the following M307 command: M307 H0 R0.190 K0.174:0.000 D1.95 E1.35 S1.00 B0 Edit the M307 H0 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.
Old: M307 H0 R0.190 K0.196:0.000 D2.03 E1.35 S1.00 B0
New: M307 H0 R0.190 K0.174:0.000 D1.95 E1.35 S1.00 B0Also, I noticed the hotend tuning produces a V parameter, but the bed tuning does not. Should I add it?
-
@ccs86 said in Heaters Unresponsive, no Errors:
Also, I noticed the hotend tuning produces a V parameter, but the bed tuning does not. Should I add it?
From the wiki - quote.........
"Vnnn VIN supply voltage at which the A parameter was calibrated (RepRapFirmware 1.20 and later). This allows the PID controller to compensate for changes in supply voltage. A value of zero disables compensation for changes in VIN voltage. Supply voltage compensation is applied to hot end heaters only, not to bed or chamber heaters."
-
@deckingman said in Heaters Unresponsive, no Errors:
@ccs86 said in Heaters Unresponsive, no Errors:
Also, I noticed the hotend tuning produces a V parameter, but the bed tuning does not. Should I add it?
From the wiki - quote.........
"Vnnn VIN supply voltage at which the A parameter was calibrated (RepRapFirmware 1.20 and later). This allows the PID controller to compensate for changes in supply voltage. A value of zero disables compensation for changes in VIN voltage. Supply voltage compensation is applied to hot end heaters only, not to bed or chamber heaters."
That explains it!
-
Did it help the original problem?
-
@phaedrux said in Heaters Unresponsive, no Errors:
Did it help the original problem?
We shall see. I'll report back after I get some time on it.
-
@phaedrux So far, so good. Thanks!