pH id not Temp!

[phoggberg]

I checked for another thread like this and didn't find it, if I missed it please excuse this noob.

This is getting a bit irritating, has anyone else encountered this? I will be posting my code for a check in another post, but I have been working on my ATO programming. I have two aqualifters supplying ATO to my sump. One runs to my KALK Reactor and one just uses plain RO. I tried to put a safety statement in the code for each outlet:

If pH > 8.35 Then OFF <--- on the KALK Pump Outlet
If pH < 8.36 Then OFF <--- on the RO Only Pump Outlet

When I leave the outlet program after updating and go to another outlet, and then return, I find the statements changed to:
If Temp > 08.35 Then OFF <--- on the KALK Pump Outlet
If Temp < 08.36 Then OFF <--- on the RO Only Pump Outlet

Today I came home from an overnight trip to my main pump and lights cycling on and off due to low sump level my because the ATO were not filling the sump because the Temp was greater than 8.36 degrees! Probably need an off and stay off on the main pump code, any suggestions?

I have tried using 08.35 and 8.35 for the value doesn't seem to matter.
These are the last statements in the program if significant The Apex seems to be doing this. I am running the latest firmware, and the controller is a little over a month and a half old.

I travel a bit so this stuff is an issue for me. Thanks in advance for your reply.

 

[aquamanic]

try using lowercase 'ph' instead.

 

[phoggberg]

Thank You...

Thank You...

Will try that in the future...

 

[jkopp36]

I have had this problem too. Keep changing it back to pH after the Apex corrects and it should eventually stick. Once it does I have not had an issue with it randomnly changing it back. Just modify it, switch over to status, then come back and double check it. Weird problem and hopefully it is being looked at.

 

[phoggberg]

Still Doesn't work!

Still Doesn't work!

try using lowercase 'ph' instead.

Tried using lower case, put the pH statement in various places in the code, although that was supposed to be the most important and it didn't make any difference.

Curt if you are reading this stuff, what seems to make a bit of difference sometimes is if you use 8.35 instead of 08.35. I would guess that the formatting code for time is ahead of the reformat of pH and not checking for the key word pH and so it corrects the time. or it could be a typo in the reformat instruction. Last time it took me 6 tries to get it to stick.

 

[schwaggs]

I have no idea why this is happening, but have you tried editing the outlet program from the Display? It is a bit of a pain but might be worth a shot.

You can also try emailing neptune support.

 

[pyton]

This is a known issue, two ways I have heard it to work

1. Save the outlet Twice

Enter your commands and clcik Update Outlet
Let it save it and you will come back to same screen
Click Update outlet again

Switch to another outlet and come back in a few minutes to make sure changes were saved.

1. Rename pH

If you Rename the probe to something like pH_Reactor or pH_Tank and adjust all your programming to fit the new name you should be okay.

 

[wolrey]

I encounted this exact problem tonight as well. I just kept changing "Temp" back to the correct "pH". Eventually the correct "pH" statement stuck. Hopefully it doesn't revert back to temp.

Has anyone had it revert after say a restart or any other out of the norm situation?

Jeff

 

[jkopp36]

Once I got it to stick, I never had an issue even after a power cycle.