Xin Xout in Europe

[RFsolution]

Is there anyone who has used the Xi,Xout command in europe at 50HZ ?

I interfaced a basic circuit to a XM10 TTL interface (TW523)

but i can not switch on a device

Any help welcome

Walter

[RFsolution]

As it was already late here are some additional informations:

For years i'm using PBP but never used Xin xOut.

I have the following questions/problems

I just want to switch on and off a module with adres B 2
the zerocros pin looks ok with a scoop, I see TXdata, and when receiving from another X-10 transimitter
I see RX data, so I may assume that the X-10 to TTL converter is working properly except for Logic inversion see Question 3)

1) Is there any difference in timing or parameters (define) for 60hz or 50Hz operation ? (Europe 50Hz)
2) I found in the latest on-line documentation a define: DEFINE XOUTXLAT_ OFF 1 but dont find any additional explication
3) I use the XM-10 TTL interface optocoupled (european version of the 2 way TW-523) what about logic inversion ?
they suggest to invert the TXdata as showed here: http://www.marmitek.com/en/pdf/8942.pdf
4) are there any other code examples ? and any X-10 European users ?

[RFsolution]

No X-10 users from Europe ??? please help

[ardhuru]

Hi,

I had replied to your earlier post on the same subject ( Xin & Xout Europe (50hz) vs US (60hz) ).

1) Is there any difference in timing or parameters (define) for 60hz or 50Hz operation ? (Europe 50Hz)

No; as long as your transmitter and receiver are on the same electrical phase it would make no difference. If they are on different phases, there would technically be a timing issue. However, in the real world as long as you have signal couplers (0,1 uF caps) accross the phases, it works fine, This is on account of the relatively wide 'listen' window deined by the X10 protocol for receivers.

2) I found in the latest on-line documentation a define: DEFINE XOUTXLAT_ OFF 1 but dont find any additional explication.

I have done dome development work on X10, but not used the XIN / XOUT, so here I'm guessing (vaguely remembering something I'd heard). DEFINE XOUTXLAT_ OFF puts PBP in a mode where it reproduced the raw data coming in from an X10 receiver, as against a house code, unit code, or a command. With the TW523, and for simple switching of loads, do not bother with this define as the defaults work fine.

3) Logic inversion is not required with a TW523 and PBP, but pull-up resistors are. Are you using them?

Regards,

Anand Dhuru

[RFsolution]

I have been looking with a scoop to the timings regarding to the zerocrossing as reference

In a 60hz system timings are as followed:
Bursts are at 120 Khz, 1 millisecond long
1 half periode = 1/120 hz (2x 60hz) = 0,0083333333333333333333333333333333 sec There are 3 burst per zerocrossing Timing between each burst regarding to zerocrossing from 60hz is 2.778 ms,5.556 ms and 8.333 ms

In a 50hz system timings should be as followed:
Bursts are at 120 Khz, 1 millisecond long
1 half periode = 1/100 hz (2x 50hz) = 0,01 sec
There are 3 burst per zerocrossing
Timing between each burst regarding to zerocrossing from 50hz is 3.333 ms,6.666 ms and 10.000 ms

I had the same problem with another US X-10 microcrontroller project and we arranged it this week

So a conclusion is: X-10 Xin/Xout can not work on a 50Hz system
I contacted Melabs to inform them, and I got some immediate support
I hope that they come with a solution soon

[ardhuru]

Hi,
You are right, there are 3 transmissions per zero crossing. The first is almost at the zero crossing, the second and third 2.778 ms and 5.556 ms later (in a 60 Hz environment) respectively. These last two are transmitted solely to cater to receivers which might be on other phases, and which would therefore see their zero crossings 2.7 ms and 5.56 ms later (again as per 60 Hz) .

Therefore, as long as the transmitter and receiver are on the same phase, they experience the zero crossing simultaneously, and the frequency itself is immaterial.

Regards,

Anand Dhuru