Apex Auto Feeder Dead? Any way to fix?

[kyley]

Hi All,
I bought an AFS from someone and it doesn't want to do anything for me. I plug it in to my full (current model) Apex - either the EB832 or the Brain - and the green light on the back of the AFS turns on and the AFS shows up in Apex Fusion.

Where it shows the devices as Off, Auto, and On, it is on Auto. If I turn it to On, it doesn't do anything.

If I go into the device and set it to Feed at 15:45 (1 drum rotation, 1 feeding per day), on Feed Cycle A, and Save, it doesn't do anything at 15:45.

And, if I start Feed Cycle A from Fusion, it doesn't do anything.

Did I get a defective Auto Feeder? Any ideas if I can do anything to fix it? I don't hear a sound from it or any hint of movement. Thanks,
--Kyle

 

[link81]

what does it say in apex.local? does it need a firmware update?

 

[kyley]

what does it say in apex.local? does it need a firmware update?

Hmm, it says Software Version 2 (OK)
Although it also let me do a software update, but that didn't change.

Also, why does it have two USB ports? I tried connecting one to the base unit and one to the brain, but no luck.

Another thing I just thought of is that the previous owner was using an older Apex Lite and I'm using the newest one. Any issue with an older AFS on a new Apex? Thanks,
--Kyle

 

[link81]

hmm.
is the AB cable known good?
if you remove the feeding chamber does it do anything? possible that something is jammed somewhere?
if you change it to "on" in fusion, it definitely should start a feed cycle.

 

[kyley]

hmm.
is the AB cable known good?
if you remove the feeding chamber does it do anything? possible that something is jammed somewhere?
if you change it to "on" in fusion, it definitely should start a feed cycle.

Thanks. And when I click Feed Cycle A (if that's what it's assigned to) it should run, right?

I can't say for sure, but I imagine the cable is good. And I tried two different ones (one on the base unit and one on the brain). Either one should work, right?

It doesn't do anything with the chamber removed either. I edited my previous answer to add that it was on an Apex Lite and now I'm trying to use it on a new Apex. Thanks,
--Kyle

 

[link81]

as long as the cable works with something else, I would assume it's fine. (the fact that its showing up in fusion at all makes me think its OK)

if it's assigned to A, and you start A then yes, it should start.

did it work on the lite, and its not working on the 2016?

 

[kyley]

did it work on the lite, and its not working on the 2016?

Correct. At least according to the guy I got it from. Thanks,
--Kyle

 

[link81]

Know anyone else with an apex?
Have you tried a reboot? (Of the apex)
Can also try deleting it from local, and re-adding it.
Neptunes support is usually pretty helpful also.

 

[kyley]

Know anyone else with an apex?
Have you tried a reboot? (Of the apex)
Can also try deleting it from local, and re-adding it.
Neptunes support is usually pretty helpful also.

Thanks. I have the guy's Apex Lite and I could set it up and see if it works on that.
I did reboot it today. Thanks,
--Kyle

 

[Tastee]

Also, why does it have two USB ports? I tried connecting one to the base unit and one to the brain, but no luck.

All Apex accessories have 2 Aquabus ports. You only need to use 1 to connect it to any other Apex accessory or the brain. The 2nd port is to allow you to daisy chain devices. It doesn’t matter whether the accessory is connected direct to the brain or another connected accessory - Apex forms it’s own LAN.

 

[SuncrestReef]

Also, why does it have two USB ports? I tried connecting one to the base unit and one to the brain, but no luck.

As @Tastee mentioned, you can daisy chain modules. Just be certain not to create a loop back to the Apex because that will mess up the communications. Example:

 

[kyley]

As @Tastee mentioned, you can daisy chain modules. Just be certain not to create a loop back to the Apex because that will mess up the communications. Example:

Cool, thanks both of you. I figured that was the case but when it isn't working, I started wondering if it had something to do with how it's connected. Or if it won't work with the newer version of the Apex for some reason. Thanks,
--Kyle