New AquaController 3/3 Pro Firmware

You will need to make a couple changes to the whatever upload program you are using; basically, where the instructions say 192.168.1.x change the 1 to a 2 (192.168.2.x). In short your AC3 is in a different subnet and that is likely causing the failure.
 
I thought i changed all the areas i needed to...

I changed the IP address for hte controller to 192.168.2.9

And the dhcp startting pool to ip of 192.168.2.50



This isnt funny any more... I just tried hooking hte controller direct to the pc, damn that is hard to undo all the cable s and stuff, and it still didnt work, then i had a biatch to get back online...

dang it
 
It shouldn't be that difficult to get working, usually it's some network thing. If you don't mind endulging a few basic questions...

Can you access the AC3 from your home network? I suspect you would use "http://192.168.2.50"?
 
no problem in the questions...

I would access the controller by typing 192.168.2.9
or use your simulator program with that same address

I also have a website that the data was uploaded to regularly...


BUT, although i would love to figure out why, I am always the one with the wierd problem, I have gotten past the problem by wiring direct.

The direction giver were not accurate though the SUBNET needed to be left at 255.255.255.0

other then that, i now have firmware 3.40 Thank you all, sorry it was difficult but so goes it...

I do have a question / comment for Curt though.

I notice the graphs and other information now comes up in pop up / seperate windows, (which is cool), but why do some seem to pop to the top and others dont when i click on the hyperlink??

Other then that, lookin good.


I think i will have some questions about the web setup page as i see some things there i dont understand or dont think is right... But I willsave that for a little bit


thanks
 
and, i am still waiting to see something on the graphs...

I have data in the datalog??? hmmm

No error message, just a black box
 
I notice the graphs and other information now comes up in pop up / seperate windows

It shouldn't..

Try refresh (F5) and what browser are you using (curious)?
 
Well, I ended up flashing back to 3.3

My controller froze up this evening on the new firmware. Noticed my halides were still on when they should have been off and when I investigated further I found that the controller was simply locked up. Front panel controls had no effect and I was forced to power it down in order to get it operational again.

Glad it happened when it did. If I had been out of the house for awhile it would have been bad as my chiller was running when the controller crashed and when I found the problem with the controller it was still running. Tank temp had gone down to 74. Imagine if my ATO, which is kalk, had been on when the unit crashed. :eek:

So for those using the beta on a system you care about you may want to think twice. Never seen a Neptune unit lock up like this before and I have used them for years. Will have to revisit the upgrade when it is out of beta.
 
<a href=showthread.php?s=&postid=14892723#post14892723 target=_blank>Originally posted</a> by Mako
Well, I ended up flashing back to 3.3

My controller froze up this evening on the new firmware. Noticed my halides were still on when they should have been off and when I investigated further I found that the controller was simply locked up. Front panel controls had no effect and I was forced to power it down in order to get it operational again.

Glad it happened when it did. If I had been out of the house for awhile it would have been bad as my chiller was running when the controller crashed and when I found the problem with the controller it was still running. Tank temp had gone down to 74. Imagine if my ATO, which is kalk, had been on when the unit crashed. :eek:

So for those using the beta on a system you care about you may want to think twice. Never seen a Neptune unit lock up like this before and I have used them for years. Will have to revisit the upgrade when it is out of beta.

So that's 2 of us that had it freeze up. Oh Curt ?????
 
Hmm, i did refresh and now teh graphs and other data comes up in the same window. That was wierd. Iactually like the info coming up in seperate windows. That way i can have different views at the same time...

BUT, i still have a black box for graphs... hmmm I want my graphs!!!! hehehehe
 
<a href=showthread.php?s=&postid=14890980#post14890980 target=_blank>Originally posted</a> by kenargo
Dynamic Host Configuration Protocol (DHCP) is a network protocol used by netowork connected devices to obtain configuration information for operation in an Internet Protocol network.

This is not a service on the computer, it is a configuration in the router. You should see a check-box on a configuration screen of your router; disable it, uncheck-in, etc then perform the firmware upgrade. Be sure to re-enable DHCP once the upgrade is completed.

You won't need to change tftp port values; leave them unchanged.

I am curious why you would put out a piece of software that requires computer inexperienced people to go into their routers and expect them to mess with the DHCP settings. Is this going to change with the final version?
 
One would assume so, though I'm a fairly new AC3 owner, and I don't know how they handled firmware updates in the past.

Everyone needs to remember, this is a beta, and it's completely up to everyone to decide if they want to mess with it, and if they do, it should be at their own risk.
 
One thing I should note is I had changed logging from 60 mins to 03 mins about 8 hours prior to the unit locking up. Don't know if that may have been part of the issue or not. Perhaps it ran out of memory, or some type of related buffer overflow???

Only reason I mention this is everything seemed fine when I had Aquanotes running and it was pulling data from the unit on a regular basis. Of course then there was no data for the web interface graphs. I wanted to start working with that so I shut Aquanotes down and changed the logging to 03 mins to build up some data.
 
<a href=showthread.php?s=&postid=14893927#post14893927 target=_blank>Originally posted</a> by Mako
One thing I should note is I had changed logging from 60 mins to 03 mins about 8 hours prior to the unit locking up. Don't know if that may have been part of the issue or not. Perhaps it ran out of memory, or some type of related buffer overflow???

Only reason I mention this is everything seemed fine when I had Aquanotes running and it was pulling data from the unit on a regular basis. Of course then there was no data for the web interface graphs. I wanted to start working with that so I shut Aquanotes down and changed the logging to 03 mins to build up some data.

I switched from 60 to 15 min logging right before the lock up.
 
<a href=showthread.php?s=&postid=14893809#post14893809 target=_blank>Originally posted</a> by rbc1225
I am curious why you would put out a piece of software that requires computer inexperienced people to go into their routers and expect them to mess with the DHCP settings. Is this going to change with the final version?

It is mostly a matter of making the controller easier to use on a daily basis, so it can more easily interface to your network. The once in a while that you need to go in to change firmware on the controller and having problems doing it is probably better than having those types of issues every time you need to get to the controller and change something. Also, if you have problems doing the work, Ken and Curt are very good at getting you though it. Last time I had to reflash (Mako, I had my AC3 freeze up like you experienced on 3.30 once - something happened when I tried to log in from work to check things, this was why I eneded up having to reflash) I couldn't figure out how to get it to work. Curt was great, walked me through it on the phone after I e-mailed him about the problem. Neptune has great customer service, and has earned my loyalty for that (having a great product doesn't hurt either :cool: )
 
Curt and Ken are both great, (ken has no affiliation with Neptune Systems, from what i was told), so he is purely volunteering his expertise...

I have no problem fiddling as long as the goal is achieved. I know the problems with network are problematic for every piece of network equipment. (I think due to the astronomical number of possible different configurations???)

I think i recall having to do these similar steps when flashing the updated firmware before as well. But this time was harder then normal, not sure why..

I would like to figure out why the problem with the graphs though... Seems that teh update was supposed to move from JAVA to FLASH to make it more reliable or something, so i was disappointed to not see the new graphs work out of the box, but, it is BETA and i know what to expect... I also know Curt will jumpp all over this, or me, to make this right...

I think it is also noteworthy to give a major jpdate to firmware to old products. Most companies limit thier updates to porducts that are one year old or so...


Anyways, Still a lifetime neptune systems customer...
 
If you have experienced the lockup problem, please email support@neptunesys.com your program and timer names. Also please include the serial # of the controller, as well as any other info you may have pertinent to the lockup. I don't think that it has anything to do with the datalogs, but I suppose it is possible.

Curt
 
<a href=showthread.php?s=&postid=14893809#post14893809 target=_blank>Originally posted</a> by rbc1225
I am curious why you would put out a piece of software that requires computer inexperienced people to go into their routers and expect them to mess with the DHCP settings. Is this going to change with the final version?

I deal with networked devices and embedded systems day in/day out, and it doesn't get much easier than this. Neptune cannot really be faulted here... they use standards-based protocols and methodology for doing firmware updates. Some of the proprietary methods I've seen for doing similar software loads have been outrageously complex and frustrating, even for a professional in the field. The "messing around" with DHCP on a home router consists of temporarily unchecking a single checkbox on the router's web page in most cases.
 
Back
Top