-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[Request] PWM values from M105 #642
Comments
I have to admit I haven't used pronterface in a long while, could you provide a screenshot of what you mean? |
Ah, that I've seen. Hm.. Problem is, it would have to be somehow shoved into the graph (probably as a secondary graph, since otherwise the temps would be too full), and I'm not that sure that it's a feature that so many people would really use to be honest (I mean, yeah, it's neat the first couple of times and quite handy for tuning stuff, but other than that?). Plugin yes (and no, right now there are no hooks for plugins to do that kind of thing, but that doesn't mean I won't be open to changing that), but part of the core, no. How does that thing handle multiple hotends btw? |
Also: firmware support might differ, but that's only a secondary concern, I don't want to overload the standard UI. |
ok, I'll look at plugins architecture. Meanwhile I'll try to implement this in my fork. Multiple hotends? I don't know - I cannot connect to Smoothieware from Repetier LOL |
is it possible to add PWM values from temperature responses? or it's so different for each firmware so it's not possible / not worthy? (e.g. #633 (comment))
I thought about PWM graph like in Pronterface (on the bottom of main graph)
I can do that by myself but I had to ask if there are any contraindications :)
The text was updated successfully, but these errors were encountered: