-
Notifications
You must be signed in to change notification settings - Fork 3
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
Dallas temperature sensor request #5
Comments
Hi! The PH4502C sensor typically have a temperature output pin on breakout boards. Can you please clarify what do you mean by "Dallas external temperature sensor"? Perhaps you mean DS18B20? (I found it on a quick Google search.) |
yes, the temperature sensor is on the PCB, but if you want to compensate the ph of the measured solution, you need the temperature of the solution. In fact, measuring the temperature on the board is useless for this reason. That's why I wanted to ask you for a variation of the measurement with an external temperature sensor - the ideal candidate is the DS18B20 - it has a waterproof case, it is easily implemented in the measured pipe together with the PH probe. |
Ohhh, right! I now understand what do you mean earlier. However, I'm afraid I currently don't have an allocated budget to buy my own DS18B20 for testing, experimentations, and validation. Additionally, I just borrowed the PH4502C sensor while developing this library. So unfortunately, it may take some time to do that update. But thank you for that great idea! |
ok i understand. And does your library compensate for PH based on temperature? |
Currently, no. It does not compensate pH calculations based on temperature. |
understand, temperature is only for information, not for compesantion... thank you, have a nice day |
Have a nice day! |
Hi, thanks for the ph library. Would you be so kind as to add functionality for the Dallas external temp sensor to compensate ph from temp please? I want to use the ph probe in the pipe and measure the temperature using dallas. Thank you.
The text was updated successfully, but these errors were encountered: