Heater Faults
-
@brian did you PID tune using M303?
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
-
@brian I'm not seeing any heater process parameters (M307) for the hot end heater (heater 1). Have you run a heater tune ? If you have, then did you save the results to config- override? If so, then can you post the contents of config-override. If you haven't run a heater then that is likely the problem. If you have run a heater tune, then can you capture a screen shot of the temperature graph when the heater fault occurs.
-
I also believe the entry in the g code for the hemera hotend temp sensor has a different # that Need's to be entered in config g file then run your pid.. you can find d that in the docs section I would have to look at my gcode tomorrow and see what that is or ask the manufacturer to supply that. is if someone knows it
I'm running a hemera also -
@jay_s_uk No
-
@deckingman No havent, didnt know there was one. Can u direct me to instructions? thanks
-
@ziggymanpopo In what docs? No instructions or guides of any kind came with the herera.
-
@brian OK i ran the PID and these are the results;
7/20/2023, 12:10:23 PM Warning: heater behaviour was not consistent during tuning
Auto tuning heater 1 completed after 4 idle and 45 tuning cycles in 1244 seconds. This heater needs the following M307 command:
M307 H1 R2.078 K0.256:0.263 D1.93 E1.35 S1.00 B0 V11.2
Send M500 to save this command in config-override.g
7/20/2023, 12:02:47 PM Auto tune starting phase 4, measuring with fan on
7/20/2023, 11:55:35 AM Auto tune starting phase 3, measuring
7/20/2023, 11:52:00 AM Auto tune starting phase 2, settling
7/20/2023, 11:49:44 AM Auto tune starting phase 1, heating up
7/20/2023, 11:49:39 AM M303 T0 S200 C7
Auto tuning heater 1 using target temperature 200.0°C and PWM 1.00 - do not leave printer unattended
7/20/2023, 11:45:12 AM M303 E0 S230 C7M303 E0 S230 C7
No heater has been tuned since startup
No heater has been tuned since startup -
@brian and then i ran M500 and checked the config.g override file and the info was there.
Does mean its good to go?
-
@brian said in Heater Faults:
@brian and then i ran M500 and checked the config.g override file and the info was there.
Does mean its good to go?
Providing you have M501 at the end of your config.g file then yes but best to run config.g by either calling it directly using M98 P"config.g" or by cycling the power.
When you first apply power to the printer, the statements and commands in config.g get read sequentially and acted upon. Then if you have M501 at the end of config.g, the contents of config-override.g get read sequentially and acted upon. As the name suggests, these command will override any of the same commands that came before. So when you run a heater tune, you can either put the result in config-override.g and use M501 in config.g to call that file, or you can copy and paste the result directly into config.g and not use config-override.g.
-
@deckingman great! thx so much, just checked and the M501 is the last line in my config.g, not sure if it was always there or not. I've done several small prints now without issue
-
@brian It seems that your issue is fixed. Always bear in mind that config-override.g does what it's name suggests. Multiple people have been caught out multiple times by this (including me in the past). At some point, you might want to change some part of your configuration so you edit config.g but the change seems to have no effect so you make a bigger change which also has no effect. The reason of course is that something in config-override.g is overriding the changes you make. For that reason, I don't use config- override.g. The downside is that when I run a heater tune, I have to copy and paste the result directly into config.g but personally I'd rather suffer that small inconvenience and have everything to do with configuration in one file. Of course, you may prefer the convenience but if so, just bear in mind that something you want to change might be in the override file rather than the main configuration file.
-
@deckingman well noted, and thx for the good advices
-
@ziggymanpopo were u able to find the code u mention re Hemera?
-
Assuming you used the 3mm thermistor (temp sensor) provided with the hemera
With is what I did
My g code says m503 P0 B4138 r4700
For the bed heater with a limit of 0 to 80 c
And M503 P1 x501 R 4700
M143 H1 S400 ;set temp limits for heater 1 to 400c
If you aren't using the thermistor that came with the e3d heater block that came with the hemera.. there might be a dif
Entry for the thermistor that you would have to
Get from the manufacturer that's the first thing then... so for manufacturer that sold you the heater block second I believe that there are two kinds of thermistor a pt100 and a pt1000 if you have a pt100 you might need a daughter board to get it to work or vice versa .i dont remeber wich one but ill will look...That info is in the duet documentation section attached to this forum ill look to see whick one needs the daughter board ...in case you don't know how to get to that info the "three bars" at the top left of the forum page will get you to the documentation portion of the forum. Let me know if you get stuck, also I would recommend you use the thermistor that came with the hemera....I'll post the info about the daughter board -
I believe the pt100 needs a daughter board according to the documentation
-
@ziggymanpopo I am using the pt100 daughter board, dont recall having to code anything. I am using the hemera revo, thermister/heater combo. And now the revo high flow, they dont make a 60w 12v version, just 24v, so im stuck with 12v 40w, so slower prints eg 40mm/s with 1.0 nozzle.
After doing the PID, after the fourth try, it started to perform correctly. So as of now all is well, no need to persue it further, and the supplier is sending me a replacement heater, so should be ok for a while, a long while i hope.
Thx for your help.
