Apex Alarm Stopped Working

[ariellemermaid]

Has anyone had an issue where an apex alarm stops working? I have it set so that when my FW reservoir (Res_Lo) is open, the alarm should alert. It’s worked for years, but after some edits, it just stopped working. All other alarms (like Trident) are working fine, and there is currently no alarm. But there should be… (floss change and maintenance are both currently off)

Here is my alarm code:

Set OFF
If Error ATKModuleLnk Then ON
If Error ATOPump Then ON
If Error QTiSolenoid Then ON
If Error DOS_Alk Then ON
If Error DOS_Ca Then ON
If Leak1 CLOSED Then ON
If Res_Lo OPEN Then ON
If NSW_Lo OPEN Then ON
If Error Trident_6_3 Then ON
If FeedA 010 Then OFF
If ATK_Hi CLOSED Then ON
If Output Floss_Change = ON Then OFF
If Output Maintenance = ON Then OFF
Defer 010:00 Then ON

Here are pictures of the sensor state, as well as a picture of code (showing that it’s colored and therefore recognizes the sensor):

 

[Gtinnel]

Did your alarm slider get set to off accidentally instead of auto?

 

[ariellemermaid]

Did your alarm slider get set to off accidentally instead of auto?

Nope. Just had it alarm for Trident reagent A. Cleared it by resetting reagent A.

 

[Gtinnel]

Nope. Just had it alarm for Trident reagent A. Cleared it by resetting reagent A.

I may be wrong (I often am) but I always thought that the Email Alarm slider only affected error conditions that you programmed in, and a error that was generated from a module directly would still be sent.

I’m not saying that your slider is in the wrong position just that I don’t think the alarm from the trident is an indicator of the position of the slider.

ETA- so I just went and looked at my programmed error conditions and I have one for my trident also. So if I remove that alarm condition I’m not sure if my trident will send an alarm or not. If not, then I’m probably wrong on what I said above.

 

[ariellemermaid]

I may be wrong (I often am) but I always thought that the Email Alarm slider only affected error conditions that you programmed in, and a error that was generated from a module directly would still be sent.

I’m not saying that your slider is in the wrong position just that I don’t think the alarm from the trident is an indicator of the position of the slider.

ETA- so I just went and looked at my programmed error conditions and I have one for my trident also. So if I remove that alarm condition I’m not sure if my trident will send an alarm or not. If not, then I’m probably wrong on what I said above.

I promise it’s not an alarm slider issue. But no, I don’t believe modules can generate alarms without programming it that way.

 

[ariellemermaid]

I promise it’s not an alarm slider issue. But no, I don’t believe modules can generate alarms without programming it that way.

Actually come to think of it, I can confirm this. It’s happened before when I’ve been on vacation that a reagent will run out. Rather than turning all alarms off, I’ve temporarily removed the Trident error line from the alarm code and it has turned off the alarm.

 

[Reefer Matt]

If it is in the open state after 10 minutes, try moving the command to the bottom of the list, as the apex prioritizes commands top down, with the last command being highest priority.

 

[ariellemermaid]

If it is in the open state after 10 minutes, try moving the command to the bottom of the list, as the apex prioritizes commands top down, with the last command being highest priority.

Didn’t work, unfortunately.

 

[ariellemermaid]

I reached out to Apex support and they discovered I had two sensors by the same name. I’ve actually had issues before where sensors change names, sometimes back to defaults. It doesn’t make any sense that this happened; I haven’t changed, unplugged, or renamed any sensors in years.

But that’s what it was in case this is helpful to anyone.