Apex LLS Alarming

trevorhiller · Nov 14, 2022

I just got an Apex Pro today and I'm working my way through programming. I had some initial difficulty getting the LLS calibrated, but after switching it over to FMM Port 3 on the Apex Pro it finally calibrated using their example Low/High calibration points.

The problem is now it keeps alarming... I'm receiving Alarm If LLS > 9.0 Then ON

I've tried creating an alternative Alarm statement (If LLS > 8.0 Then ON), completely turning off the alarms (setting Alarm to Never) and unplugging/reconnecting the LLS, Changing the LLS Configuration to the 23" model and back to the 15" model as well as rebooting the Apex.

I can't seem to find where this statement exists in the programming that is causing this alarm to trigger. Am I missing something here? Even if I delete all the code from the Email Alarm with the exception of Set OFF, it still alarms.

MnFish1 · Nov 14, 2022

I'm sure this is a stupid question - did you remember to click 'Send to Apex' - to update the code in the apex? Second - I'm also assuming that your pictures represent where your settings are 'now'? I may be wrong - but - I would consider removing all of the check boxes (the enable, the configure off, etc)

doubleshot00 · Nov 14, 2022

Try this and see if its under this area.
Open app and click the gear icon.
Then click on the graph icon beside the gear.
Then the click alarm gears and go through whats programed

trevorhiller · Nov 14, 2022

doubleshot00 said:
Try this and see if its under this area.
Open app and click the gear icon.
Then click on the graph icon beside the gear.
Then the click alarm gears and go through whats programed

Currently the only thing programmed under any of the alarm areas is

"Set Off"

trevorhiller · Nov 14, 2022

MnFish1 said:
I'm sure this is a stupid question - did you remember to click 'Send to Apex' - to update the code in the apex? Second - I'm also assuming that your pictures represent where your settings are 'now'? I may be wrong - but - I would consider removing all of the check boxes (the enable, the configure off, etc)

Not stupid, I went back through to make sure I didn't miss something like this and it still seems to be going off.

I tried unchecking the log checkbox, deleting all the text from the configuration space and sending to Apex and then tried reprogramming it with "Set Off" and sending to Apex, it's still going off.

This is slightly maddening lol it's like a ghost line of code stuck somewhere.

MnFish1 · Nov 14, 2022

trevorhiller said:
Currently the only thing programmed under any of the alarm areas is

"Set Off"

I would remove that. Have no advance programming, and unblock the 'enable log' button. EDIT - sorry I didn't see your comments!!! - I might call APEX tech support - OR did you try to post on the forum on the Neptune site?

MnFish1 · Nov 14, 2022

PS - check out some of the suggestions on this thread - there may be one or 2 that will help - it goes into "great" detail beyond the original question - seems like lots of people are/were having this issue (I believe most o these were on the 2016 model)
https://forum.neptunesystems.com/showthread.php?19303-Remove-alarm-notification

trevorhiller · Nov 14, 2022

I did post on the Neptune forums but I hadn't gotten any replies yet.

Just out of curiosity, I tried switching the LLS from Port 3 to Port 4 on Apex FMM and made port 3 my optical. In the process of re-configuring the LLS, Apex named it "LVLX1_4" and I left the name as it is.

That caused me to receive an alarm that said LEVEL is <6.0 (0.0)...

LEVEL is what I had tried changing the name to (from LLS) to see if I could get it to overwrite the old programming. There wasn't anything called LEVEL in my settings at this point, yet I was still getting the alarm.

I found that under the system button (the one that maps out the flow chart of all devices) there is an option to delete the FMM module if you change the drop down from "Configure" to "Delete." I deleted it and then went back to Tasks and reran the configure Liquid Level Sensor task. It seems the glitch was with the FMM itself because after deleting the configuration of the whole FMM and setting it back up everything is working as it should!

8 hours of my life spent troubleshooting this, but glad it seems to be working now! At least I know the ins/outs of where everything is in Fusion now!