Well this is new…
Any ideas what might be causing this? Improper PID loop?
Did it just go off like that? After much time? Could you post your redeem log somewhere in a pastebin?
That looks suspiciously like some kind of an accumulating overflow.
Elias, it was about an hour in to the print. I will get the redeem log of the print for you. Looking through it at the moment but I’m not seeing anything very useful. There’s an M104 S205 where I bump the temp down then back to 210, which seemed to level the temps back out.
Here’s the redeem log. http://files.mrzood.com/plugin_redeem.log
Without having looked through the log, what is your I on the PID?
pid_i_E = 0.01
For what it’s worth, I’m using the E3D v6 hot-end PID chart since that’s the hot end I’m using.
E3D v6 Hot end
temp_chart_E = SEMITEC-104GT-2
pid_p_E = 0.1
pid_i_E = 0.01
pid_d_E = 0.3
ok_range_E = 4.0
I let the thermals do their own thing and this is how it went: https://drive.google.com/file/d/0B4vlYd5QDwgBY2JIc3pPcjdxd1E/view?usp=sharing
I have not seen this before. I’ve always had rock steady temperatures using E3D ith similar settings… I’m at a loss.
Some kinda cumulative rounding error in the PID loop, maybe?
I’ll see if I can get some more useful info from the logs…
@Chris_Romey did you try running an M303 to get new PID settings? I’ve found that the default for E3D are ok, but M303 fine-tunes it and avoids this kind of over-heating over long term.
Finally have some time to play around with the PID tuning. While my PID is way off, it’s no longer doing the long over/undershoot. Still some more tuning to go.
@Elias_Bakken are there any special considerations I should be taking with the M303 values that are returned when putting them in my local.cfg?
Use m500 to store the values. Are you on devel? I saw an error retired with m500 on devel just today.
I’m on:
FIRMWARE_VERSION:1.1.8~Raw Deal
Should be ok then, but take a look in the local.cfg to make sure it was stored.