Colors for temperature graphs

[xeddog]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No problem
Describe the solution you'd like
A clear and concise description of what you want to happen.
Color changing temperature graphs for nozzle and bed temps.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Are there any????
Additional context
Add any other context or screenshots about the feature request here.
I think I would like to see color changing temperature graphs for nozzle and bed temps. Something along the lines of :
Blue when the temperature is initially set and up until the next stage
Green when the temperature is + or - 2 degrees of target temp.
RED when the temperature is + or - 5(?) degrees from the set temperature after reaching set temp and stabliizing

This could potentially show the need for running PID tune, or a potential problem coming up, etc. with just a couple of glances at the dashboard.

[StefanCohen]

I had exactly this in mind early on and I still think it is a good idea. Take a look here: https://community.octoprint.org/t/dashboard-plugin/11536/46?u=stefan_cohen

I might give it a try after I've sorted out the fullscreen layout.

[Naugrimohtar]

How about similar for the CPU temp meaning change when getting high?

[StefanCohen]

@Naugrimohtar I like that but how do we define what "High" is for the CPU? Are there themal limits for the RPi specified somewhere that we can use or do we need a user setting for this?

[xeddog]

Maybe this will help. From https://www.raspberrypi.org/documentation/hardware/raspberrypi/frequency-management.md

"For Raspberry Pi 3 Model B+, the PCB technology has been changed to provide better heat dissipation and increased thermal mass. In addition, a soft temperature limit has been introduced, with the goal of maximising the time for which a device can "sprint" before reaching the hard limit at 85'C. When the soft limit is reached, the clock speed is reduced from 1.4GHz to 1.2GHz, and the operating voltage is reduced slightly. This reduces the rate of temperature increase: we trade a short period at 1.4GHz for a longer period at 1.2GHz. By default, the soft limit is 60°C, and this can be changed via the temp_soft_limit setting in config.txt."

[Naugrimohtar]

Agreed! I googled briefly and saw that the RPi 3 scales speed at 85C core temp. Also read that the 3b+ scales as low as 60-70c. I also saw and article that detail was changed to 60c but could be overridden ( raspberrypi/firmware#1014 (comment) ) Perhaps user settable with 57c yellow and 65c red to start? I wonder if there is a way to query the OS for throttle temps?

…

On Sun, Oct 6, 2019 at 7:45 AM StefanCohen ***@***.***> wrote: @Naugrimohtar <https://github.com/Naugrimohtar> I like that but how do we define what "High" is for the CPU? Are there themal limits for the RPi specified somewhere that we can use or do we need a user setting for this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#40>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG3BMWAHRBGYH4JDMDL7UMDQNHMVVANCNFSM4IZAUJIQ> .

[StefanCohen]

Keep in mind that OctoPrint might just as well be running on a Xeon instead of ARM so we will need user settings for the CPU thresholds but might set them to something like 60 for yellow and 80 for red by default regardless.

The hotend and bed thresholds are different and should probably behave like @xeddog described above.

[xeddog]

I didn't think about that. All the different processors would add a few thousand wrinkles, wouldn't it.

[Naugrimohtar]

Wrinkles yes but those with other platforms might not care to monitor their core temp so perhaps in addition to being able to specify the temps, we could slow enabling:disabling of that ‘widget’, and the other widgets too?

[xeddog]

But if they did care to, then the author could potentially be swamped with detailing the temperature characteristics of hundreds of processors. Maybe an option might be to let you specify your own temperatures.

[LMS0815]

What's about providing a user defined field for CPU?
And stick to the original idea.

Blue when the temperature is initially set and up until the next stage
Green when the temperature is + or - 2 degrees of target temp.
RED when the temperature is + (or - 5? I would regard low as OK...)

[StefanCohen]

WIP for 1.11.0:

It changes to red above the critical threshold. Will work on the temp gauges next.

[StefanCohen]

I added the cpu frequency to the CPU widget as that is relevant to the temp reading and throttling:

[StefanCohen]

WIP:

There is now a setting to enable the temp gauge coloring (default off). There is also a temp deviation setting (default 10C). It works like this:

• Blue if target = 0
• Blue below target - deviation
• Green between target - deviation and target + deviation
• Red above target + deviation.

[Naugrimohtar]

Excellent!

…

On Sat, Oct 12, 2019 at 12:12 PM StefanCohen ***@***.***> wrote: WIP: [image: Screenshot 2019-10-12 at 19 04 37] <https://user-images.githubusercontent.com/33824565/66705149-696e8600-ed23-11e9-9710-6e9372a0ed1a.png> [image: Screenshot 2019-10-12 at 19 04 19] <https://user-images.githubusercontent.com/33824565/66705150-6e333a00-ed23-11e9-8b3b-1daa528da0d1.png> There is now a setting to enable the temp gauge coloring (default off). There is also a temp deviation setting (default 10C). It works like this: - Blue if target = 0 - Blue below target - deviation - Green between target - deviation and target + deviation - Red above target + deviation. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#40>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG3BMWGLWELANQ33CAV4APDQOIAOXANCNFSM4IZAUJIQ> .

[StefanCohen]

Fixed in 1.11.0