IMPORTANT ISSUE with bed temp controller
-
@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.
-
@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
-
@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.
-
This post is deleted! -
@Luke-sLaboratory hmm wait if I look at my config file bang bang IS activated..
-
@fcwilt you where right (before deleting your comment) but my config was set as using bang bang..
-
@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
-
@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
-
@fcwilt true, probably why they where changed on the other machines
-
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.
-
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.
