Rename heaters (thermistors).
-
I have a lot of fans scattered around my printer to cool various things in thermostatic mode using spare heater channels. I've stuck thermistors in various places and defined dummy tools so that they show up in DWC but they show up as Heater 1 (which is the hot end) then, Heater2, Heater 3, Heater 4 etc. I have a crib sheet which I have to keep referring to in order to remember which "heater" corresponds to which thermistor. Is there any way I can change these labels for something more meaningful?
-
I guess i could allow M106 to take temperature measurement channel numbers as an alternative to heater numbers. Would that help?
-
I guess i could allow M106 to take temperature measurement channel numbers as an alternative to heater numbers. Would that help?
Thanks for the offer David but I think you've misunderstood what I mean. It's not a configuration issue. I guess what I'm asking for is a way of displaying on DWC the monitored thermistors with meaningful labels.
The way I do it is to define "dummy" tools. So I have M563 P99 H2 which is the thermistor that I have stuck to one of the XY driver chips on the Duet, M563 P98 H3 which is the thermistor I have stuck to one of the driver chips on the Duex5, M563 P97 H4 which is a thermistor I have stuck to one of the XY motors (which were getting hot enough for the plastic mount to distort with the belt tension) M563 P96 H5 etc. Each of these thermistors has a cooling fan associated with it. So on DWC, I can see all the thermistors but they are called "Heater 1" then in brackets the tool numbers associated with it, (in this case the normal hot end), Heater 2 and in brackets T99 which isn't a heater of course, Heater 3 (T98), Heater 4 (T97) etc. The last one is actually labelled "Bed" so I was thinking that it might not be too difficult to have the labels "Heater 2", "Heater 3" etc configurable by the user to reflect what they actually are.
Of course, better still would be to have then displayed as sensors in the area to the right of the temperature chart, along with CPU temperature and Probe. Using dummy tools is just a fudge on my part to get them displayed.
-
I see the problem. Looks like you need a system to define additional component temperature names that are not related to heaters, just like the CPU temperature, along with the temperature sense channels used to measure them.
-
I see the problem. Looks like you need a system to define additional component temperature names that are not related to heaters, just like the CPU temperature, along with the temperature sense channels used to measure them.
That would be ideal but I'd guess it might be a lot of work to implement? I'm also conscious of the fact that most users will only have the main Duet board and it only really becomes a bit of an issue when one has the Duex5 and when this starts to get populated too. For most users, a temperature channel is associated with a heater but they can be associated with cooling fans so the term "Heater" can be inappropriate under some circumstances.
I've had a thought, but have no idea of how easy or difficult it would be to implement, which is this. If we had a "label" parameter that we could use in M305 then maybe DWC and/or Panel Due could use this label for display purposes? e.g. M305 P2 Tnnn Bnnn Rnnn LBoardTemp (or some such) when L or some other letter is the label name. If no "L" parameter is present then the display would revert to using "Heater 2" as the default. If this is feasible, could it also be extended to M106 so that fans could be labelled and displayed as "HotEnd" or "PrintCooling" or "CaseFan" etc?
Just some random thoughts.
Ian
-
I would really like to see this happen also. I plan on redoing my rostock while adding the duex 5. Adding water cooling and wanting to check temps everywhere it can be confusing if i want to watch 8 of them on the web that are not labeled properly or cant view at all. I have not just tried to read a temp not assigned to a heater. Same with fans. Being able to change the color of the trends on the chart would also be nice.
Please make this happen.
-
I too would like to see the ability to have meaningful/custom labels where possible. Not sure of the implications for the LCD panel as I do not yet have one, so selfishly happy if it is all done browser/client side as the gcode menu seems to be.
-
I'd +1 for having thermistor inputs (or temp sensing channels) being designated and viewable in a way that makes it easier to manage. I recently upgraded my corexy with a repaired duetwifi board, which has a problem with one thermistor channel, so I wanted to use the e1 thermistor with the e0 heater output, but couldn't get it to work.
EDIT as the board was faulty so ignor that, but being able to just display temp channel x would be handy, and decoupling the temperature channels from the heaters would alo be useful, could always have a table in config where you assign temp. channels to heaters.