Solved IMPORTANT ISSUE with bed temp controller
Since last update the firmware does NOT always shut down hot ends or beds when they are in FAULT and keep them active :
Woke up this morning to a 220c bed.. not only cost me couples hours of printing but also a 300$ heating bed. Got lucky it didnt catch in fire.
Since the last update it happen couples of time where the hot ends would go over their temp but I was always around to monitor them. They go in FAULT mode but keep heating up.
Please review the firmware asap, it is a major fire issue !
for the bed its a good idea to add a thermal fuse.
what kind of setup are you running?
an ssr? because normal beds do not reach that temperature.
maybe the ssr failed.
engikeneer last edited by
@jrockland maybe also post your config, hardware and firmware versions so the Duet guys have something to go on?
@Veti It is a commercial bed, reach 220c easy.. You are 100% right I will add an external safety switch in case.
I was just really lucky because if it had been one of my hot end it would had catch in fire, and I'm not sure their is thermal fuse for that..
mrehorstdmd last edited by
@jrockland Get a fully spe'd and certified TCO from a reliable source like DigiKey. They only cost about $1.
@engikeneer Duet3d 6HC, latest firmware 3.2 stable.
config doesn't matter as it went into fault but kept running. not the first time since the firmware update.
@mrehorstdmd TCO ? like those thermal fuse ? sound like a really good idea, and if they are small enough I could also stick one on top of my heat block. I will look into it.
@Veti m307 h1 r0.310 c706.9 d6.34 s1.00. I don't know why you want that.
I have to re type it by hand so I wont do the whole config file.
@Veti my machines are commercial grade, there is no "copy paste" options.
my machines are commercial grade, there is no "copy paste" options.
how do you expect anyone to analyse this problem if you provide no information?
i could state that for every other user this is working fine and must be a problem in your setup.
*** For developers:
-heat bed is ran by relays (First thing I checked was if a relay had "stick")
-firmware went into "fault" after it couldn't heat fast enough (happen often)
-instead of shutting down it kept feeding the relays.
-Did a M999 and everything went back to "normal".
Pin out: IO3.OUT
m307 h1 r0.310 c706.9 d6.34 s1.00
firmware 3.2 stable
never had this issue before last update.
fcwilt last edited by
@fcwilt not from my computer. I need the geek squad to get on their computer for that.
also lot of information is confidential so I can only quick fix manually from the firmware user page and can't copy paste anything.
Luke'sLaboratory last edited by Luke'sLaboratory
However - some explanation on why the config.g is useful here - it helps diagnose some other issues from weird or overriding settings.
Have you ran a new PID tune with the update to 3.2? The heater tuning uses feedforward algorithms to improve performance and may be one of the reasons for not heating fast enough.
engikeneer last edited by
@jrockland you can see everyone is very interested with the amount of people replying!
First thing the developers will need to know to investigate will be some steps to recreate the issue. Eg. Your config file now, and your config file & firmware version from when it worked (3.1.1?).
There are many commands in your config that could impact this (e.g. M143, which IO port you're using etc).
@Luke-sLaboratory Yes, I ran a pid tuning on everything since the new format seem to work much better and did improved stability.
I gave more info in a response (not sure how to edit my post) about m307, how the bed is connected and which port it use. not sure if anything else is relevant.
@engikeneer M143 is at 150.
latest firmware used was 3.1.1 stable.
it also happen on my other machines at least once, on hot ends. I disregarded as I was around and was busy so I just forced reset and get it going again.
Luke'sLaboratory last edited by
I know that sometimes the relay/SSR used can have unintended behaviors if not properly accounted for, they can "latch" on if too warm or if not properly configured. If you're able to provide part #'s for the relays and some pictures of wiring, etc, That could help evaluate the issue.
jay_s_uk last edited by
well are you running in SBC mode or standalone for starters?
M569 P0.1 S1
M569 P0.0 S1
M569 P0.2 S0
M569 P0.5 S1
M569 P0.3 S1
M569 P0.4 S1
M584 X0.0 Y0.1 Z0.3:0.4:0.5 E0.2 U0.4 V0.5 P5
M671 X149.0:-15.0:305.0 Y-70:180.0:180.0 S50.0
M350 X16 Y16 Z16 U16 V16 E16 I1
M92 X88.50 Y88.50 Z2085.3 E435.00 U2085.3 V2085.3
M566 X600.00 Y600.0 Z30.00 U30.00 V30.00 E10000
M203 X8000.00 Y8000.00 Z300.00 U300.00 V300.00 E10000.00
M201 X650.00 Y650.00 Z60.00 U60.00 V60.00 E6000.00
M906 X400 Y800 Z400 E400 U400 V400
M581 T0 U1 S1 C0
M558 P5 C"!io7.in" I1
G31 P100 Z2.40
M308 S0 P"temp0" Y"thermistor" A"HOT END" T100000 B4138
M308 S1 P"temp1" Y"thermistor" A"BED CORE" T100000 B4138
M308 S2 P"temp3" Y"thermistor" A"BED ACTUAL" T100000 B4138
M950 H0 C"out1" T0
M307 H0 R3.444 C172.8 D4.15 S1.00 V24.3
M950 H1 C"!io3.out" T1
M307 H1 R0.310 C706.9 D6.34 S1.00
M570 H1 P360
M143 H1 S150
M950 F0 C"out7" Q500
M106 P0 S0 H0 T100
M950 F3 C"out8"
M106 P3 S127.5
M950 F2 C"out9"
m106 P2 S255
M563 P0 S"REPLICATOR" D0 H0 F1
G10 P0 X0 Y0 Z0
G10 P0 R0 S0
@Luke-sLaboratory Yea it is the first thing I looked at. wasn't the case.
@jay_s_uk sadly SBC mode.. I know it isn't the most stable but it is the only effective way for us.
jay_s_uk last edited by jay_s_uk