Apex 2016 Modules Blinking

[Kaidman]

Hi all,

I've got an Apex 2016 with 4x EB832, Trident, 3x DOS, Autofeeder, and a BOB. Late last night I noticed a couple of my radions turn off (connected to EB832) while the others stayed on (connected to a regular surge protector). Two of my EB832s were blinking orange, so I unplugged them and plugged them back in. This fixed the issue at the time.

Today every module is now blinking orange besides the Apex 2016 base unit. I've tried pulling power to a couple EB832s and plugging them back in, this did not help. I have also rebooted the Apex base unit with no results.

Are there any other general troubleshooting tips that will get my modules back up and going? Do I have a failed module causing this issue?

I have already submitted a ticket with Neptune and called support. Unfortunately it sounds like support will be tied up all day today and may not get a call until tomorrow, so any help would be appreciated.

Thank you!

 

[SuncrestReef]

A blinking module typically indicates the module is not in communications with the Apex. It’s possible your AquaBus cables or AquaBus ports are corroded. Carefully examine each end of the cables and each port. Try a different AquaBus cable if you have one, and/or try plugging into a different AquaBus port.

 

[Kaidman]

A blinking module typically indicates the module is not in communications with the Apex. It’s possible your AquaBus cables or AquaBus ports are corroded. Carefully examine each end of the cables and each port. Try a different AquaBus cable if you have one, and/or try plugging into a different AquaBus port.

Could a single cable be taking down all of the modules? I think that's what I'm hearing you say. The good news is I recently had my Apex Classic and lots more modules get fried by lightning, so I have less to troubleshoot now... Maybe I'll start from the base unit and only plug in one at a time.

Thanks for the quick reply.

 

[Kaidman]

This was it! I remembered a fish getting fiesty around feeding time last night and making an extra splash. Apparently it got in my AFS. I unplugged the AFS and everything immediately came back online. Sure seems like a bad design when a single module goes down to take the whole system down to its knees. Hopefully they are working on a resolution for that in the next version of the Apex (or sooner).

Thank you for your help!

 

[SuncrestReef]

Could a single cable be taking down all of the modules? I think that's what I'm hearing you say. The good news is I recently had my Apex Classic and lots more modules get fried by lightning, so I have less to troubleshoot now... Maybe I'll start from the base unit and only plug in one at a time.

Thanks for the quick reply.

It depends on where each module is plugged in. If they are daisy-chained, then a single bad cable on the first module in the chain would block all the other downstream modules from communicating.

 

[Kaidman]

It depends on where each module is plugged in. If they are daisy-chained, then a single bad cable on the first module in the chain would block all the other downstream modules from communicating.

 

[Kaidman]

In this case the AFS was the last module in a chain, so it really should have nothing to do with all the others. Anyways, I'm thrilled it is fixed quick, have a lot of other things on my mind and this was going to drive me crazy if it wasn't a quick fix.

Edit: accidentally double posted.. Can't find a delete option.