More detailed heater-fault :-)
A Former User last edited by A Former User
after spending a few afternoons (I will not tell you at this place but be assured it was quite some time I´ve invested) to check, why I could tune the heatplate to 120°C but after tuning when manually heating not go over 100°C IT TURNS OUT (now don´t you laugh out ther ) that within my filament-config.g I already copied another M143 with 100°C max for PETG (which I had loaded at that time *slap on the forhead no icon avaliable * ) on top of the m143 with 120°C in the general config.g !
What a relief if - at last - finally one finds out
So that brought me to thinking - WHAT IF - the heater would not only throw in the console: heaterX-fault BUT rather tell me "reached Hx Sxxx Ax" e.g. like it was configured in config.g (or as in my case filament-config.g) via M143 so to know WHY the heaterfault was issued. Or could it be reflected in the debugging via M111?
I know my errors lead me to ask for a lot of feature-requests but hey, maybe it is not so hard down the road and it helps others too?
This is obviously not an urgent thing - I am quite aware that there are more important requests out there.
Good thing is: Because of all the waiting of the plate to get hot while tryin 3.1.1, 3.2RC2 & 3.2Alpha we played around with the 3*I/O-heatplate to check out series-/parallel/only-one-loop(noseries/noparallel) and did the calculation and now it is fed with twice as much A so is way faster -> At least some learning!
Also will start to try out M111
EDIT: Maybe in a first step which of the 3 "monitor" (0/1/2) for the "heater" was escalating might help to diagnose, because I assume that within M143 the P parameter is referring to it? (https://duet3d.dozuki.com/Wiki/Gcode#Section_M143_in_RRF_3_01RC2_and_later)
Seeing within DWC-object-model 3 monitors for each heater