CAUTION: New Apex AOS update

SuncrestReef · May 4, 2019

Neptune released the newest AOS update for Apex and Apex-EL yesterday with a lengthy list of new features and bug fixes. As an IT guy, I know the risks of being the first to update to new software, but I decided to update anyway. Most of the update went well, but it did mess up 2 of my 3 FMM modules by mis-identifying the sensors I have plugged in to each port. The one for my ATO normally has optical sensors in ports 1, 2, and 3, but now it shows this and it won't let me make any changes to it:

Screen Shot 2019-05-04 at 5.39.28 AM.png

I submitted a ticket to Neptune Support, but I'm not sure if they are open on the weekends.

So, be warned...If your Apex is currently running fine, I'd recommend avoiding this update until further testing has been done and other bugs revealed. I'll post updates as I learn more.

Here's Neptune's release: https://forum.neptunesystems.com/showthread.php?26615-AOS-5-05_5A19-is-now-available!

User1 · May 4, 2019

Interesting. I just saw the update earlier and figured it was getting ready for the Trident launch. Saw a few Cor pump updates for which I have three of those pumps so did the upgrade. After that I saw the FMM module update requirement so did that. I do not remember what I had mine set to - I'm an idiot. I use it for the ATO and this is what it is set to...

It sees one Optical Sensor instead of two. Not sure what happened here.

SuncrestReef · May 4, 2019

saf1 said:
Interesting. I just saw the update earlier and figured it was getting ready for the Trident launch. Saw a few Cor pump updates for which I have three of those pumps so did the upgrade. After that I saw the FMM module update requirement so did that. I do not remember what I had mine set to - I'm an idiot. I use it for the ATO and this is what it is set to...

It sees one Optical Sensor instead of two. Not sure what happened here.

Does yours let you un-check the Auto detection option and manually set your optical sensors? When I try, it discards my changes.

Typically the ATO would have Optical sensors in ports 1 and 2.

User1 · May 4, 2019

Yes, it lets me uncheck. I tested on Port 1. It was checked to use auto detection and I was able to uncheck and save.

User1 · May 4, 2019

SuncrestReef said:
Typically the ATO would have Optical sensors in ports 1 and 2.

That is what I thought as well. It is auto detecting as water on floor sensor. No idea why but I'll shoot them a email/ticket and see what they say.

SuncrestReef · May 4, 2019

saf1 said:
Yes, it lets me uncheck. I tested on Port 1. It was checked to use auto detection and I was able to uncheck and save.

After you saved the changes, did it keep them? On mine it just reverts back to the wrong sensors after I save my settings.

User1 · May 4, 2019

Yes, they are saved. I've checked a couple times. That is the image above. I checked again and yes. Lets me save, uncheck, check, etc.

Jay Z · May 4, 2019

Make sure you update off a hard line. Lot of people bricking units trying to update over WiFi.

SuncrestReef · May 4, 2019

Jay Z said:
Make sure you update off a hard line. Lot of people bricking units trying to update over WiFi.

Yes, My Apex is connected via Ethernet cable.

leepink23 · May 4, 2019

I guess I got lucky, no issues with the update with my ATK, hopefully everyone gets theirs fixed.

Billldg · May 4, 2019

I did notice that my WXM module graphics for my Radions is messed up now, didn't change any settings, but its almost impossible to read after Apex update.

BigHildy53 · May 4, 2019

What version are you downloading? I have 5.04 7A18 and my system says it's the latest. I have two FMM modules, no APEX ATK.

smartwater101 · May 4, 2019

Jay Z said:
Make sure you update off a hard line. Lot of people bricking units trying to update over WiFi.

If this was true we'd be hearing about it quite a lot. A module going wonky is one thing. Bricking the system would bring riots lol

Billldg · May 4, 2019

Ver. 5.05 5A19

Did you reboot your Apex, and I had to refresh the Network page after the reboot for it to show a update available.

BigHildy53 said:
What version are you downloading? I have 5.04 7A18 and my system says it's the latest. I have two FMM modules, no APEX ATK.

RussM · May 4, 2019

Jay Z said:
Make sure you update off a hard line. Lot of people bricking units trying to update over WiFi.

The cautions against updating over WiFi apply only to the old Apex Classic series, not to the newer Apex and Apex EL. The AOS update released yesterday is for those two newer Apex models.

Jay Z · May 4, 2019

RussM said:
The cautions against updating over WiFi apply only to the old Apex Classic series, not to the newer Apex and Apex EL. The AOS update released yesterday is for those two newer Apex models.

Nice. Keeps me from Making a new Ethernet cord. Went to WiFi update this morning and a huge warning came up about bricking it. Googled it and seen some have had issues. Thanks for clearing it up!

SuncrestReef · May 4, 2019

Update:

After re-applying the update to the FMM, the problem appears to be resolved. Apparently the update didn't take the first time even though it reported the update was successful. If any of you experience this same issue, I'd recommend repeating the module update process.

rkpetersen · May 4, 2019

Not directly related to this problem, but I have never had much use for the auto-detect feature.
Once a sensor is plugged into an FMM, it doesn't change unless you manually unplug and replace it.
So it's easy to just set a port manually for the particular device, and then never touch it again until you change the device on that port.
And setting sensors manually also removes the possibility of auto-detect errors.

SuncrestReef · May 4, 2019

rkpetersen said:
Not directly related to this problem, but I have never had much use for the auto-detect feature.
Once a sensor is plugged into an FMM, it doesn't change unless you manually unplug and replace it.
So it's easy to just set a port manually for the particular device, and then never touch it again until you change the device on that port.
And setting sensors manually also removes the possibility of auto-detect errors.

I agree 100%. I've had my ports set manually for a year, then this update broke it and forced two of them to Auto-detect, and wouldn't let me change back to manual settings until I re-applied the module update.

leepink23 · May 4, 2019

SuncrestReef said:
I agree 100%. I've had my ports set manually for a year, then this update broke it and forced two of them to Auto-detect, and wouldn't let me change back to manual settings until I re-applied the module update.

Where do you go to see auto vs manual on the ports?