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

Pinecil V2 has erroneous temp spikes in companion #1915

Open
vguttmann opened this issue May 24, 2024 · 14 comments
Open

Pinecil V2 has erroneous temp spikes in companion #1915

vguttmann opened this issue May 24, 2024 · 14 comments
Assignees
Labels
Awaiting Response Waiting for user response, if none issue will be closed.

Comments

@vguttmann
Copy link

vguttmann commented May 24, 2024

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
Screenshot_20240524-105154

To Reproduce

Details of your device:

  • Device: Pinecil V2
  • Release: V2.22E.C308FE8C
  • Power adapter being used: Lenovo 65W USB PD laptop charger
  • IronOS companion version: 1.0.0

Additional context

Other issue: aguilaair/IronOS_Companion#10

@vguttmann
Copy link
Author

vguttmann commented May 28, 2024

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.
Also, the spikes are not consistent in height.

@Ralim
Copy link
Owner

Ralim commented May 28, 2024

Hia,

Did you test with the linked PR above?
Part of this issue is to do with BLE and the adc not playing nice together (I think).
Its normally filtered out on the iron itself, but BLE has no filtering.

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.

@xam100
Copy link

xam100 commented May 31, 2024

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.
image

I did also notice random temp spikes when the iron is just laying on the table cooling down.
image

@Ralim
Copy link
Owner

Ralim commented Jun 2, 2024

@xam100 Did you test with a build from #1916 as mentioned above?

@xam100
Copy link

xam100 commented Jun 2, 2024

@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.
image

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
image

@Ralim
Copy link
Owner

Ralim commented Jun 4, 2024

Thank you for testing.
Annoying to see its still occurring for you.
I guess I have more work to do 😢 .
Will try and spend more time on it when I get some more time.

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.

@Ralim
Copy link
Owner

Ralim commented Jun 4, 2024

Hia,
If you check a chance you can test this firmware image?

Pinecilv2_EN.zip

@xam100
Copy link

xam100 commented Jun 4, 2024

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.
image

Very similar behavior is observed when re-heating the iron after an idle period (no re-pairing)
image

Those spikes max out at around 350C on the pinecil display
image

Repository owner deleted a comment from xam100 Jun 4, 2024
@discip
Copy link
Collaborator

discip commented Jun 4, 2024

@xam100
Sorry, I did not mean to delete your post. 😯

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.

@Ralim
Copy link
Owner

Ralim commented Jun 4, 2024

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 ?

@xam100
Copy link

xam100 commented Jun 4, 2024

pinecil B2 86mm Tip
lenovo 65w 20v charger but sometimes only 45w is used
image

The post accidentally deleted by @discip was showcasing another temp spike issue resulting from a sudden request of power
here are two examples when it happened

Pinecil.1.mp4
Pinecil.2.mp4

@Ralim
Copy link
Owner

Ralim commented Jun 4, 2024

pinecil B2 86mm Tip
lenovo 65w 20v charger but sometimes only 45w is used

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).

@Ralim
Copy link
Owner

Ralim commented Jun 8, 2024

Just to test; could you try the build from here and compare for you: https://github.com/Ralim/IronOS/actions/runs/9426474334?pr=1925

@discip
Copy link
Collaborator

discip commented Jul 24, 2024

@vguttmann
@xam100
Is this still an issue after the latest update #1925?
If not, please consider closing this issue. 😊

thanks in advance

@discip discip added the Awaiting Response Waiting for user response, if none issue will be closed. label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Response Waiting for user response, if none issue will be closed.
Projects
None yet
Development

No branches or pull requests

4 participants