continuing weirdness since firmware 3.4 upgrade

[ciphros]

I had posted a while back that I was having an issue with my alarm getting tripped when my 2nd MH kicked on. It had stopped for some time, but it's back again. I decided to pull the xml data for outlets to see what's going on when it triggers - here's what I got:
- <record>
<date>08/19/2009 11:31:00</date>
<name>MH2</name>
<value>ON</value>
</record>
- <record>
<date>08/19/2009 11:31:03</date>
<name>COL</name>
<value>OFF</value>
</record>
- <record>
<date>08/19/2009 11:31:35</date>
<name>LOW</name>
<value>ON</value>
</record>
- <record>
<date>08/19/2009 11:31:36</date>
<name>ALM</name>
<value>ON</value>
</record>
- <record>
<date>08/19/2009 11:31:36</date>
<name>LOW</name>
<value>OFF</value>
</record>
- <record>
<date>08/19/2009 11:31:37</date>
<name>ALM</name>
<value>OFF</value>
</record>
- <record>
<date>08/19/2009 11:32:00</date>
<name>FAN</name>
<value>OFF</value>
</record>


Looks to me like when MH2 turns on, it causes switch 2 to have a momemtary "ON" (LOW timer listed above). I know that the switch wouldn't ever be on for 1 second - since the tank has to have lost water, and under normal conditions, it's sucked up against the top of the stem, so it can tolerate the waves no problem (usually aren't any anyway - sump is pretty well baffled). This never used to happen before the firmware upgrade. Still looking for any ideas, anyone?

[kenargo]

What is the proximity of wiring and ballast to the float switch? It is possible that the sudden in-rush of current to the ballast or light could be causing a momentary magnetic field which is interrupting the float?

[ciphros]

Ballast is mounted in the canopy, wires go up from there and out near the ceiling then down to the DC8. Wires to the light stay inside the canopy. Float switch is in the sump on the floor over 6 feet away, wires run up from there to the breakout box (about a foot from the DC8) and then to the input on the AC3. Highly doubt there is anything interrupting the float from the light. It's highly sporadic for when it happens. It happened last Thrusday and Friday, then nothing until today.

It actually looks like maybe the light isn't really the total cause here either, the light doesn't come on just before the low sump timer and alarm. Today it was 35 seconds after the light came on, Thursday it was 5 minutes 5 seconds after, and Friday 15 minutes 30 seconds after. And that reminds me, the guy watching my house while we were out of town said that MH3 turned on with MH2 for a minute, then went back out before the alarm came on on Friday - and yet MH3 doesn't even show in the list as activating. Here's the xml from Thursday and Friday:

Thursday-
- <record>
<date>08/13/2009 11:31:00</date>
<name>MH2</name>
<value>ON</value>
</record>
- <record>
<date>08/13/2009 11:34:46</date>
<name>COL</name>
<value>OFF</value>
</record>
- <record>
<date>08/13/2009 11:35:00</date>
<name>FAN</name>
<value>OFF</value>
</record>
- <record>
<date>08/13/2009 11:36:05</date>
<name>LOW</name>
<value>ON</value>
</record>
- <record>
<date>08/13/2009 11:36:06</date>
<name>ALM</name>
<value>ON</value>
</record>
- <record>
<date>08/13/2009 11:36:06</date>
<name>LOW</name>
<value>OFF</value>
</record>
- <record>
<date>08/13/2009 11:36:07</date>
<name>ALM</name>
<value>OFF</value>
</record>

Friday -
- <record>
<date>08/14/2009 11:31:00</date>
<name>MH2</name>
<value>ON</value>
</record>
- <record>
<date>08/14/2009 11:39:00</date>
<name>FAN</name>
<value>OFF</value>
</record>
- <record>
<date>08/14/2009 11:46:30</date>
<name>LOW</name>
<value>ON</value>
</record>
- <record>
<date>08/14/2009 11:46:31</date>
<name>ALM</name>
<value>ON</value>
</record>
- <record>
<date>08/14/2009 11:46:31</date>
<name>LOW</name>
<value>OFF</value>
</record>
- <record>
<date>08/14/2009 11:46:32</date>
<name>ALM</name>
<value>OFF</value>
</record>
- <record>

[kenargo]

What trips the alarm? Could the float be bouncing in the water or could the float be going bad?

Is low == add or do you have a setup with low/add being separate floats?

[ciphros]

Low is switch only for alarm - loss of water from system and completely separate from top-off - it controls nothing other than sending an alarm when triggered. It's burried to the hilt unless something causes water loss from the system. Don't think it is the float's problem, it happens nearly the same time every day that it trips - so it's something external - otherwise it'd be doing it at random times throughout the day.

[plack]

I had sompthing on an ac2 trip aound the same time daily then I plugged everything from the dc8 thru a surge protector before going to the ground fault circuit and the problem went away.

Just a thought-- a guess !

[ciphros]

<a href=showthread.php?s=&postid=15566332#post15566332 target=_blank>Originally posted</a> by plack
I had sompthing on an ac2 trip aound the same time daily then I plugged everything from the dc8 thru a surge protector before going to the ground fault circuit and the problem went away.

Just a thought-- a guess !

Can you elaborate Plack - Did you have to use 8 different surge protectors plugged into the outlets of the DC8, or was it just the DC8 into a surge protector, then that plugged into the GFCI (guessing this last is the case, but wanted to be sure)?

Let me know and I will try accordingly and post back to let everyone know if it works or not.

Thanks for the tip!

Nate

[plack]

" just the DC8 into a surge protector, then that plugged into the GFCI "


Yes that is the way I have it !

The surge protector is a battery Backup for a P.C. not a tiny one either.

:-)

Paul