IMPORTANT ISSUE with bed temp controller
-
@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
-
@jrockland said in IMPORTANT ISSUE with bed temp controller:
pberrypi rngd[377]: stats: bits sent to kernel pool: 484096
Jan 14 02:04:45 raspbMy take from this is that it shut down the duet after 10 min of heater fault, and if the relays need a high signal to turn off, by having no signal (from a shut down duet) it just stayed on and caused the issue.
-
@Veti didnt understand the first part but Ill change it to out.0
-
@jrockland said in IMPORTANT ISSUE with bed temp controller:
didnt understand the first part
it means your bed will be reporting the wrong temperature.
it will display 100C but it wont be 100C -
@Luke-sLaboratory I dont know what SSR mean, but they look like normal relays to me.
-
@jrockland said in IMPORTANT ISSUE with bed temp controller:
SSR
Solid State Relay.
Using cheap ones is a sure way to burn your house down. -
@jrockland https://duet3d.dozuki.com/Wiki/Connecting_thermistors_or_PT1000_temperature_sensors - Relevant documentation.
I'd take a serious look at what relays you are using (whether they're SSR's or traditional) the correct switching frequency, which thermistors you actually have in all of your machines, and the configuration of using a high Signal from the duet to turn relays off.
Preferably you'd drop the frequency to ~10hz (by adding a Q10 to your M950 where you set up the output for out3 (or out1)), and reconfigure/aquire new relays that require a high signal from the duet to turn on. That way, if your duet goes offline for whatever reason, your relays will not turn on.
Next I'd definitely recommend high-quality SSRs. Cheap/underrated/undercooled ones will latch on and have the exact behavior that may have caused this issue in the first place. Thats why I was looking for specifics on the relays used.
