IMPORTANT ISSUE with bed temp controller

Veti

for the bed its a good idea to add a thermal fuse.
like
https://de.aliexpress.com/item/32885492280.html

what kind of setup are you running?
an ssr? because normal beds do not reach that temperature.
maybe the ssr failed.

engikeneer

@jrockland maybe also post your config, hardware and firmware versions so the Duet guys have something to go on?

jrockland

@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

@jrockland Get a fully spe'd and certified TCO from a reliable source like DigiKey. They only cost about $1.

jrockland

@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.

jrockland

@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

@jrockland said in IMPORTANT ISSUE with bed temp controller:

config doesn't matter

some cooperation from your side would be appreciated.

jrockland

@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

@jrockland said in IMPORTANT ISSUE with bed temp controller:

I have to re type it by hand so I wont do the whole config file.

we mean the whole config.g. you can copy and past the entire file. no need to retype

jrockland

@Veti my machines are commercial grade, there is no "copy paste" options.

Veti

@jrockland said in IMPORTANT ISSUE with bed temp controller:

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.

jrockland

*** 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".

Board: Duet6HC
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

@jrockland said in IMPORTANT ISSUE with bed temp controller:

@Veti my machines are commercial grade, there is no "copy paste" options.

The printer uses a Duet board but you don't have access via browser to the Duet Web Control?

That seems odd.

Frederick

jrockland

@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

@jrockland

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

@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).

jrockland

@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.

jrockland

@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

@jrockland

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

well are you running in SBC mode or standalone for starters?