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

Dips in ET and Stack Temp #883

Closed
MAKOMO opened this issue May 13, 2022 Discussed in #874 · 1 comment
Closed

Dips in ET and Stack Temp #883

MAKOMO opened this issue May 13, 2022 Discussed in #874 · 1 comment
Milestone

Comments

@MAKOMO
Copy link
Member

MAKOMO commented May 13, 2022

Discussed in #874

Originally posted by alikaMCR May 3, 2022
Hello everyone,
First of all, I'm not very competent at this type of troubleshooting or even these types of forum discussion. This is all very much over my head, so bear with me as I try to understand these concepts.
I am currently using a Loring s35. We recently purchased a new work laptop for monitoring our roast profiles. I downloaded the latest version of artisan and noticed that I will have these little dips in communication loss in the ET which also affect my ETROR. After a little bit of digging around in the Roast Properties - Data, I noticed that my stack temperature will display as -1 or u.u on the main display. However, sometimes it will display a reading, and when it does, I lose another temperature reading. Typically, this is the ET. Then at some point, usually quickly after, it reverts back to normal. On the previous laptop, we never had an issue like this. I attached a couple images of what I noticed.
Can anyone tell me what they think is going on? Any solutions?
Thank you very much.
Big dips
Big dips data

-Alika

@MAKOMO MAKOMO added this to the v2.6.2 milestone May 13, 2022
@MAKOMO
Copy link
Member Author

MAKOMO commented May 13, 2022

It turned out that this is caused by communication errors over a disturbed WiFi connection. In those cases Artisan receives only partial responses and fails to properly assign them to the correct channels. This has been fixed by rejecting incomplete responses and requesting the data again.

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

No branches or pull requests

1 participant