Heater Fault
-
@dave-parry Ok Got it done. Installed 3.3 using bossa. Then tried to install 3.4.0beta 5 and just got the same problem. So I erased again with bossa and used YAT to install 3.4.0 Beta 5 and it worked. However I would like to know why it won't work through DWC as normal. If I have to do it with Bossa it means I have to take the heated bed off do the update, re-install and then recalibrate. IfI have to do that each time I want to update I will have to extend the erase pins so they are acessible.
-
@dave-parry After all that it hasn't cured the original fault. Still getting hot end heater errors as soon as I start a print. Do a heater reset, reset temp, wait for it to get back to set temp, restart and it prints fine. Don't think its the problem but tomorrow I will change the sensor and heater cartridge and see if it helps.
-
Maybe a redundant question, but you say that you store the pid calibration with M500.
Then it's saved to the config-override.g.
Do you load that in the end of the config.g with M501?
-
@gixxerfast yes it's in the file.
-
@dave-parry It seems it was a problem with the V6 hotend.
Took it apart, cleaned and re-installed and its so far been OK.
I think the block may have loosened from the heatbreak a little bit.
But would still like to get to the bottom of the update problem. -
@dave-parry ok, thanks for the update about the heater fault. Will be interesting to see if it is now fixed over repeated uses.
We can test the upgrade again when the next beta comes out.
-
@t3p3tony Thanks Tony.
-
@dave-parry Have got the heater error problem back again.
It seems that the voltage drops when the stepper motors run, but the power supply is a 24v 25w meanwell power supply, so should be more than enough power. I am going to check connections but just thought I have the hot end fan connected to a always on output, as that is how it was on my duet 0.8.5 board. Should it be on a thermostatically controlled fan output? -
@dave-parry are you sure you mean its only a 25w 24v PSU?
-
@jay_s_uk Sorry 25A
-
@dave-parry said in Heater Fault:
I have the hot end fan connected to a always on output, as that is how it was on my duet 0.8.5 board. Should it be on a thermostatically controlled fan output?
this can be either, and its 99% not the cause of the power supply voltage dipping.
Does M122 report voltage drops?
-
@t3p3tony Will check tomorrow Tony been out tonight and only just got in.
-
@t3p3tony results of M122 and error message
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta5 (2021-10-12 13:54:53) running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9P6M2-NWNS4-7J1DA-3SJ6M-TA2ZK
Used output buffers: 1 of 24 (22 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 70336 of which 0 recycled
Never used RAM 17804, free system stack 134 words
Tasks: NETWORK(ready,27.3%,245) HEAT(notifyWait,0.0%,209) Move(notifyWait,0.0%,312) MAIN(running,72.7%,442) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:08 ago, cause: software
Last software reset at 2021-10-19 10:55, reason: User, GCodes spinning, available RAM 17804, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 42.8, current 43.6, max 43.7
Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: pos 17561,standstill, SG min/max 0/152
Driver 1: pos 17561,standstill, SG min/max 0/160
Driver 2: pos 17561,standstill, SG min/max 0/145
Driver 3: pos 0,standstill, SG min/max n/a
Driver 4: pos 0,standstill, SG min/max n/a
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2021-10-19 10:57:50
Cache data hit count 4294967295
Slowest loop: 5.92ms; fastest: 0.17ms
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 3.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 110993ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4, completed 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 -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: 8.40ms; fastest: 0.04ms
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 duplex19/10/2021, 10:57:47 Error: Heater 1 fault: temperature excursion exceeded 15.0°C (target 210.0°C, actual 180.8°C)
-
@dave-parry Its giving this error everytime I drive the axis motors.
The motor currents are all set at 1000 mA. -
@dave-parry said in Heater Fault:
Supply voltage: min 23.9, current 24.1, max 24.2,
no voltage drops reported so I don't think its that. The heating error only happens when you drive the axis motors? I assume you moved the axis motors before sending M122?
-
@t3p3tony yes but I did have a report from before here it is.M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta5 (2021-10-12 13:54:53) running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9P6M2-NWNS4-7J1DA-3SJ6M-TA2ZK
Used output buffers: 1 of 24 (13 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 70336 of which 0 recycled
Never used RAM 17804, free system stack 134 words
Tasks: NETWORK(ready,25.7%,245) HEAT(notifyWait,0.0%,311) Move(notifyWait,0.0%,314) MAIN(running,70.7%,442) IDLE(ready,3.6%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:24 ago, cause: software
Last software reset at 2021-10-19 10:55, reason: User, GCodes spinning, available RAM 17804, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 42.3, current 43.1, max 43.3
Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: pos 32435,standstill, SG min/max 0/70
Driver 1: pos 32508,standstill, SG min/max 0/98
Driver 2: pos 32530,standstill, SG min/max 0/69
Driver 3: pos 0,standstill, SG min/max n/a
Driver 4: pos 0,standstill, SG min/max n/a
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2021-10-19 10:56:06
Cache data hit count 894906521
Slowest loop: 5.88ms; fastest: 0.15ms
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 3.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 3783ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 3, completed 3, hiccups 0, 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 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.3
=== 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: 8.15ms; 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 -
@dave-parry said in Heater Fault:
@dave-parry Ok Got it done. Installed 3.3 using bossa. Then tried to install 3.4.0beta 5 and just got the same problem. So I erased again with bossa and used YAT to install 3.4.0 Beta 5 and it worked. However I would like to know why it won't work through DWC as normal. If I have to do it with Bossa it means I have to take the heated bed off do the update, re-install and then recalibrate. IfI have to do that each time I want to update I will have to extend the erase pins so they are acessible.
You may have an old version of Duet2_SDiap32_WiFiEth.bin in the /firmware folder.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
This post is deleted! -
Its fine you are on b5 now so we will see if you can upgrade properly when b6 comes out
Looking back through the thread I realised that you have not done a heater tune since the beginning of the issue so please run M303 again with the fans setup as you plan to have them. if you use M303 T method to do the tuning then it will take into account the part cooling fan if you have one.
-
Will do Tony.
It is printing now, but the temp trace is all over the place.
I did do a heater tune this morning before I started, I used M303 H1 S240 followed by M500 but will use your method when the print finishes.
