IMPORTANT ISSUE with bed temp controller

dc42

@jrockland said in IMPORTANT ISSUE with bed temp controller:

@dc42 well that is the thing, it is inverted so it doesn't turn on as soon as I turn the board on. that is really weird. Ill have the board sent to my tech so he can look at it.

if I remove the inversion the board feed power as soon as it turn on (checked with a meter)

We really need to know what sort of relay or SSR you are using, and how you have connected it to the Duet. If it's a relay board then it may be better to connect it to an IO_x_OUT pin instead; but a SSR is better because it allows you to use PWM and hence PID.

Luke'sLaboratory

@dc42 He's talking about the actual board output, but I don't remember if i'm able to measure V_in across inactive outputs or not, since the ground is switched

jrockland

@dc42 on that specific machine we still use the old SRD-05VDC-SL-C, apparently we haven't blown them up yet. so no SSR'S on that one.

problem is probably in my gcode.

Luke'sLaboratory

@jrockland said in IMPORTANT ISSUE with bed temp controller:

SRD-05VDC-SL-C

Oh - so its a mechanical switch you were trying to drive with PWM. Well, that about "solves" it, other than inverting the heater signal. Datasheet shows ratings for 300 electrical switches/min, with only 30 mechanical switches/min allowed.

FWIW - this is why we always ask for the config.g when diagnosing issues.

Veti

as i said not having a quality ssr gives you a good chance of burning down your house

get some quality components like
Omron G3NA-210B-DC5 (10A) or Crydom D2425 (25A) or Crydom 84134000 (10A) SSR

jrockland

@Luke-sLaboratory driving relays with io's isn't the right way ? pretty sure it is what there telling us to do in the wiring diagram.. I might be wrong..

Veti

@jrockland said in IMPORTANT ISSUE with bed temp controller:

pretty sure it is what there telling us to do in the wiring diagram.. I might be wrong..

what wiring diagram?

Luke'sLaboratory

@jrockland IOs are fine, but you're trying to use a PWM signal (based on PID values) instead of a simple off/on. the mechanical relay can't keep up, and it may cause some other issues like latching on and causing the issue described. You'll need to re-enable Bang-bang, which will output either full voltage or none.

jrockland

@Veti O don't worry for me, theses machines are intended to crash so they have fire extinguishing system in place. and I don't run them in my house.

ever seen an axis with over 60lbs of torque crash ? parts goes flying XD

jrockland

@Luke-sLaboratory That would explain why it was working before the update, bang bang was probably activated before...

I will try to find how to write it properly using bang bang.

fcwilt

This post is deleted!

jrockland

@Luke-sLaboratory hmm wait if I look at my config file bang bang IS activated..

jrockland

@fcwilt you where right (before deleting your comment) but my config was set as using bang bang..

fcwilt

@jrockland said in IMPORTANT ISSUE with bed temp controller:

@Luke-sLaboratory hmm wait if I look at my config file bang bang IS activated..

Even with the slow rate of "bang bank" a mechanical relay is not a good choice.

Frederick

fcwilt

@jrockland said in IMPORTANT ISSUE with bed temp controller:

@fcwilt you where right (before deleting your comment) but my config was set as using bang bang..

I saw that someone had already mentioned that issue so I tried to delete mine.

Frederick

jrockland

@fcwilt true, probably why they where changed on the other machines

jrockland

Good news tho, the 3/4 inch aluminum bed survived (still straight). the only thing that died is the embedded magnets (n52).. Ill get those replaced then work on the gcode once the board is back.

jrockland

reprap is getting better and better, and those 6hg/3hc boards are really solid. we blown multiple motors and heaters core (I remember something crashed IN the board hard enough that the thin metal door bended and shorted the board) and it still running strong.

I tried to delete the post as it look like bang bang was deactivated, so not a firmware issue. anyway probably my bad when I wrote the gcode.