IMPORTANT ISSUE with bed temp controller
-
*** 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 stablenever had this issue before last update.
-
@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
-
@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. -
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.
-
@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).
Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
i3 clone with a bunch of mods -
@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. -
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.
-
well are you running in SBC mode or standalone for starters?
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
G90
M83M569 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 V400M208 X0 Y0 Z0 U0 V0 S1
M208 X280 Y140 Z120 U120 V120 S0
M574 X1 S1 P"!io6.in"
M574 Y1 S1 P"!io0.in"
M574 U1 S1 P"!io2.in"M581 T0 U1 S1 C0
M558 P5 C"!io7.in" I1
G31 P100 Z2.40M308 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
M140 H1
M570 H1 P360
M143 H1 S150M950 F0 C"out7" Q500
M106 P0 S0 H0 T100
M950 F3 C"out8"
M106 P3 S127.5
M950 F2 C"out9"
m106 P2 S255M563 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.
-
@jrockland said in IMPORTANT ISSUE with bed temp controller:
M950 H1 C"!io3.out" T1
seems odd to invert an output
and you have no frequency set which means that SSR/relay would be running way faster than is good for itOwns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jrockland said in IMPORTANT ISSUE with bed temp controller:
@jay_s_uk sadly SBC mode.. I know it isn't the most stable but it is the only effective way for us
Can you provide the contents of /var/logs/syslog for the day it happened on?
May be something of interest in there...Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jay_s_uk not a programmer here.. but I figure it is inverted because of the "!" ? Ill check that out.
-
Wait - this means that to have the bed be "off" - the duet needs to run with out3 "on"
so if the duet doesn't send signal (or if a wire gets cut, loose, etc) the relays will be turned on?
Otherwise, yeah, the frequency thing is definitely a non-recommended setup as well - Could @jrockland confirm that they're SSR's and not "traditional" relays?
-
@jrockland Yes - the ! is to invert the signal, in this case, for the duet to turn "on" the expected output, it needs to turn "off" the on-board output.
-
which definitely isn't very fail safe...
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jrockland said in IMPORTANT ISSUE with bed temp controller:
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 B4138those settings rre incorrect.find the correct beta value in the thermistor documentation.
M950 H1 C"!io3.out" T1
i would suggest that you connect it to out0
-
@jay_s_uk Agreed, this makes me anxious
