Try to use the RTD calculator but I'm not able to use my own R_Ref value. Whatever value I try to use the calculator always replace it with the calculated value instead. The same goes for R_Bias.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Try to use the RTD calculator but I'm not able to use my own R_Ref value. Whatever value I try to use the calculator always replace it with the calculated value instead. The same goes for R_Bias.
Hi Sven Gustafson,
When you enter your own R_REF or R_BIAS value and do not run the algorithm, the tool recalculates the error, power consumption, etc., based on the values you entered.
If you are using a low-side R_REF, you can enter any value of R_BIAS and the tool will use this value of R_BIAS when it runs the algorithm
For a high-side R_REF, the tool automatically bypasses the user-entered value of R_BIAS and instead calculates a value based on the other parameters.
In both cases, if you want to run the algorithm, the tool automatically determines the value of R_REF and uses this in lieu of the user-entered value
Was your goal to enter values of R_REF and R_BIAS and have the algorithm determine a valid solution (assuming one exists)? There is a possibility this can be implemented, so let me know if this is the case.
On that note, why would it not be acceptable to run the algorithm and let the tool determine the values of R_REF and/or R_BIAS? The answer to this question will help us determine if additional modifications are necessary to accommodate other use cases
-Bryan
Thank you Bryan, it wasn't obvious that you shouldn't run the algorithm after you inserted the values, now I know.
I try to use the tool to investigate an existing design.
Hi Sven Gustafson,
Thanks for the additional information. We should be able to implement this change.
Please check a future revision for this update. I will try to get this completed in the next week or so
-Bryan