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

Bad Temperature readings do not update correctly #7

Open
blu006 opened this issue Sep 9, 2020 · 4 comments
Open

Bad Temperature readings do not update correctly #7

blu006 opened this issue Sep 9, 2020 · 4 comments

Comments

@blu006
Copy link
Member

blu006 commented Sep 9, 2020

A bad temperature reading updates to 0C instead of showing as an invalid number (XX or the like).

@blu006
Copy link
Member Author

blu006 commented Sep 14, 2020

To clarify, this means that the temperature sensor is missing from the controller and reads as 0C on the website.

@blu006
Copy link
Member Author

blu006 commented Sep 17, 2020

It is noted that commit MAGLaboratory/haldor@cd1a0e7 changed the handling of a missing temperature sensor from "--" to "XX" which may or may not have changed the website behavior.

@blu006 blu006 closed this as completed Sep 29, 2020
@blu006 blu006 reopened this Sep 29, 2020
@blu006
Copy link
Member Author

blu006 commented Dec 1, 2020

it should be further noted that development efforts made did not correct this problem completely.

The JS updater now turns XX into NaN when updating the synoptic view under temperature sensor failure conditions.

@blu006
Copy link
Member Author

blu006 commented Feb 19, 2021

JS updater still turns XX into NaN.

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

1 participant