SuperRay
Guest
I thought this was a cool trick/tip for those who are about to get your new APEX controllers and will be adding Float Switches for ATO.
This posting is copied from RussM on RC
Averting Disaster
It's been discussed here many times why the proper orientation of a float switch (normally open or normally closed) for a given use is critical. The New User Guide says it quite well:
The most common usage of switches is for floats. Floats are referred to as being "normally open‟ (NO) or
"normally closed‟ (NC). This is a direct result of the orientation of the float to the internal switch contacts. A
normally open float means the contacts are open and when the float moves up or down, the contacts close. The
reverse is true with normally closed floats. It is this OPEN or CLOSED that you use in programming for a
switch. Some floats are reversible. They come in a particular orientation, like normally open but by removing a
clip and reversing the float position it becomes normally closed. Other floats you have to purchase in the proper
orientation and cannot change.
The reason the orientation is important is for failures. If/when a float switch fails, more likely than not it will fail in
the open (float sticks, wire breaks, contacts don't close, etc). In addition, when you disconnect the BB
from the Apex base module, all switches go to their OPEN state. So keep this in mind when you layout your
floats. You want the OPEN condition to trigger stopping something, like a pump. You don't want OPEN
to trigger a pump starting or you will have a nasty surprise some day.
That line in boldface red is the actual subject of this post.
If you've followed the guidelines above, you may not know (at least immediately) that most or all actions which depend on switch state will not be happening if the breakout box got disconnected. So, how can you tell if the breakout box gets inadvertently unplugged?
Easy... use an available switch input and a virtual outlet.
[BoBUnplugged]
Set OFF
If Switch6 OPEN Then ON
Then, do this is the Email Alarm outlet (and audible alarm outlets too if desired) :
If Outlet BoBUnplugged = ON Then ON
In order for this concept to work, the switch input must be constantly CLOSED by installing a shorting jumper between the selected switch terminal and the ground terminal of the breakout box. I picked Switch6, because it was available, and because it just so happened that a standard staple conveniently works perfectly as a jumper between the I6 and GRD terminals.
But you could just use a short piece of wire.
Now, if the BoB get disconnected, the Apex will see the switch state as OPEN, and you will get an alarm.
This posting is copied from RussM on RC
Averting Disaster
It's been discussed here many times why the proper orientation of a float switch (normally open or normally closed) for a given use is critical. The New User Guide says it quite well:
The most common usage of switches is for floats. Floats are referred to as being "normally open‟ (NO) or
"normally closed‟ (NC). This is a direct result of the orientation of the float to the internal switch contacts. A
normally open float means the contacts are open and when the float moves up or down, the contacts close. The
reverse is true with normally closed floats. It is this OPEN or CLOSED that you use in programming for a
switch. Some floats are reversible. They come in a particular orientation, like normally open but by removing a
clip and reversing the float position it becomes normally closed. Other floats you have to purchase in the proper
orientation and cannot change.
The reason the orientation is important is for failures. If/when a float switch fails, more likely than not it will fail in
the open (float sticks, wire breaks, contacts don't close, etc). In addition, when you disconnect the BB
from the Apex base module, all switches go to their OPEN state. So keep this in mind when you layout your
floats. You want the OPEN condition to trigger stopping something, like a pump. You don't want OPEN
to trigger a pump starting or you will have a nasty surprise some day.
That line in boldface red is the actual subject of this post.
If you've followed the guidelines above, you may not know (at least immediately) that most or all actions which depend on switch state will not be happening if the breakout box got disconnected. So, how can you tell if the breakout box gets inadvertently unplugged?
Easy... use an available switch input and a virtual outlet.
[BoBUnplugged]
Set OFF
If Switch6 OPEN Then ON
Then, do this is the Email Alarm outlet (and audible alarm outlets too if desired) :
If Outlet BoBUnplugged = ON Then ON
In order for this concept to work, the switch input must be constantly CLOSED by installing a shorting jumper between the selected switch terminal and the ground terminal of the breakout box. I picked Switch6, because it was available, and because it just so happened that a standard staple conveniently works perfectly as a jumper between the I6 and GRD terminals.
But you could just use a short piece of wire.
Now, if the BoB get disconnected, the Apex will see the switch state as OPEN, and you will get an alarm.
