Bed timed out - Not able to resolve
Every print and preheat I get to temp, it stabilizes, floats +/-0.1° like I would expect, and then after about 5 minutes I get this message, and it shuts the bed down.
I have run a PID Autotune for the temp I am running and it finishes out fine and gives me the values which i saved to the config-override with M500.
I am at a loss at this point. I have added an M307 to my config with the proper PID's but nothing seems to be working and I can't find anything similar searching.
Phaedrux last edited by
After you have saved the auto tune results with M500, did you add M501 to the end of config.g to load them at startup?
What values did you get from the tune?
What are your thermistor parameters?
What type of bed heater is it?
What firmware version and duet board?
What firmware are you running? The "bed timed out" and "Message from Duet firmware" are not standard messages from RepRapFirmware.
M307 H0 A217.9 C661.8 D0.6 V24 B0 Is the result returned.
The heater parameters are-
M305 P0 T100000 B4138 C0 ; Set thermistor + ADC parameters for heater 0
M143 H0 S150 ; Set temperature limit for heater 0 to 255C
M307 H0 A217.9 C661.8 D0.6 V24 B0 ; Set PID's for 110°C
its a e3d BigBox bed with a standard e3d semitec thermistor.
Im running Duet2Firmware-2.02 downloaded on 1-2-19 on a Duet 2 Wifi.
@dc42 I'm having a similar discussion with Tony on the e3d-toolchanger group (thats what this is running) maybe I should just redo my firmware?
I suspect that the "bed timed out" message is in one of the macro files in /macros or /sys on the SD card. Can you locate it?
That's what I was thinking too. I downloaded both and did a project search through Atom and was not able to find it in either folder.
I am happy to send zip files over if you would like to see them.
Please search the GCode file you are trying to print for the "bed timed out" message. It may be a line like:
M117 bed timed out