Calibration failed for PH?

[rkelman]

I tried to calibrate my PH and the settling number stays at 1228. At the end of the process I get "Calibration failed" Any Idea's? I am running the beta firmware.

 

[aquamanic]

It sounds like you're not "setting" or storing the values between the 7.0 and 10.0 solutions. If the readings are too close to each other, the calibration will fail. First do the 7.0. Let the numbers stabilize. Then "select" to store that reading. Rinse the probe then repeat with the 10.0 solution. Again, when the numbers stabilize, "select" to store the high reading. Then calibration is complete. Rinse the probe again and you can now put it in the 7 or 10 solution to see if it actually reads 7 or 10.

 

[rkelman]

The number never moves. It starts at 1228 and never moves.

 

[aquamanic]

Do you have it connected to the first Ph probe port or the combo Ph2/ORP port?

 

[rkelman]

Its on the Ph port.

 

[Deleted member 143833]

and did you remove the protective plastic cap?

 

[rkelman]

lol. Yes. Also the probe is working ok. It seems to be something with the calibration routine.

 

[Deleted member 143833]

Also the probe is working ok. It seems to be something with the calibration routine.

How have you been able to determine that the probe is OK? It could be bad calibration fluid if you are certain you are performing the correct steps.

 

[rkelman]

Its reading the same as my test kits. I need to calibrate low for my calcium reactor though. I don't think its calibration fluid because the settling numbers never move at all. No change whatsoever. Normally they would change somewhat before stopping right? I had started the calibration routine before I got calibration fluid just messing with it and the numbers changed. Now they never move from 1228.

 

[Deleted member 143833]

Now they never move from 1228.

If calibration is being done correctly then the numbers should move. If they do not move then I suspect a bad probe.

 

[rkelman]

The calibration routine seemed normal until I updated to the beta firmware. Do you think that could have anything to do with the issue I'm having?

 

[aquamanic]

It's easy enough to load the old firmware and see. I've got the zip file if you need it.

 

[rkelman]

That would be great. I'll PM you.

 

[rkelman]

Ok I loaded the old firmware and still no joy. Sometimes is actually locking up the Apex. Perhaps I need to email support?

 

[phuzzykins]

It really sounds like a bad probe; I had one fail suddenly, and this is exactly the behavior that I saw. I was able to move the probe to a completely different controller and verify that it was the probe.

 

[aquamanic]

Curt just posted another fix for 4.02 and one of the fixed items was an ORP calibration issue (I know yours is PH but who knows?). You might try loading that firmware first and just see but it sounds like you might have a bad probe. He's got some tests you can run if you email him.

 

[rkelman]

I emailed Tech support so I'll post my results here. That way the next guy can find the info if they search. Thanks.

 

[rkelman]

It was the firmware. I upgraded to the newest firmware and that fixed the issue. Curt was a great help. Thanks.

 

[aquamanic]

:thumbsup: