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

MHP30: Temperature stability #1958

Open
Ralim opened this issue Aug 1, 2024 · 7 comments
Open

MHP30: Temperature stability #1958

Ralim opened this issue Aug 1, 2024 · 7 comments

Comments

@Ralim
Copy link
Owner

Ralim commented Aug 1, 2024

Sure, here's a revised version for better legibility:

I am having a similar problem as the OP.

I flashed the latest version of IronOS, and I consistently experienced overshoots in the temperature target. This issue improves when I limit the power, but that solution doesn't work for my application. I need to adjust the temperature in steps of ~10°C, ranging from approximately 35°C to 350°C, and I require a relatively stable temperature. Overshoots are unacceptable, and limiting the power prevents me from reaching high temperatures.

Does anyone have a possible solution for this? I also tried compiling IronOS myself. Although I managed to compile it, I'm not sure I did everything correctly. I experimented with changing the TIP_THERMAL_MASS value by increasing and decreasing it as @Ralim suggested, but it only worsened the problem.

Any help would be greatly appreciated.

Best regards,
Tomás

Originally posted by @tomasrojasc in #1461 (comment)

@Ralim
Copy link
Owner Author

Ralim commented Aug 1, 2024

@tomasrojasc

I suspect the newer "tips" for these units have different thermal properties to the older ones.
If changing the thermal mass does not give enough calibration range, you can instead swap to using the PID controller and tuning P/I/D independently.

This is currently how the Pinecilv2 is tuned for example; you will need to add this line and the following tuning numbers to the configuration.h file. Then you can adjust the P/I/D response using the tuning numbers.

@tomasrojasc
Copy link

Well, that was a super quick response. Thank you very much! I'll try that tomorrow since today is quite late already.

I'll keep you up to date.

Best regards,
Tomás

@Ralim
Copy link
Owner Author

Ralim commented Aug 1, 2024

I don't have one of the newer tops so I can't really tune much, but if your willing to test tuning and try and get a working set of settings that would be an immense help.

@tomasrojasc
Copy link

Hi, here is an update. I compiled the OS on my own but something is off... when I set the temperature, instead of having a solid red light, I have an alternating flash between red and green. I think my hex is not right. Can you help me compile correctly this? maybe a docker? I am committed to tune the PID controller but I need to be sure that my compilation works as expected.

@Ralim
Copy link
Owner Author

Ralim commented Aug 2, 2024

If the PID is really unstable you could run into that. I would suggest starting with just a P value (make the others 0).

If you open a draft-PR the github actions system will build firmware for you as another method.

@tomasrojasc
Copy link

Ohh ok I'll do it with GitHub, that is super useful, thanks. I'll let you know how it goes.

@tomasrojasc
Copy link

Hi,

I believe I need approval for this to compile. I accidentally changed the draft to an actual PR (sorry, I'm not very familiar with PRs) and then created another one, which is a draft.

Do I need authorization every time I want GitHub to compile the project? Is there a way to do it independently, like creating my own private repository with GitHub workflows for compilation? This way, I won't bother anyone, especially since tuning a PID involves a lot of trial and error.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants