New Apex salt alarm

[dsmize2011]

I keep getting this salt alarm every hour on the hour. I have turned the alarm on and off multiple times. It wont stop .

Neptune Alarms.PNG

[boozeman27]

Power cycle the whole apex system, it should fix the problem. It did for me. Also make sure all your firmware is current. Even if it says it is, go ahead and hit update on each module.

[Kwajtrader]

I'm having a similar problem, the values are in range but it is throwing an alarm every hour. I'm going to try resetting.

22	2017-07-25 21:22:44 -0400	ON	If Salt > 37.0 Then ON (34.0)
23	2017-07-25 22:22:44 -0400	ON	If Salt > 37.0 Then ON (33.8)

[Kwajtrader]

Power cycling did not help. I have updated the one eb832 connected. The Apex is at version

5.02_5A17. Help!

[AndrewAbo]

Any updates?

[AndrewAbo]

I'm having a similar problem, the values are in range but it is throwing an alarm every hour. I'm going to try resetting.

22	2017-07-25 21:22:44 -0400	ON	If Salt > 37.0 Then ON (34.0)
23	2017-07-25 22:22:44 -0400	ON	If Salt > 37.0 Then ON (33.8)

I haven't been able to find any other posts with this problem, but it looks like there are a few of us with the same issue. Mine is a new system, and I'm familiar with programming after having my last Apex classic for >4 years.

I don't have any configurations that reference ORP (yet), only the built in statements. I've tried widening the default range, and even disabling the ORP probe entirely. The text messages still come in like clockwork every hour.

I saw a potential fix posted by RussM (go figure!) on a different issue where there was some hysteresis loop circumvented, I believe by adding a "Defer 02:00 Then ON" statement.

As Kwajtrader stated, I, too am on 5.02_5A17.

[AndrewAbo]

Also, the unplug trick fixed a false salt alarm, but not the ORP alarm. The "apply firmware update to modules, even if they have been updated already" did not help.

[zombie]

Add

Defer 000:10 Then ON

To the entire email outlet.

If that does not solve the problem, update the firmware as I believe 2 firmware ago there was a bug (at least appeared to be) that had similar symptoms.

You might be an engineer if...You have no life and can prove it mathematically.

[AndrewAbo]

Add

Defer 000:10 Then ON

To the entire email outlet.

If that does not solve the problem, update the firmware as I believe 2 firmware ago there was a bug (at least appeared to be) that had similar symptoms.

You might be an engineer if...You have no life and can prove it mathematically.

Thanks for the assistance, but the Defer statement didn't help. Email and text still came in.

The firmware is up to date, as well.

[zombie]

Your outlet is in auto right?

You might be an engineer if...You have no life and can prove it mathematically.

[AndrewAbo]

Your outlet is in auto right?

You might be an engineer if...You have no life and can prove it mathematically.

Not entirely sure what you mean by the outlet being in auto.

The email config is below, but again, I haven't configured anything with ORP (ORP is causing the issue, not salt, or email). The alarm is triggered like clockwork every hour at 12 min. past. I've disabled the ORP probe, and it still sends email and text. For now, I've removed text, as I prefer being able to sleep (as a fellow engineer could appreciate). Emails and alarms are still triggered, however - even with the ORP probe disabled.

Set OFF
Fallback OFF
If Sw1 OPEN Then ON
If Tmp > 80.0 Then ON
Defer 000:10 Then ON

[zombie]

There is an outlet for the email alarm that can be set to ON OFF or AUTO. Make sure it's set to AUTO.

You might be an engineer if...You have no life and can prove it mathematically.

[AndrewAbo]

There is an outlet for the email alarm that can be set to ON OFF or AUTO. Make sure it's set to AUTO.

You might be an engineer if...You have no life and can prove it mathematically.

Yes, all of my outlets are set to Auto.

[zombie]

I don't know what the problem is then. Your symptoms sound exactly like what happens when the email alarm outlet is in ON instead of AUTO and your code looks fine. I would send an email to support if you are certain that outlet is in AUTO.

You might be an engineer if...You have no life and can prove it mathematically.

[AndrewAbo]

I don't know what the problem is then. Your symptoms sound exactly like what happens when the email alarm outlet is in ON instead of AUTO and your code looks fine. I would send an email to support if you are certain that outlet is in AUTO.

You might be an engineer if...You have no life and can prove it mathematically.

Agreed, puzzling at best. Thank you for your time. I'll be sure to circle back around once there is a solution.

[AndrewAbo]

Agreed, puzzling at best. Thank you for your time. I'll be sure to circle back around once there is a solution.

Contacted support, and they provided the fix:

1. Go to the Input Page
2. Remove all alarms
3. Then reboot the Apex
4. Go back to the Input Page
5. Re-enable the alarms.

Hopefully this helps someone out there.

[RussC]

Contacted support, and they provided the fix:

1. Go to the Input Page
2. Remove all alarms
3. Then reboot the Apex
4. Go back to the Input Page
5. Re-enable the alarms.

Hopefully this helps someone out there.

Questions from a Newbie:
1) How do you remove all the alarms?
2) How do you reboot the APEX? Doe that keep all your code and data?
3) How do you re-enable all your alarms?

[Phea2]

Following

[Leopardshark]

Same happened to me after I reinitializaed the unit.
Hope this annoying alarm will stop.
Regards

- - - Updated - - -

Questions from a Newbie:
1) How do you remove all the alarms?
2) How do you reboot the APEX? Doe that keep all your code and data?
3) How do you re-enable all your alarms?

You have to go to Settings, then to the Inputs tab and then manually turn them off.
Also in settings there is an option to reboot the Apex.
HTH