IMPORTANT ISSUE with bed temp controller
-
@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
-
@Veti said in IMPORTANT ISSUE with bed temp controller:
i would suggest that you connect it to out0
doesn't really matter in this case as its using an external relay
-
@Veti Depending on the actual thermistors they could be, but having all 3 be identical is suspect for sure! - would need validation to be 100% sure. For relay outputs, any output is fine, I prefer to use a connectorized output for my SSR ones.
-
B4138 thermistors have not been used in years. so its very unlikely that its correct.
-
@Veti Fair, I have some in a cabinet somewhere as a backup to my backup's backups.
-
@jay_s_uk Jan 14 00:00:09 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="388" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Jan 14 00:00:10 raspberrypi systemd[1]: man-db.service: Succeeded.
Jan 14 00:00:10 raspberrypi systemd[1]: Started Daily man-db regeneration.
Jan 14 00:02:30 raspberrypi DuetControlServer[14574]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 14 00:02:30 raspberrypi DuetControlServer[14574]: [info] Connection to Duet established
Jan 14 00:04:45 raspberrypi rngd[377]: stats: bits received from HRNG source: 480064
Jan 14 00:04:45 raspberrypi rngd[377]: stats: bits sent to kernel pool: 424096
Jan 14 00:04:45 raspberrypi rngd[377]: stats: entropy added to kernel pool: 424096
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2 successes: 24
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2 failures: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Poker: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Runs: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Long run: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: HRNG source speed: (min=238.614; avg=440.907; max=492.430)Kibits/s
Jan 14 00:04:45 raspberrypi rngd[377]: stats: FIPS tests speed: (min=3.285; avg=14.301; max=31.423)Mibits/s
Jan 14 00:04:45 raspberrypi rngd[377]: stats: Lowest ready-buffers level: 2
Jan 14 00:04:45 raspberrypi rngd[377]: stats: Entropy starvations: 0
Jan 14 00:04:45 raspberrypi rngd[377]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Jan 14 00:17:01 raspberrypi CRON[32185]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 14 00:25:30 raspberrypi DuetControlServer[14574]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 14 00:25:30 raspberrypi DuetControlServer[14574]: [info] Connection to Duet established
Jan 14 00:32:49 raspberrypi DuetControlServer[14574]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 14 00:32:49 raspberrypi DuetControlServer[14574]: [info] Connection to Duet established
Jan 14 00:51:21 raspberrypi DuetControlServer[14574]: [warn] Bad header CRC32 (expected 0x6d61620f, got 0x45d967fb)
Jan 14 00:51:21 raspberrypi DuetControlServer[14574]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000005)
Jan 14 00:56:55 raspberrypi DuetControlServer[14574]: [warn] Bad header CRC32 (expected 0xd5e94b60, got 0x4319b529)
Jan 14 00:56:55 raspberrypi DuetControlServer[14574]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000005)
Jan 14 01:04:29 raspberrypi DuetControlServer[14574]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 14 01:04:29 raspberrypi DuetControlServer[14574]: [info] Connection to Duet established
Jan 14 01:04:45 raspberrypi rngd[377]: stats: bits received from HRNG source: 500064
Jan 14 01:04:45 raspberrypi rngd[377]: stats: bits sent to kernel pool: 454336
Jan 14 01:04:45 raspberrypi rngd[377]: stats: entropy added to kernel pool: 454336
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2 successes: 25
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2 failures: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Poker: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Runs: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Long run: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: HRNG source speed: (min=238.614; avg=440.930; max=492.430)Kibits/s
Jan 14 01:04:45 raspberrypi rngd[377]: stats: FIPS tests speed: (min=3.285; avg=14.314; max=31.423)Mibits/s
Jan 14 01:04:45 raspberrypi rngd[377]: stats: Lowest ready-buffers level: 2
Jan 14 01:04:45 raspberrypi rngd[377]: stats: Entropy starvations: 0
Jan 14 01:04:45 raspberrypi rngd[377]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Jan 14 01:17:01 raspberrypi CRON[3031]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 14 01:30:42 raspberrypi DuetControlServer[14574]: [error] Heater 1 fault: temperature excursion exceeded 15.0°C (target 90.0°C, actual 128.2°C)
Jan 14 01:30:42 raspberrypi DuetControlServer[14574]: [info] Job has been paused at byte 8469316, reason HeaterFault
Jan 14 01:30:42 raspberrypi DuetControlServer[14574]: [info] Starting macro file pause.g on channel Autopause
Jan 14 01:30:42 raspberrypi DuetControlServer[14574]: [info] Finished macro file pause.g
Jan 14 01:30:46 raspberrypi DuetControlServer[14574]: [info] Printing paused at X182.6 Y50.4 Z40.6 U10.0 V10.0
Jan 14 01:40:42 raspberrypi DuetControlServer[14574]: [info] Cancelled printing file 0:/gcodes/MEGATOR P1.gcode, print time was 8h 15m
Jan 14 01:40:42 raspberrypi DuetControlServer[14574]: [error] Shutting down due to un-cleared heater fault after 600 seconds
Jan 14 01:59:09 raspberrypi systemd[1]: Starting Daily apt download activities...
Jan 14 01:59:11 raspberrypi systemd[1]: apt-daily.service: Succeeded.
Jan 14 01:59:11 raspberrypi systemd[1]: Started Daily apt download activities.
Jan 14 02:04:45 raspberrypi rngd[377]: stats: bits received from HRNG source: 540064
Jan 14 02:04:45 raspberrypi rngd[377]: stats: bits sent to kernel pool: 484096
Jan 14 02:04:45 raspberrypi rngd[377]: stats: entropy added to kernel pool: 484096
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2 successes: 27
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2 failures: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Poker: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Runs: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Long run: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: HRNG source speed: (min=238.614; avg=443.777; max=492.430)Kibits/s
Jan 14 02:04:45 raspberrypi rngd[377]: stats: FIPS tests speed: (min=3.285; avg=14.223; max=31.423)Mibits/s
Jan 14 02:04:45 raspberrypi rngd[377]: stats: Lowest ready-buffers level: 2
Jan 14 02:04:45 raspberrypi rngd[377]: stats: Entropy starvations: 0
Jan 14 02:04:45 raspberrypi rngd[377]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us -
@jrockland said in IMPORTANT ISSUE with bed temp controller:
Jan 14 01:30:42 raspberrypi DuetControlServer[14574]: [error] Heater 1 fault: temperature excursion exceeded 15.0°C (target 90.0°C, actual 128.2°C)
this suggest a failure of the relay
