Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arrow next to Z Thermal Adjust, indicating ascending vs descending temp. #2098

Open
PhilBaz opened this issue Dec 27, 2024 · 5 comments
Open
Labels
💡 Type: FR Requests a new feature

Comments

@PhilBaz
Copy link

PhilBaz commented Dec 27, 2024

Requested feature:

Simple idea. An arrow next to the Z Thermal Adjust (in the temp panel) that would indicate if the temp is moving up or down.

The problem is that when the printer is (re)heating, after a previous print, it can be difficult to know whether the Z Thermal Adjust is actually moving down or up, since it takes a long time for this to turn around. It would be great to have an arrow to show the direction of travel.

Screenshot 2024-12-26 222241

Solves the following problem:

Don't know if the frame temp is actually ascending or descending.

Additional information:

Hope this makes sense... The basic theory is that bed meshing is more reliable when frame temp is moving up, rather than changing directions after the bed mesh is taken.

Let me know if more info would be helpful.

@PhilBaz PhilBaz added the 💡 Type: FR Requests a new feature label Dec 27, 2024
@meteyou
Copy link
Member

meteyou commented Dec 27, 2024

hey @PhilBaz! what should the algorithm for the symbol look like? because Moonraker sends the data at 200ms intervals, it would mostly display "the same" and then only briefly up or down. therefore, a more "advanced algorithm" would make more sense here.

@meteyou meteyou added the ❔ User Input Further information is requested label Dec 28, 2024
@PhilBaz
Copy link
Author

PhilBaz commented Dec 30, 2024

If possible maybe average of 30 or 40 seconds of Moonraker temp, then compare that against the next 30-40 seconds. If posible maybe a rolling average of n-40 to n-80 seconds, subtracted from n-39 to n-0. if that makes sense?

I think part of what you are saying is that the symbol would only show for some amount of time when the temp had not stabilized. Like it would be there when rising or falling but not when relatively stable? Would it possibly make sense to just always have the last direction indicated even if it has stabilized?

Thanks for considering the request :)

@meteyou
Copy link
Member

meteyou commented Dec 30, 2024

I think part of what you are saying is that the symbol would only show for some amount of time when the temp had not stabilized. Like it would be there when rising or falling but not when relatively stable? Would it possibly make sense to just always have the last direction indicated even if it has stabilized?

@PhilBaz no, i didn't mean to say that. i just wanted to ask what the relevant range for calculating the direction should be. if i only query to the last data point, it would probably also show 90% of the time == and not up or down, because the temperature change is much too slow.

Copy link
Contributor

Ahoi!

It looks like there hasn't been any recent updates on
this issue. If you created this issue and no longer
consider it to get merged, then please login to github
and close it. Otherwise, if there is no further activity
on this issue, it will be automatically closedwithin the
next 7 days.

Fair wind and a following sea!
~ Your friendly MainsailGithubBot

PS: I'm just an automated script, not a real sailor.

@PhilBaz
Copy link
Author

PhilBaz commented Jan 14, 2025

@meteyou I see this is going stale... Didn't know if you would like me to leave it be. Did the approach above make any sense in terms of getting a useful symbol?

@github-actions github-actions bot removed 💤 Stale ❔ User Input Further information is requested labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 Type: FR Requests a new feature
Projects
None yet
Development

No branches or pull requests

2 participants