-
-
Notifications
You must be signed in to change notification settings - Fork 723
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
Pinecil V2 has erroneous temp spikes in companion #1915
Comments
Thanks to the help of the Companion devs, I was able to figure out that it's indeed an issue with IronOS. Interestingly, the spikes only appear when the iron is actively heating - not when it's in cooldown or idle. |
Hia, Did you test with the linked PR above? This has been a thing around since BLE support was added (roughly, don't have an exact timeline and chat is busy to search back in). If I build with BLE stripped from the build the issues disappear for me here, but would love any other observations. Unsure what the root cause is though, as tracing the raw register read from the ADC does have corrupted data. Lightly suspect its timer + BLE interrupt fighting but unsure. |
Hi I have encountered a similar issue with a similar setup
I wasn't able to reproduce it in the same manner but I did see it happen during normal usage. I did manage to reproduce temperature spikes by playing (contacting) with the solder tip using tweezers, and that spike did not reflect on the pinecil display. I did also notice random temp spikes when the iron is just laying on the table cooling down. |
@Ralim just tried using this build , and yes it seems to be reproduceable. Firstly a spike appears during the first power on, right after flashing, resetting settings and re-paring. Afterwards, the issue comes back occasionally. Strangely, the spikes don't always reflect on the bluetooth web page but seem to always show on the display, i.e. the pinecil display can be seen briefly temp spiking to 300-310 but the graph doesn't always have time to show that spike |
Thank you for testing. The screen on the Pinecil is showing a very,very lightly smoothed rolling average; where as the BLE will point-in-time sample the unfiltered reading so depending how often the issue arises will vary what you see on each. |
Hia, |
Hi, tested 1069e46 04-06-24, three good findings. Random temp spikes did not show up this time. Temp spike after pairing is still noticeable and is corelated with high (45W) sustained power output. Very similar behavior is observed when re-heating the iron after an idle period (no re-pairing) |
@xam100 Unfortunately on my device it showed up as if this post was entered twice, so I removed the latter. But for some reason both posts vanished. I’m so sorry. Please forgive me. Hope you will find the references you used again. |
Okay this is good. These temperature spikes are likely something else (PID) can you confirm what power source and what tip your using so I can replicate these ? |
pinecil B2 86mm Tip The post accidentally deleted by @discip was showcasing another temp spike issue resulting from a sudden request of power Pinecil.1.mp4Pinecil.2.mp4 |
Aha, okay I'll have a look at tuning. The wattages displayed are only estimated so take them with a grain of salt. The system is tuned to overshoot slightly on the readback when you do a large temp change like that but it shouldn't overshoot that much. (Some overshoot is desireable to help bring the outside tip temp up faster since the temp sensor is inside the tip and leads the outside). |
Just to test; could you try the build from here and compare for you: https://github.com/Ralim/IronOS/actions/runs/9426474334?pr=1925 |
@vguttmann thanks in advance |
Describe the bug
When using IronOS companion, sometimes the tip temperature spikes up to 450C for one time point (see screenshot). I'm not sure whether this is an IronOS or a companion bug, therefore I'm opening an issue in both repos
To Reproduce
Details of your device:
Additional context
Other issue: aguilaair/IronOS_Companion#10
The text was updated successfully, but these errors were encountered: