M307 in startup gcode gives heater over-powered warnings
-
I want to experiment with custom M307 commands for my various slicer profiles so i added some to my startup gcode, but I now get annoying warnings at the start of every print.
Warning: Heater 0 appears to be over-powered. ..... Warning: Heater 1 appears to be over-powered. .....I have defaults in config.g but no M501 at the end.
I thought maybe adding some combination of M500, and M502 to my startup gcode would make the warnings go away, but I've had no luck.
Is there nothing i can do to make the warning go away?
-
The warning is about the (available) power and potential maximum temperature of left on at 100% power due to a fault. so you'll need to change the heater (or heatloss) to get rid of the warning
-
@bearer said in M307 in startup gcode gives heater over-powered warnings:
The warning is about the (available) power and potential maximum temperature of left on at 100% power due to a fault. so you'll need to change the heater (or heatloss) to get rid of the warning
I'm pretty confident that not the issue, as the parameters used are from pid tuning the heaters using M303.
Additionally If I remove the M307 from my startup gcode and put them in config.g (the exact same commands) i get no warnings.
It seems like the firmware doesn't like Having M307 in config.g and in the gcode file for a print at the same time.
I should add I've validated it's using the parameters set in the start up gcode, even though it gives the warning.
I think either i'm missing something, or this is an edge case bug.
-
-
@Veti said in M307 in startup gcode gives heater over-powered warnings:
That's a little ambiguous, because as I mentioned above if I set them in config.g I get no warning.
-
update to 3.2 and you wont get the message
-
@Veti said in M307 in startup gcode gives heater over-powered warnings:
update to 3.2 and you wont get the message
What does 3.2 do to make them go away?
-
introduce a new heater tuning
-
@Veti said in M307 in startup gcode gives heater over-powered warnings:
introduce a new heater tuning
That seems unlikely. If it was related to the algorithm, i'd expect it to complain no matter how the parameters where loaded.
-
For @dc42 or any of the other developers you might look at this.
Board: Duet WiFi 1.02 or later + DueX5 Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1) Duet WiFi Server Version: 1.23 -
@DanS79 said in M307 in startup gcode gives heater over-powered warnings:
Additionally If I remove the M307 from my startup gcode and put them in config.g (the exact same commands) i get no warnings.
You still get the warning, it's just a one time thing at boot instead of each print
-
@bearer said in PanelDue 7i - warning message at start-up:
const float noWarnTemp = (temperatureLimit - NormalAmbientTemperature) * 1.5 + 50.0; // allow 50% extra power plus enough for an extra 50Cnot sure if that panned out for that guy, but the issue is the firmware has calculated the theoretical maximum temperature for the heater if left on, and if that exceeds the formula above the warning is issued ... so in theory increasing the allowable temperature so the noWarnTemp becomes higher than what the warning is for then no warning (maybe)
https://duet3d.dozuki.com/Wiki/Gcode#Section_M143_Maximum_heater_temperature
-
@DanS79 The warning is just that. It's a warning that the heater is over powered and so, if a MOSFET was to fail, there is a potential fire hazard. IIRC, it was introduced a few years back, along with a couple of other features when a user did in fact have such a fire, and complained that the firmware did not report that the hazard existed. IIRC, the other features which were introduced at the same time were checking for erratic temperature excursions which might indicate that a heater cartridge had fallen out or other such potential faults.
So you might find a way to remove the "annoying" warning, but you'll be left with the fundamental problem of using over powered heaters and the potential fire hazard that causes. You might find that a fire will be somewhat more annoying than the warning message. If I were part of the Duet team, and because we live in a world of litigation, I would most certainly not remove what is essentially a safety feature from the firmware because a user with over powered heaters found the warning message annoying.
-
@DanS79 I would also add that you won't see the warning when in config.g because it is run at boot, so dwc hasn't started yet so you won't see the message. If you run M98 P"config.g" from console, it will re run your config file and you will see the warning message.
You will also have seen the warning message when you originally tuned the heaters.Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
i3 clone with a bunch of mods -
@engikeneer said in M307 in startup gcode gives heater over-powered warnings:
@DanS79 I would also add that you won't see the warning when in config.g because it is run at boot, so dwc hasn't started yet so you won't see the message. If you run M98 P"config.g" from console, it will re run your config file and you will see the warning message.
You will also have seen the warning message when you originally tuned the heaters.I tried the M98, and did indeed get the warnings. Yes, I got them when i did the pid tune, but thats really the only place I would expect to see them.
Everytime they get loaded is almost like annoyware imo.
-
@DanS79 said in M307 in startup gcode gives heater over-powered warnings:
Everytime they get loaded is almost like annoyware imo.
Does the seatbelt light in your car annoy you too?
-
@Phaedrux said in M307 in startup gcode gives heater over-powered warnings:
Does the seatbelt light in your car annoy you too?
Yes, and while i can't disable the light I did disable the annoying chime....
-
did you even try M143 or are you confident enough to complain without trying it?
-
he just wants to complain
-
This post is deleted! -
@bearer said in M307 in startup gcode gives heater over-powered warnings:
did you even try M143 or are you confident enough to complain without trying it?
I did the math and that would require raising the HE limit to 582°C. That's well above even the theoretical maximum recommended by the manufacture, so i disregarded that as an option.
-
@Veti said in M307 in startup gcode gives heater over-powered warnings:
he just wants to complain
You can shove off!
-
@DanS79 said in M307 in startup gcode gives heater over-powered warnings:
I did the math and that would require raising the HE limit to 582°C. That's well above even the theoretical maximum recommended by the manufacture, so i disregarded that as an option.
In that case, the estimated hot end temperature reached if you were unlucky enough to get a stuck heater would be even more above the manufacturer's recommended limit, probably enough to melt the heater block if it is aluminium.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@DanS79 said in M307 in startup gcode gives heater over-powered warnings:
@bearer said in M307 in startup gcode gives heater over-powered warnings:
did you even try M143 or are you confident enough to complain without trying it?
I did the math and that would require raising the HE limit to 582°C. That's well above even the theoretical maximum recommended by the manufacture, so i disregarded that as an option.
lol, its not gonna change the teperature to set the m413 before and after m307 ... you'll still have an overpowered heater if you do or you don't.
think of it like printing a dummy seatbelt clip to get rid of the pesky sounds in the car...
-
@dc42 said in [M307 in startup gcode gives heater over-powered warnings]
In that case, the estimated hot end temperature reached if you were unlucky enough to get a stuck heater would be even more above the manufacturer's recommended limit, probably enough to melt the heater block if it is aluminium.
It's an E3D copper block, so its recommended max is 500°C.
