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

Possible bug: false live temperature spikes in v2.22 on Pinecil #1873

Closed
builder555 opened this issue Jan 28, 2024 · 4 comments
Closed

Possible bug: false live temperature spikes in v2.22 on Pinecil #1873

builder555 opened this issue Jan 28, 2024 · 4 comments
Assignees

Comments

@builder555
Copy link

Describe the bug
Since the latest update I noticed live data occasionally spike to 400C
Screenshot 2024-01-28 at 10 40 38

To Reproduce

  1. Open PineSAM, or any other software that gets live temperature over BLE
  2. Turn on heating on pinecil
  3. Observe

You can also use this stand-alone script to get values directly:

pip install pinecil
>>> from pinecil import find_pinecils
>>> import asyncio
>>> 
>>> async def main():
>>>     pinecils = await find_pinecils()
>>>     pinecil = pinecils[0]
>>>     await pinecil.connect()
>>>     while True:
>>>         data = await pinecil.get_live_data()
>>>         print(data['LiveTemp'])
>>>         await asyncio.sleep(0.5)
>>>
>>> asyncio.run(main())

Expected behavior
Temperature rising more-less gradually

Details of your device:

  • Device: Pinecil
  • Release: 2.22E.C308FE8C
  • Power adapter being used: Ugreen 65W GaN.

Additional context
I found it to be easier to reproduce if pinecil was in sleep mode right before activating.

@Ralim
Copy link
Owner

Ralim commented Jan 29, 2024

Hia,
So this has been talked about on here before.
It came up during some of the later work on 2.22. Where basically the hardware timer, just activates at entirely at the wrong time or skips a cycle. So it means the heater stays onto the start of the adc cycle (and corrupts the measurement).
At the moment the gui just filters these out mostly as a workaround as I gave up spending time trying to mask it from happening.

I haven't yet had any new ideas on the cause, really hope its actually a software init bug but havent found it

@builder555
Copy link
Author

@Ralim do you happen to have a link to that conversation or place in the code where it's happening? Maybe I can tinker around, see what comes up.

@Ralim
Copy link
Owner

Ralim commented Jan 30, 2024

The main discussion was in #1827

Sorry I'm away from my computer for a while so not able to search in depth .

I spent a while trying to figure it out and trying different masks but didn't quite get it to stop occuring.

Doing things like speeding up the cycle hides it better but it was still occuring so didn't go too far down that path.

@builder555
Copy link
Author

i'll close this since it's a duplicate of that discussion.

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