[Solved] Atlas EZO-pH calibration
Mycodo Version: 8.8.5
Dr G...I hope all is well. To be young and have your energy!
Observation/Question about the Mycodo Atlas EZO pH 3-point calibration. The low, mid, high calibration order appears to always produce a 2-point mid/high calibration stored in the EZO pH and not the expected 3-point low/mid/high. I believe this is because the EZO firmware wipes out all calibration settings when it encounters a cal,mid,n.nn command.
“...Issuing the cal,mid command after the EZOTM pH circuit has been calibrated, will clear the other calibration points. Full calibration will have to be redone.”
"...Doing a mid-point calibration after the pH circuit has been calibrated will clear the other calibration points. Hence the mid-point must be done first."
I went through the Mycodo 3-point calibration routine (including deactivating the device and clearing existing calibration) and, upon conclusion, put the board into UART mode (datasheet says changing comms mode has no effect on stored calibration values) and used the Atlas Arduino code (see cite) to query the board. The cal,? command produces a cal,2 response instead of the expected cal,3.
When I perform the calibration via UART in mid-low-high order, cal,? interrogation yields the expected cal,3 result. So I think the solution is to always perform the midpoint calibration first.
Note that this doesn't make a jot of practical difference in my measurements to date (new probe though), but my data may end up in a publication and/or tort so I'm validating/documenting every sensor calibration and measurement procedure out the wazoo.
Thank you for all your efforts!
The calibration order was modified recently before you made your post, yesterday.
Ah! Thanks Kyle.
You're welcome. The change is not yet available. It will be in the next release.
I was literally about to post about this. Thanks for bringing it up @mugwump!
@frank The modification had already been made before the question was brought up, I merely pointed to the yet to be released edit.
@kylegabriel thanks! I only posted because I was calibrating mine 15 min ago and noticed the Atlas directions were different. I really appreciate all of your work with this platform!
You're welcome. Since there's a lot of activity on this, I'll go ahead and make a release tonight so you all can start using the fixed code. I tested it to work last night.