Apex ATK. Please help before I hit it with a hammer.

[Mark Goode]

I tried it linked to the Apex when I first got it, and it didn't work - except once, when it started the PMUP but didn't stop until I unplugged it (the float valve saved the day) - the rest of the time it did nothing.

I tried it in standalone mode, and every hour the PMUP runs for 3 - 5 seconds before cutting out, even though the water level is a couple of inches below any sensor. A couple of times it's alarmed and flashed red, but the rest of the time nothing but a pathetic little squirt every hour.

I decided to have another go through the Apex, but just get an error message (see below). The sensor leads marked 1 & 2 are in the correct sockets, and are pushed home as far as they can go without using a hammer.

On an unrelated issue, Apex is reporting my salinity is zero. I really hate Neptune Apex.

 

[ZombieEngineer]

That error means it did not detect an optical sensor in that port. Go to the fmm module setup page and change that port to optical. After you do that check it's function. It should show closed when covered with water and open when not (fusion takes like 30 seconds to refresh so be patient).

If they both do not respond correctly, you may have a bad optical sensor that needs replaced.


The salinity readin 0 means your probe is unplugged.

 

[Mark Goode]

That error means it did not detect an optical sensor in that port. Go to the fmm module setup page and change that port to optical. After you do that check it's function. It should show closed when covered with water and open when not (fusion takes like 30 seconds to refresh so be patient).

If they both do not respond correctly, you may have a bad optical sensor that needs replaced.


The salinity readin 0 means your probe is unplugged.

Thanks Mr Zombie.

I also posted my frustration on the Neptune forums, and a chap there suggested I delete that error line from the EmailAlrm program, which was probably there from a previous attempt to get it working. This I did, and it now runs for 20 seconds before it stops. I'll watch it over the next few hours.

As for the salinity probe? <ahem> mumble mumble musta knocked it or something...

 

[ZombieEngineer]

Thanks Mr Zombie.

I also posted my frustration on the Neptune forums, and a chap there suggested I delete that error line from the EmailAlrm program, which was probably there from a previous attempt to get it working. This I did, and it now runs for 20 seconds before it stops. I'll watch it over the next few hours.

As for the salinity probe? <ahem> mumble mumble musta knocked it or something...

What Russ told you will fix the error, but not the root cause.

Also likely why it's turning on for 20 seconds and then turning off. If your optical failed and is showing closed when not covered in water, the ATO won't run.

If you check the things I mentioned earlier and the optical is failed, you can temporarily unplug it, go to your PMUP code and temporarily remove the switch 2 line. Thus will let your PMUP run based on the one working optical sensor until you get a replacement.

If not already there, add this line to your email alarm

If Error PMUPoutletname Then ON


This will alert you if it runs for more than 5 minutes.

 

[Mark Goode]

What Russ told you will fix the error, but not the root cause.

Also likely why it's turning on for 20 seconds and then turning off. If your optical failed and is showing closed when not covered in water, the ATO won't run.

If you check the things I mentioned earlier and the optical is failed, you can temporarily unplug it, go to your PMUP code and temporarily remove the switch 2 line. Thus will let your PMUP run based on the one working optical sensor until you get a replacement.

If not already there, add this line to your email alarm

If Error PMUPoutletname Then ON


This will alert you if it runs for more than 5 minutes.

Okay, both sensors look like they're open (if I'm reading this contraption correctly):

I was with you up to this bit : "go to your PMUP code...". Can you give me a clue where to look? Apologies if I appear a bit dim, I must be getting old; I can't remember C++ giving me as much trouble as this wretched thing. Mind you, that was 25 years ago at least.

Thanks for your help.

 

[Tub Life]

I know this is an old post, but this may help others who have this problem.
I had the same error as OP, looks as if the optical sensor isn't installed when it is.
The problem lies in the autogenerated naming of the sensors.
Apex setup wizard is looking for SWX3_2 where as it actually named it SWX5_2 for you.
So if you change the corresponding sensor to SWX3_2 the wizard will complete without error.
(in my case the sensor was named SWX6_2 instead of SWX3_2, and SWX6_1 instead of SWX3_1, and so on.)

 

[Mark Goode]

Maybe I should have updated this post once I solved the problem.

The wires to the sensors were much longer than I needed them to be, so I just stuffed them into the return chamber by the ATO sensor unit itself. Once I had tidied those wires and clipped them out of the way everything worked.

Why that fixed it I've no idea, but it did.