AquaController Jr. Problems

I never reported it because it didnt seem like that big of a deal. i guess it can be corrected in the next update. Speaking of which, when i do a self-test it shows my version to be 3A05, do i need to update this to 4A05?

Another issue is the default temp at 20F. why is it set so low? during the initial startup this may just be an annoyance as it turns the heaters on or whatever, but i had a more serious problem with it. One night i checked my tank to find my temp (based on heater's thermometer) at 86. I was so confused as my fans were off, the lights were on, and the heater was on (not heating due to the heater's setting, but the temp was displayed). I was wondering why none of the programs were acting as they should. Checking the temp on the AC unit i found it reading 20F. I figured something must have really gotten messed up. I checked to make sure the temp probe is still in the water and noticed that it had unplugged from the unit (must have not clicked it in). Of course once i plugged it back in everything adjusted right away. I just dont see why it sets to 20F which would be much riskier than setting it say to 78F as a default. Is it just to make it obvious when its not working?
 
clp said:
I was able to replicate the problem the intermittent lock up problem when entering the run display. I am very surprise that no one has noticed it before and reported it. The controller will reset itself in about 30 to 60 seconds after the screen goes blank so there is not danger that your tank won't be controlled. I'd say it is just one of those annoying type bugs. Also, the bug only exists when entering the run display from the select button press.
That is not so bad. At least control of the tank is maintained.
Originally posted by clp
I've emailed Aquaduck a beta release of the fixed firmware.
Thanks for the new firmware Curt. I will install it tonight and "play" with it over the weekend and let you know what happens.
Originally posted by clp The configuration of the controller is not changed following a firmware update. To get the default program/configuration back into the controller you need to do an init memory. You must press the select button when the arrow is next to the OK for configuration to be updated. I'm guessing you didn't do this.
You're right. I didn't do that step so I ended wiping the memory clean.
Originally posted by clp
Following a power cycle all the timer states are unknown, and the initial temperature reading is about 20F. After 5 seconds have elapsed program evaluation starts. The probe readings will stabilize in about 5 to 10 seconds after power up. I don't really see this as an issue/bug. Curt
Perhaps outputs should be dissabled during this start-up time to prevent alarms and devices that are programmed based on the temperature reading from being tripped on and off? Maybe the MAX CHANGE statement could be used on the alarm output so alarm conditions have to exist for a minute or so before the alarm device is turned on? I will try this over the weekend. Thanks for the excellent technical support! :thumbsup: :thumbsup:
 
alrha said:
I just dont see why it sets to 20F which would be much riskier than setting it say to 78F as a default. Is it just to make it obvious when its not working?
You posted your program a while back and you have an alarm statement (If Temp < 77 Then Alm On) so why didn't your alarm go off? I think maybe the 20 deg default reading is intentional so that an unplugged probe causes am alarm condition. You could also add this to your program:

If Temp <70 Then HET OFF

Should your heater fail open and your temperature starts dropping it will hit 77 and then the alarm will go off. Hopefully you will be around to fix the problem. If the heater IS working and the temperature continues to fall to 70 it's not doing any good so may as well be shut off. But this would never happen because your tank will never drop below room temperature. If the reading gets below 70 there is only one reason this could happen and that is an unplugged temp probe. So should the probe get unplugged the alarm will sound imediately and the heater will be dissabled to prevent it from overheating your tank.

This is also true for the pH reading. An unplugged probe will give a very low reading and sound an alarm.
 
Aquaduck said:
You posted your program a while back and you have an alarm statement (If Temp < 77 Then Alm On) so why didn't your alarm go off?

just because i programed it, doesnt mean i plugged in my Alarm yet :hammer: (in any event, i wasnt home at the time - thank god no harm was done at least, the heater has its own thermostat thay shuts the heater).
and just b/c i have the float valve for my RO/DI unit, doesnt mean i set it up yet. Perhaps i just buy what i need and wait for them to set themselves up.
 
Oh I know where your comin' from. I understand completely. I also have a float switch to install as a safety overflow prevention on the tank but do you think I would get around to installing it? Someday....

You might as well add

If Temp <70 Then HET OFF

to your program. It wouldn't hurt and just offers another level of protection. Is it done yet? :p J/K
 
Aquacontroller Jr. firmware 5A05 results

Aquacontroller Jr. firmware 5A05 results

I install Firmware Version 5A05 on my Aquacontroller on Friday night and it looks like they fixed the screen lock-up issue when pressing the "set" button on to run the program. I tried various times to get it to freeze up but the new code is solid. :thumbsup:
 
I just got mine last week and it has 4A05 now there's already a 5A05?? I'd also like to know since these things don't ship with any firmware cable or instructions on upgrading firmware.
 
You need a ACJR firmware upgrade cable. One end of the cable plugs into the serial port of your PC and the other into the temp probe connector of the Jr. We are selling the upgrade cable for $9.95; it is just not on our website yet. Send an email to support@neptunesys.com w/ your controller serial number (found in selftest), and I'll send you the updater program and new firmware. If you have version 3A05 of the firmware, we'll give the cable for free as the firmware has a potentially major bug.

Curt
 
I was able to replicate the problem the intermittent lock up problem when entering the run display. I am very surprise that no one has noticed it before and reported it. The controller will reset itself in about 30 to 60 seconds after the screen goes blank so there is not danger that your tank won't be controlled. I'd say it is just one of those annoying type bugs.

For anyone interested this bug is in version 4A05 because I just experience it. It does'nt happen all the time but it did today once. I didn't see that the controller reset itself until I pulled the power. Maybe I didn't let it sit long enough. Curt, so do you have another version beyond 4A05 already that fixes this problem? I'll send you an email tonight with my serial number.
 
Curt, is there any way to add a line of code within the program? or can we only add code to the bottom?
 
Back
Top