Apex Help Asap

Nighthawk26

Active Member
Joined
Apr 10, 2015
Location
Waterloo
I too hate stuff like this. Equivilant sort of thing has happened to all of us I'm sure with one thing or another. In the nicest way possible, next time, RTFM. ;)
 

Kman

Super Active Member
Joined
Apr 15, 2014
Location
KW
Actually the eb8 should follow the Fallback statement that each outlet was programmed to.

It doesn't act like that because those statements are controlled by the Apex not the power bar. When you program, it is on the Apex base module not the other modules or eb8. If that were true if you programmed say a timer to turn your lights on and off it would still work if it got disconnected and it doesn't. It is a built in safety feature so if your hardware loses connection to the Apex they still work.

I know this for a fact because I had a water overflow accident when I was on vacation a few months ago that Eric had to take care of for me. My overflow box broke off and water came up and over the top of the tank. Shorting out the eb8 that controls my DT and ended up corrupting my Apex shutting it down. I had my fall back statement set to off on the eb8 in my fish room that controls my main sump pump and once it lost connection it kept running as a normal plug ignoring all programmed statements. It ended up dumping most of my 110 sump worth of saltwater onto my floor and hardware. If the Fallback statement still worked after the Apex lost connection the fallback statement would have shut the outlet off that controls my sump pump and it didn't. So it kept pumping away happily.
 

Pistol

Super Active Member
Donor
Joined
Aug 16, 2012
Location
Corunna
It doesn't act like that because those statements are controlled by the Apex not the power bar. When you program, it is on the Apex base module not the other modules or eb8. If that were true if you programmed say a timer to turn your lights on and off it would still work if it got disconnected and it doesn't. It is a built in safety feature so if your hardware loses connection to the Apex they still work.

I know this for a fact because I had a water overflow accident when I was on vacation a few months ago that Eric had to take care of for me. My overflow box broke off and water came up and over the top of the tank. Shorting out the eb8 that controls my DT and ended up corrupting my Apex shutting it down. I had my fall back statement set to off on the eb8 in my fish room that controls my main sump pump and once it lost connection it kept running as a normal plug ignoring all programmed statements. It ended up dumping most of my 110 sump worth of saltwater onto my floor and hardware. If the Fallback statement still worked after the Apex lost connection the fallback statement would have shut the outlet off that controls my sump pump and it didn't. So it kept pumping away happily.
Yours is a different situation than normal, according to the comprehensive manual "The Fallback statement establishes what state the outlet should be in if the EB4/8 loses communication with the base module", so the statement is in the eb8, your situation fried the eb8 so the statement couldn't work.
 

Kman

Super Active Member
Joined
Apr 15, 2014
Location
KW
I hear what you are saying and know what you are talking about in the comprehensive user manual on page 50 as I have read this. It didn't work like they claim for me. I have tested all three of my E8B (including the replacement of my fried one) and none work as they claim after losing connection when fallback set to off. I wish they did and had.

The statement on my fried eb8 correct didn't work as it is fried you are correct. But I have 2 other eb8 that were not fried that reside in my fish room behind my DT and they still had power after they lost connection with the Apex and continued to function as a normal powerbar. Those two E8B are the ones that run my sump pump, ATO and everything else on my other tank in the fish room. Nothing worked for statements that I had programmed on those E8B including the fallback. If it had my sump pump would have shut off, my ATO and top up pump would have shut off after they lost connection as well as everything else that I have set to shut off. Instead the sump pump kept pumping and when my water level dropped in my sump my ATO kicked in and kept pumping till it timed out. If the fallback set to OFF had worked for me my sump pump would have shut off and my ATO and top up pump would have shut off as well. Instead of turning on when my water level line got low making the situation worse. So I hope it works for everyone else because it sure did for me.

Trust me I wish this had worked for me as I would not have over $1000 in hardware damages to my tank that i had top replace and repairs from water damage to my house. So I myself don't have piece of mind thinking that it is fool proof because I learned the hard way it isn't. I hope other have different results because it really sucked.
 

Pistol

Super Active Member
Donor
Joined
Aug 16, 2012
Location
Corunna
I hear what you are saying and know what you are talking about in the comprehensive user manual on page 50 as I have read this. It didn't work like they claim for me. I have tested all three of my E8B (including the replacement of my fried one) and none work as they claim after losing connection when fallback set to off. I wish they did and had.

The statement on my fried eb8 correct didn't work as it is fried you are correct. But I have 2 other eb8 that were not fried that reside in my fish room behind my DT and they still had power after they lost connection with the Apex and continued to function as a normal powerbar. Those two E8B are the ones that run my sump pump, ATO and everything else on my other tank in the fish room. Nothing worked for statements that I had programmed on those E8B including the fallback. If it had my sump pump would have shut off, my ATO and top up pump would have shut off after they lost connection as well as everything else that I have set to shut off. Instead the sump pump kept pumping and when my water level dropped in my sump my ATO kicked in and kept pumping till it timed out. If the fallback set to OFF had worked for me my sump pump would have shut off and my ATO and top up pump would have shut off as well. Instead of turning on when my water level line got low making the situation worse. So I hope it works for everyone else because it sure did for me.

Trust me I wish this had worked for me as I would not have over $1000 in hardware damages to my tank that i had top replace and repairs from water damage to my house. So I myself don't have piece of mind thinking that it is fool proof because I learned the hard way it isn't. I hope other have different results because it really sucked.
I tested my apex today, disconnected the usb from the head unit, after about 15 seconds the eb8 and eb4 both started flashing green on the status indicator then after about another 15 seconds all the fallback statements kicked in and everything that was supposed to shut down did shut down, after re establishing the connection everything turned back on.

I wonder if you have some coding errors in your statements the could have caused your situation.
 

Kman

Super Active Member
Joined
Apr 15, 2014
Location
KW
I don't have coding errors as I can copy anyone's programming and have the same thing happen. Mine when I tested it this weekend just stays on and nothing happens after I unplug the power bar from the Apex. Mine if everything looses power and goes down when it all comes back up the outlet shuts off like it should and defers my 30 min that I have programmed, after 30 min it turns back on. If I unplug one power bar nothing happens on that power bar and everything stays on. My Apex sounds an alarm because it sees it lost connection to the power bar so it is noticed something is wrong. When i first noticed this I updated my firmware on the Apex and everything connected and still nothing.
 

Neopimp

Website Doctor
Staff member
Website Admin
Joined
Jun 9, 2014
Location
Sarnia
So you are saying that if it lost connection with the head unit it turns into a power bar with all outlets on regardless of the fallback line of code in the outlet program?




Sent from my iPhone using Tapatalk
 

bart84

Active Member
Joined
Apr 23, 2014
Location
Brantford, Ontario
I am confused as well. When mine acted up. Some were on ( pumps an ad such ) but some were off ( all my lights ). I am kind of curious to do a test but don't want to screw it up again.
 

Neopimp

Website Doctor
Staff member
Website Admin
Joined
Jun 9, 2014
Location
Sarnia
I have tested my setup and it does what its supposed to. I had my main unit just stop working one night a year ago and the EB8 followed exactly what the fall backs were. If it acted the other way then there are thousands of Apex/BRS dosers combos at huge risk out there.

I am betting that in your disaster the apex did not loose comms with the other EB8 and they continued to function as programmed. Other wise why would the ATO time out? Why would the ATO even start if not told to by the main unit. Possible that the sump pump saw the low level... ato started up... fixed the low level condition in the sump... main pump fires back up do to the SET On you probably have... drains a bunch of water out... repeat?

Cant say for certain obviously because I do not know your set up or programming but the Fallbacks are a very important statements and not likely to be screwed up by Neptune. They 100% work or you should be in touch with neptune.

As far as how they work...Fallbacks are stored in a rewritable RAM/Flash type chip in the EB8. When they get set/saved, the main unit will set a memory bit either on or off on a chip inside the eb8. One bit for each outlet. That will be what the EB8 goes to when the handshaking between the main unit and EB8 fail. My understanding of it anyways.


Sent from my iPhone using Tapatalk
 
Last edited:

Pistol

Super Active Member
Donor
Joined
Aug 16, 2012
Location
Corunna
I am confused as well. When mine acted up. Some were on ( pumps an ad such ) but some were off ( all my lights ). I am kind of curious to do a test but don't want to screw it up again.
In your case you corrupted the data so anything could have happened, you should go into apex/nstatus.sht and save your configuation so you don't have to reprogram everything if something like that happens again.
I tested mine and it worked fine, did take about 30 seconds though.
 
Top