Replies: 3 comments 3 replies
-
|
I am not a fan of this idea.
By the way: you are opening discussions, not issues. Fine for general questions but if you have a bug or a feature request (which this is), then an issue makes it easier for me not to forget about it |
Beta Was this translation helpful? Give feedback.
-
|
I considered this issue and there are methods: #4 is a valid point concerning drift of the standards but why was the temperature set point included in the SCIP command? |
Beta Was this translation helpful? Give feedback.
-
How would you achieve this for already produced and sold LibreCALs?
Temperature drift is not guaranteed to be linear. And for a calibration device, its coefficients should match the actual behavior as close as possible.
Why not? As mentioned in other discussions, I am not a big fan of software restricting the hardware and implementing such a command is easy enough. Yes, the manual specifically mentions that it is not recommended to change because of temperature drift. But if you really want to, you could calibrate with your LibreCAL, change the temperature to 50°C and then measure the LibreCAL again. This way you can create your own calibration coefficients that are valid at 50°C. I do not consider this a common use case and measuring the coefficients at various temperatures would significantly increase the production time per device. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I propose to increase the temperature setpoint to a user adjustable setting. Starting at 35C in 5C increments to at least 50C.
Reason:
1- The current setting of 35C is insufficient to buffer external heat influences from nearby equipment.
2- Calibration in the field may require higher temperatures.
Beta Was this translation helpful? Give feedback.
All reactions