Toolboard Heater Fault
-
this is the diagnostics when the hotend is in a fault state. The console of paneldue doesn't tell me what the fault is
RepRapFirmware for Duet 3 MB6HC version 3.3RC3 (2021-05-26 12:29:42) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 150784 Dynamic ram: 62052 of which 208 recycled Never used RAM 138292, free system stack 126 words Tasks: SBC(ready,5.7%,328) HEAT(delaying,0.0%,295) Move(notifyWait,0.0%,266) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,8.1%,59) MAIN(running,86.1%,922) IDLE(ready,0.1%,29), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:05:42 ago, cause: software Last software reset at 2021-06-06 13:29, reason: User, GCodes spinning, available RAM 141148, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 Step timer max interval 133 MCU temperature: min 36.6, current 37.0, max 37.2 Supply voltage: min 2.1, current 24.5, max 25.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 0.5, current 12.1, max 12.1, under voltage events: 2 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/8/8, gc cycles 0 Driver 0: position 32400, standstill, reads 56524, writes 33 timeouts 0, SG min/max 0/0 Driver 1: position -400, standstill, reads 56518, writes 39 timeouts 0, SG min/max 0/194 Driver 2: position 3084, standstill, reads 56518, writes 39 timeouts 0, SG min/max 0/356 Driver 3: position 0, standstill, reads 56518, writes 39 timeouts 0, SG min/max 0/182 Driver 4: position 0, standstill, reads 56518, writes 39 timeouts 0, SG min/max 0/173 Driver 5: position 0, standstill, reads 56518, writes 39 timeouts 0, SG min/max 0/125 Date/time: 2021-06-06 13:35:40 Slowest loop: 161.46ms; fastest: 0.03ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 81161ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 41, completed moves 41, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 3102, send timeouts 10, received 4070, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 750, free buffers 49 (min 48), ts 1713/1702/0 Last cancelled message type 30 dest 127 === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 12305/12305 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2c88c Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.3-rc3 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 36.10 Codes per second: 0.42 Maximum length of RX/TX data transfers: 3060/896 -
What is the error message given in the console?
Post your config.g please.
-
@phaedrux said in Toolboard Heater Fault:
Post your config.g please.
Is in the first posting
is it possible that the PID settings to early loaded? (in line 57 & 58) -
@phaedrux I did post my config.g in the OP.
It doesn't give an error message in the console or in the UI. I just says fault
-
I just uploaded another benchy and tried pre heating the hotend manually. After less than 20 seconds it faults out. No error message of any kind.
If I clear the fault by clicking "Hotend", wait 10 seconds once the popup comes up asking me to confirm and hit reset. I click "Hotend" again and it successfully heated up without a fault
-
@dhusolo said in Toolboard Heater Fault:
M307 H1 R2.330 C273.8:126.9 D12.41 S1.00 V25.7 ; Set PID for Hotend .4Bmm nozzle POST RRF 3.2.3
I'm surprised the tuning thinks your hotend has 12 seconds of dead time, yet the graph shows it hitting 90c quite quickly.
Have you tried PID tuning on 3.3 RC3 yet? Might be worth deleting your M307 line and re-tuning.
What kind of thermistor do you have?
If you send M98 P"config.g" do you get any errors back?
-
@phaedrux Yes I noticed it heating up quite quickly however that might be due to the fact that it's a liquid cooled setup.
I haven't deleted the M307 line and re-tuning but I have tried PID tuning a few times with the existing M307.
These are the thermistors I'm using. I noticed these are 3950 where I had 4725 in my M308 config however I've been using the same thermistor with the same B value for a few months. link
When I do M98 P"config.g" I do not get any errors
-
Let us know how a fresh PID tuning works out with the corrected B value. It will likely give you a slightly more accurate temp reading. So if you're used to printing at a certain temp now that might change slightly.
-
@phaedrux I just ran it again after clearing
M307.M303 T0 F0.9 S215
These are the results
M307 H1 B0 R2.824 C282.4:110.0 D9.82 S1.00 V25.7 -
@dhusolo Why F0.9?
Fnn (RRF 3.3beta3 and later) Fan PWM to use when the print cooling fan is turned on (ignored if the T parameter is not present), default 1.0. Use a lower value if youpr printer uses a powerful print cooling fan that you do not normally run at full PWM.
-
@phaedrux tunes with Fan on at 90%
-
M307 H1 B0 R2.824 C282.4:110.0 D9.82 S1.00 V25.7Vs
M307 H1 R2.330 C273.8:126.9 D12.41 S1.00 V25.7Now the quetion is, how does it perform?
-
@phaedrux No change. Started heating to 220C from 30C. It faults once it gets to about 90c. Reset fault and continue heating right away. This time it gets to 180c and faults. Reset again and it'll heat the rest of the way.
-
Can you post a photo of the hotend itself?
Is the fan on when heating? Have you tried tuning the heater without the fan? -
@phaedrux I ran PID tuning again without the "F" parameter and I got
M307 H1 B0 R2.837 C252.0:103.7 D9.60 S1.00 V25.7
previously with the layer fan on it was
M307 H1 B0 R2.824 C282.4:110.0 D9.82 S1.00 V25.7
-
What does the hot block look like?
Did tuning without the F param help at all?
-
@dhusolo said in Toolboard Heater Fault:
@phaedrux No change. Started heating to 220C from 30C. It faults once it gets to about 90c. Reset fault and continue heating right away. This time it gets to 180c and faults. Reset again and it'll heat the rest of the way.
I'm not sure if it helps, but I recently had such a heating curve with the same error. The solution was a loose Crimp on the Duet Board, so I would say double-check the thermistor wiring with the crimps.
-
@siam Thanks for the suggestion. I suspected bad crimps so I re-did them just to make sure they had a good connection. The curve is due to the hotend going to a fault state and stops heating. I clear the fault and start heating again
-
@phaedrux It's an older design but for the most part the only thing changed between this and my current setup is now I'm using twin blower fans instead of 1
-
I've found out that if I heat in increments it doesn't fault. If I go directly to 210 it'll fault. It didn't fault if I set it to 80c, wait for it to heat up, set it to 160c, wait to heat up, than set to 210.
