Hotend alarm heating to slow

fcwilt

Can we assume you re-booted or otherwise ran config.g after editing it?

Frederick

ecnsupplies

@fcwilt
Yes many times. Also wired thing is the auto tune takes the temp up to 205 3 times with no issues but when i manually try it. It fails. Or if i try and upload a gcode file.

Last tune

Auto tuning heater 1 completed after 3 idle and 10 tuning cycles in 882 seconds. This heater needs the following M307 command:
M307 H1 R1.782 K0.652:0.006 D9.93 E1.35 S1.00 B0 V24.1
Edit the M307 H1 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.

droftarts

@ecnsupplies See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Heaters_tuning#troubleshooting

If auto tuning fails with a message that the temperature is not rising fast enough, this indicates that either you are using too low a P value in the M303 command, or the dead time in the existing model is much too low for your heater. You can increase the dead time using the M307 command. For example, sending M307 H0 D30 will increase the dead time to 30 seconds. The actual dead time will be known after a successful auto tuning.

The whole page is also worth reading.

Ian

fcwilt

@ecnsupplies

You posted "manually try it" - exactly how are you doing that? Are any conditions different when doing that versus when tuning?

Frederick

droftarts

@ecnsupplies see https://docs.duet3d.com/User_manual/Reference/Gcodes#m307-set-or-report-heating-process-parameters

Order dependency
RRF 3.x: The M307 command must come later in config.g than the M950 command that created the heater number it refers to.

In your config, M307 H1 comes before M950 H1. Move it to after M950.

Edit: You can check what heater parameters are being used by sending M307 H1 on its own.

Ian

ecnsupplies

@fcwilt
Manually in duet 3 web interface. Use drop down and put to 200 and activate .

When using the auto tune it's m303 to m205 command and it runs all 4 tests. I gave you the last results that I put in the config.g and replaced it with the old one in there.

The test runs fine and goes up to 205 3 times with no issues.

Only fails when I do it manually or upload a gcode file to start a project.

Stupped why it works on auto test but not anyother way. It must be disabling something to run the test that's stoping it from normal use.

droftarts

@ecnsupplies it looks like you replaced you bed heater M307 with the one for your hotend. So now you’ll probably need to tune your bed again, unless you have a backup.

Ian

ecnsupplies

@droftarts
I have a backup. And the bed works fine. Just the hotend gives the error.
It's so close to getting to 205. Makes it to 185 in a min. Before it fails.

fcwilt

@ecnsupplies

I don't see any M570 commands in your config.g file.

See M570 Heater Fault Detection

Frederick

ecnsupplies

@fcwilt
Added M570 H1 P4 T15 in config file, shut down, waited 2 minutes then turned back on
It did not help! Same error at 183.6 deg.

ecnsupplies

@ecnsupplies
Swapped the m307H0 R0.532 K0.167:0.000 D13.56 E1.35 S1.00 B0 added it to hotend and put back the bed defaults all working! thank you

fcwilt

@ecnsupplies

Glad you got it working.

Just FYI the parameter P4 is less than the default which would be P5.

Frederick

ecnsupplies

@fcwilt
Ok. Will change that.

fcwilt

@ecnsupplies said in Hotend alarm heating to slow:

@fcwilt
Ok. Will change that.

I checked a couple of my printers and they were set to P300 - that is very large and I have no recollection of why I did that. It doesn't seem right at all.

Frederick

Phaedrux

@head223a said in Hotend alarm heating to slow:

switching to 24v power unit resolved the extremely slow heating issue

Was it a 12v power supply before? What voltage are the heaters rated for? Running 12v heaters at 24v is dangerous.