What do these error codes mean?
DjDemonD last edited by
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
The 0x0003 code means that the last software reset occurred because you asked it to do a reset. This would be because you pressed the Emergency Stop button, or sent M999, or did a firmware update. The remaining values don't mean anything in this case, they are only relevant if the reset was caused by an exception. They are the values of certain status registers in the ARM processor, except for SP which would be the value of the stack pointer if an exception caused the reset.
DjDemonD last edited by
Thanks David, I had a heater fault and it stopped these codes were in the m122 I just wondered if they shed more light on it.
Its recently had an upgrade to a duetwifi, I had not yet tuned the heaters.
So I tuned the hotend with part fans off and got
Heater 1 model: gain 463.0, time constant 213.4, dead time 5.0, max PWM 1.00, mode: PID
Computed PID parameters for setpoint change: P16.5, I0.077, D57.6
Computed PID parameters for load change: P16.5, I1.130, D57.6
With fans on full
Heater 1 model: gain 207.6, time constant 96.4, dead time 2.0, max PWM 1.00, mode: PID
Computed PID parameters for setpoint change: P41.4, I0.430, D58.0
Computed PID parameters for load change: P41.4, I6.895, D58.0
I chose the fans on full model and saved it but with fans off it overshoots3-4 degrees and cant seem to get back down to the set point.
Would you recommend tuning with fans at 50%?
Thanks for posting figures with fans both on and off, they are interesting. I plan to have the firmware tune with heaters both on and off at some time in the future so that it can predict what effect turning on the fan will have.
You could tune with the fan at 50%, or use values in between those two sets. e.g. A340 C160 D3.5. If it shows any tendency to oscillate when the fan is off, increase the dead time.
deckingman last edited by
….....................I plan to have the firmware tune with heaters both on and off at some time in the future so that it can predict what effect turning on the fan will have.
Or how about automatically switching between the two sets of parameters when the fan is on? I have a bit of an issue in that, when experimenting with different filaments, if I want to increase the temperature by say 5 degrees during a print, I have to make sure that the fan isn't running when I do it otherwise I get a slow temperature rise fault. Of course, the Duet safety checking is doing it's job because the slow temperature rise could have been due to the heater cartridge coming out. My fans direct air down away from the nozzle but near the start of a print when the nozzle is low, air being deflected back up off the bed is unavoidable.
Yes, I intend to vary the PID parameters depending on the fan setting too.