x10 not working

[Efried]

according to some editors X10 is dead, its not very reliable. This (and the lacking CAI interfaces to X10) is another argument speeding up IEEE 802.11 developments...

 

[XRinger]

according to some editors X10 is dead, its not very reliable. This (an the lacking CAI interfaces to X10) is another argument speeding up IEEE 802.11 developments...

 
X10 hardware is now getting more expensive, but it's still not very costly. My applications are non-critical, so being only 99.87% reliable
isn't a big deal. X10 is easy to use and the CAI firmware to control X10 RF remotes (Like the FireCracker) is very easy to set up.
 
The CAI  X10 interface is the main reason I purchased my first CAI board. 

 

[Efried]

X10 hardware is now getting more expensive, but it's still not very costly. My applications are non-critical, so being only 99.87% reliable
isn't a big deal. X10 is easy to use and the CAI firmware to control X10 RF remotes (Like the FireCracker) is very easy to set up.
 
The CAI  X10 interface is the main reason I purchased my first CAI board. 

 
Ok, what are your experiences regarding wall penetration of RF in heavy brick houses?
I recently found out that users are selling add on boards for IO and AD, I would trust the system architecture if CAI sets up a webshop putting all those pieces together including an X10 interface board.

 

[XRinger]

I'm not sure that weak 310 mhz signals will penetrate brick walls very well. 
I located the X10 receiver in the a basement area (near the transmitter)
where my remote-control signal only has to penetrate a wooden kitchen floor.
 
The transmitter   http://i46.photobucket.com/albums/f147/Xringer/Green%20slot/R079.jpg
Can be located where it can 'see' the receiver. Any used of handheld remotes 
should also happen in the area of the receiver.
 
Anyone with a soldering iron can add a diode to a Firecracker and make the
RS-232 cable (or use an old cable).
 
Wiring X10 up isn't very hard. CAI directions are excellent.

 

[Efried]

Anyone with a soldering iron can add a diode to a Firecracker and make the

RS-232 cable (or use an old cable).
 
Wiring X10 up isn't very hard. CAI directions are excellent.

 
I have found a new type of application, if WCs would be capable of switching between remote control mode (PLC off) and PLC-mode.  The central WC controlling all via X10 is no option because X10 units have only one sensor per unit. It would be nice having an Wifi connected WC network having ad hoc possibility to act autonomously but also as slave...

 

[XRinger]

I got another error this morning. 
 
The two fans came on, when the heat should have come on.. (Both fans use the same device code, 7)
In binary, the fan device is 0111 and the heat device is 0101 ..
 
Seems like a burst of RF noise or AC line noise in the middle of the byte, could confuse the receiver.. A single bad bit..
I would change the house code on the fans, but that would make them too hard to control them using the handheld RF remote control.
 
Maybe I just need to make the device bytes more dissimilar.
My three device codes in use now, are  5, 6 & 7.   0101, 0110 & 0111.
I'll change them to  0001, 1000 & 1111 and see if that makes them noise proof..
 
If those device codes still get errors, I'll try using three different house codes too.
 
 
 
FAN_ON:
    X10 2 7 1    
    RET   



HEAT_ON:    
    X10 2 5 1    
    RET    
 
etc.

 

[CAI_Support]

Your local electrical company may changed out old reliable meter to new ones. Those new meters generate RF signals from time to time, which can cause power line communication problem.  We also noticed the EnPhase power inverters generate power line communication signals clash with other power line communication devices.  Enphase told us by adding coil to filter the power section of their inverter, user can remove the noise.  Test result showing there are still noise go into power line with the coil they recommended.  To filter out the power line noise really good is critical for X10 to work reliably.

 

[XRinger]

My meter transmits on UHF, so the meter reader can drive by, eating donuts while my meter is read by a radio in his car.
Not very likely to interfere with power line signals. Plus the transmitter runs a whole lot less power than a cell phone.
 
http://www.griffmonster.com/miscellaneous/electricmeter/electric_digital_meter_reading.html
 
I kinda like this meter because it's easy to read, when I need to calibrate a TED..

 

[pittom]

just got wc32 in today and x10 not working.  worked on wc8 but i use test code 

start
tsteq op1 1
x10 0 0 1
set op1 0
tsteq op2 1
x10 0 0 0
set op2 0
end

remote flashes but does not turn it on/off.I put a battery in remote and worked on/off but not on wc32. When i try to go back into program error bad house code,even tried    http://webcontrol-ip/api/sendX10.cgi?hc=0&uc=0&cmd=1 said success but no on/off.
 
when i go to x10 control every thing on page is packed on 2 can't read anything
 
tom

 

[XRinger]

On the I/O Setup page, do you have X10 Enable checked?  (On).

 

[pittom]

YES,the remote is flashing when i send code. I an doing everything the same as it was working on wc8.  

 

[CAI_Support]

In WC32, X10 PLC logic using house code A-P, device code 1-16,  command 0-3.
We will need to change that to no longer enforce those, so that user can use VAR/RAM as parameter to X10.