Constant Alert not Sure why

[KRoss]

Email and or Test I receive:

Date: 2017-04-24 08:23:31 -0400
Status: ON
Statement: If Sump_T < 74.5 Then ON (76.8 )

So if I am reading this right says if my tank is less then 74.5 then alarm?


But it is not:
sump-T.jpgSump-Settings.jpg

I have played with the settings and nothing seems to stop the alert.

My Email Settings show:
Set OFF
If Sw1 OPEN Then ON
If Swx8_1 CLOSED Then ON


So Not sure what is causing it.

Thanks

[Frogfish]

Is the probe name all caps? Your alarm statement shows lowercase. Capitalization is important and could be that the alarm is on a probe you don't have which would always be lower than your alarm threashold.

[zeusvh]

The event message shows that the IF statement reads if Sump_T is less than 74.5, trigger alarm. But the parenthesis after states that the ACTUAL current temp is HIGHER at 76.8. So the alert should not be triggering. Do you have two temp probes that may be confusing it?

[KRoss]

probe.jpg

I assume it the probe highlighted?

[jonmos75]

Turn Off the the temp alarm from the input page, reboot the Apex base unit (located in the misc page), then re-enable the Temp alarm.

[KRoss]

So it seems to be just walking down the alerts:

1- Alert was this:
Date: 2017-04-24 15:35:18 -0400
Status: ON
Statement: If Tank_P < 7.80 Then ON (8.29)
Disabled and rebooted

2- Alert was this:
Date: 2017-04-24 15:38:42 -0400
Status: ON
Statement: If FLx4_R < 250 Then ON
Disabled and Rebooted

3- Alert was this:
Date: 2017-04-24 15:41:56 -0400
Status: ON
Statement: If FLx4_B < 450 Then ON
Disabled and Rebooted

4- Alert was this
Date: 2017-04-24 15:43:52 -0400
Status: ON
Statement: If Tank_S > 40.8 Then ON (36.7)
Disabled and Rebooted

Still going down them..

[KRoss]

But I was able to finally figure it off:

on My Second salinity probe in my tank it was set for >35 and < 34 and it was 36. Once I reset that one everything worked.

I would think it would show the actual alert based on the one that was having an issue not the first one on the list.

[zeusvh]

>35 and < 34 means that it ALWAYS triggers at ANY value, continuously. I would expect strange behavior. It may not be able to keep up with the logic code. You are locking it in a loop.