Issues with Aquacontroller Jr and X10

[Bryan]

Hello:

I am a owner of a new Aquacontroller JR, and am having difficulties with the unit in regardsto the X10, and frankly getting rather frustrated.

I am not new to X10 usage and have been using the technology for years on my tank with very few problems, that is until I changed over to the Aquacontroller jr.

I am getting random turn on events on my X10 controllers. When these events happen I notice there is activity on the IM513 moduule ( The light blinks off/on) as the module turns on which leads me to believe the Aquacontroller is sending out these commands. These random turn on events happen appprox 1-2 times per hour and mostly on a module connected to a IceCap 660 ballast, however I have noticed the issue with other controllers as well, but few and far between.

After approx 5 min later the IM513 module will then again show activity and the X10 modulewill turn itself off(usually but sometimes another cycle is required before it turns off). I suspect this is the "X10 repeat interval" doing it's job and checking and correcting the state of the X10 modules.

As a test last evening I disconnected the cable from the aquacontroller from the IM513 and these random turn on events stopped.

I also used my previous X10 controller to turn on X10 modules and NO activity was seen on the IM513 module which most cetainly confirms the problem is from the Aquacontroller.

I suspect errant signals are being send out from the Aquacontroller or the X10 Repeat interval feature is turning the modules on and then off.

All modules have "local control" disabled and the module with the Ice cap ballast has a X10 filter on it. The aquacontroller and the IM513 is kept a fair distance from any power cables, pumps, lights etc

Any ideas??

 

[clp]

It is very unlikely that the AquaController is sending out the incorrect commands. Much more likely since you are using X10 is that the commands the controller is sending out are corrupted by line noise, and being interpreted incorrectly by the control modules.

Here are some tips to debug the X10 problem:

- Make sure that the control interface is plugged into the AquaController with a 4 conductor telephone cord. The light should blink off when commands are sent out, but otherwise will be on.
- Make sure that the control modules x10 addresses match the configuration of the AquaController. The default AquaController program is listed in the back of the manual.
- The control interface and control modules should plug into the same circuit. If not, you may need to install a signal bridge.
- Do no use power strips with active surge suppression as they can attenuate the x10 signal. Use inexpensive powerstrips.
- With the AquaController try to turn on and off the control modules. Go to Control & Status -> Manual Control. Select the device you are having trouble with and repeatedly turn it on and off. Note that commands are only sent out when you press the select button.
- If you have added any new equipment to your tank, turn it off, and then repeat the Manual control test.
- Try switching to an unused X10 address on the control module and in the AquaController’s configuration.
- Try swapping the control module with a known good one and see if the problem persists.
- Try power cycling the AquaController. Remove the 9V battery and unplug the AC adapter at the same time.
- If nothing is working try shutting off all appliances around your tank, and then try the manual on/off test. If something is causing X10 interference around your tank, it is likely an electronic ballast. Once the interfering device is found use an X10 noies filter (part # NF5) to isolated from the power in your house.
- To avoid X10 noise problems, use the DC4, DC4HD, DC8 boxes instead. They have hardwired control and are immune to powerline noise.

Curt

 

[Bryan]

Thanks Curt, but the problem never existed until I switched over to the controller Jr.

The problem is occuring in the evening when everything in the tank is mostly off, so I don't see what interference could be causing the problem. I am certain it is the X10 repeat interval commnds being sent out that are triggering the ON condition on the module(s), these commands then turn off the module(s) 5 min later.


If it was interference then why am I not having problems during the day when lights and pumps are turned on, they all respond correctly and shut off correctly in the evening.

I have gone into the debug mode in the self test mode as suggested in other threads. Would the values it displays help in any diagnosis?

 

[clp]

Confirm that there are not duplicate timer name or control addresses. Also make sure you don't have any bogus program statements. Then reboot the controller. You can also email timer names and program to support@neptunesys.com, and I'll take a look.
The reason a X10 interference issue is more likely to show up is because the AquaController sends many more commands than a standard X10 controller. Most X10 controllers for home automation only send the command 1 time. Let say the probability of a corrupted X10 signal is 1 out of 100. In the case of a standard X10 controller, a device would be set incorrectly say 1 out 100 days.
For the AquaController which resends commands every 5 minutes the same X10 error rate results in an incorrect on/off state every day. If you want the AquaController to operate without repeating commands set the X10 repeat interval to 0. I don't recommend this though as an incorrectly received heater/chiller command could be disastrous. It would be much better to find the source of the X10 electrical noise or use our direct connect boxes instead.
The source of the interference does not have to be a device controlled by the AquaController. It can be any appliance in your house. The most likely source of interference is electronic ballasts. If X10 is going to be used, then the source must be found, and a noise filter installed on it.

Curt

 

[Bryan]

Thanks Curt I will give it another go tonight. One thing I will try is switch the module from the Iceap ballast with another one on the circuit, if the problem follows then perhaps the module itself is faulty, but I did have issues with other modules turning on. But after disabling the local contriol on the modules on Sunday, I haven't noticed issues with them, just the one controlling the IceCap ballast.

What about the line from the controller to the IM513, could it be picking up noise, what is the suggested cable run length. The one I am currently using is is a 15 feet .

I will e-mail you the commands etc.

 

[Bryan]

Well, it's been a week since I replaced the cable between the jr and the powerline interface and not one "false" triggering of modules that I can tell. I even added a timer to turn on/off every minute to keep the interface busy, but no problems.

So if others are having issues with X10, might be a good idea to check the cable you are using between the jr and the powerline interface or even the DC4/8 for that matter.