My Latest X10 Woes...

Started by davideinmd, July 29, 2011, 09:51:53 AM

Previous topic - Next topic

davideinmd

I have a PRO Inline Fixture Dimmer Module that is set to B9, however, though it works occationally as that code, it sometimes decides it's a B7. I have a Wall Switch Module that is set to B7 but it will only work as a B6 and only sometimes. I have to older LM465's (non-soft start) that don't work at all now (however no module set to any code will work in those two outlets even though they have for years). There were some recent electrical storms and that was when the outlets stopped working but the other two modules that are confused have been that way for a longer time even though they worked like they were supposed to in the beginning. No new devices or anything changed that is plugged into any outlets. Any thoughts?

Brian H

Try rotating the House and Unit Code Dials on them a few times. The address switches maybe getting dirty and sometimes the address is incorrect.

davideinmd

Tried that (difficult as it was to get to the inline) no change.

Quote from: Brian H on July 29, 2011, 10:03:53 AM
Try rotating the House and Unit Code Dials on them a few times. The address switches maybe getting dirty and sometimes the address is incorrect.


davideinmd

I discovered that my XPCR Phase Coupler/Repeater was no longer working. I put in an old passive coupler and the non-working outlets work now. Still the funny issue with the two that refuse to be who I made them.

Noam

Quote from: davideinmd on July 29, 2011, 12:00:38 PM
I discovered that my XPCR Phase Coupler/Repeater was no longer working. I put in an old passive coupler and the non-working outlets work now. Still the funny issue with the two that refuse to be who I made them.
If you rotate the dials one code (move from B7 to B8, for example), does it then work on B7?
I suppose it is possible that something got fried when you had the power spike, or, the contacts are not working right on the dial. Even rotating them around a few times doesn't always fix the issue.

You might try different codes, and see if you can find one that seems to work reliably for you.
The contacts may be dirty/worn, and rotating the dial around a few times isn't enough to clean them.

If you feel adventurous enough, I suppose you could try opening the modules up, and rake a good look at the contacts.

JeffVolp


The contact wipers on some of my old BSR (brown box) X10 modules broke loose from the thumbwheel and didn't set the correct numbers anymore.  They were repairable by carefully re-forming the plastic hold-down tabs with a "warm" soldering iron.

Jeff
X-10 automation since the BSR days

Noam

Quote from: JeffVolp on July 29, 2011, 01:55:40 PM

The contact wipers on some of my old BSR (brown box) X10 modules broke loose from the thumbwheel and didn't set the correct numbers anymore.  They were repairable by carefully re-forming the plastic hold-down tabs with a "warm" soldering iron.

Jeff

I probably would have just soldered a jumper across, and hard-coded the HC/UC at that point.

davideinmd

#7
That's funny you guys! But really I guess for the few bucks I'd just swap em out with new ones. I reckon I got my 3+ years' money's worth. Love my X10! :) (On the side of that, I think that X10 changed the way the software works for the cams. Now when the signal isn't quite good enough it just goes black...and on...and black... In fact, Since I upgraded to the lastest AHP, which I updated again since the July 1, 2011 update, AHP on my 64 bit Windows 7 machine crashes when I am using the software actively. Oh, and the cams freeze after about 15 minutes.)

Quote from: Noam on July 29, 2011, 04:34:06 PM
Quote from: JeffVolp on July 29, 2011, 01:55:40 PM

The contact wipers on some of my old BSR (brown box) X10 modules broke loose from the thumbwheel and didn't set the correct numbers anymore.  They were repairable by carefully re-forming the plastic hold-down tabs with a "warm" soldering iron.

Jeff

I probably would have just soldered a jumper across, and hard-coded the HC/UC at that point.

JeffVolp

Quote from: davideinmd on July 29, 2011, 05:17:47 PM
But really I guess for the few bucks I'd just swap em out with new ones. I reckon I got my 3+ years' money's worth.

In the BSR era a module cost about 3 hours wages, so it was certainly worth repairing. 

Back then you could buy a new car for $3000 - anybody remember the Rabbit?

Jeff
X-10 automation since the BSR days

dbemowsk

These days I wish I had an old VW Rabbit diesel.  I have heard of people running those motors on all kinds of old oil.  Really a die hard car back in the day.
Dan Bemowski
Owner of PHP Web Scripting LLC
Programmer of RemoteWatch X10
User of any X10 products I can get my hands on.

davideinmd

BSR...Big Silly Remote? I tried to look it up but I guess it's older than the internet. As am I.  :-\

Quote from: JeffVolp on July 29, 2011, 05:50:17 PM
Quote from: davideinmd on July 29, 2011, 05:17:47 PM
But really I guess for the few bucks I'd just swap em out with new ones. I reckon I got my 3+ years' money's worth.

In the BSR era a module cost about 3 hours wages, so it was certainly worth repairing. 

Back then you could buy a new car for $3000 - anybody remember the Rabbit?

Jeff

dave w

Quote from: JeffVolp on July 29, 2011, 05:50:17 PM
Back then you could buy a new car for $3000 - anybody remember the Rabbit?
Yeah! About the same time I had a Ford Pinto, also known as the Ford "Char-Broil". But was a great handling, peppy little car.
"This aftershave makes me look fat"

davideinmd

Ok...enough about x10 I reckon...lol...so how bout those Pirate's... (sigh)...no one hangin in the Home Automation Chatroom either.

Noam

Quote from: davideinmd on July 29, 2011, 05:17:47 PM
That's funny you guys! But really I guess for the few bucks I'd just swap em out with new ones. I reckon I got my 3+ years' money's worth. Love my X10! :) (On the side of that, I think that X10 changed the way the software works for the cams. Now when the signal isn't quite good enough it just goes black...and on...and black... In fact, Since I upgraded to the lastest AHP, which I updated again since the July 1, 2011 update, AHP on my 64 bit Windows 7 machine crashes when I am using the software actively. Oh, and the cams freeze after about 15 minutes.)

Are you sure you're running 3.316? That was supposed to have fixed the "black frame flicker" problem that was introduced in 3.315.

davideinmd

#14
Yes...3.316. In fact, it wasn't a problem in the last one (I forget the version #),

Quote from: Noam on July 29, 2011, 06:30:32 PM
Quote from: davideinmd on July 29, 2011, 05:17:47 PM
That's funny you guys! But really I guess for the few bucks I'd just swap em out with new ones. I reckon I got my 3+ years' money's worth. Love my X10! :) (On the side of that, I think that X10 changed the way the software works for the cams. Now when the signal isn't quite good enough it just goes black...and on...and black... In fact, Since I upgraded to the lastest AHP, which I updated again since the July 1, 2011 update, AHP on my 64 bit Windows 7 machine crashes when I am using the software actively. Oh, and the cams freeze after about 15 minutes.)

Are you sure you're running 3.316? That was supposed to have fixed the "black frame flicker" problem that was introduced in 3.315.