X10 XM10 User Manual

X-10 protocol for the Marmitek XM10 OEM Controller

Marmitek XM10 OEM Controller

*O.E.M Original Equipment Manufacturer

Safety Warnings

•The wiring of your electrical installation is live (230 V) and extremely dangerous. Never connect the module when plugged into the mains. Always turn off the main switch before starting the installation.

•To prevent short circuits, this product should only be used inside and only in dry spaces. Do not expose the components to rain or moisture. Do not use the product close to a bath, swimming pool etc.

•Do not expose the components of your systems to extremely high temperatures or bright light sources.

•Do not open the product: the device contains live parts. The product should only be repaired or serviced by a qualified repairman

•In case of improper usage or if you have opened, altered and repaired the product yourself, all guarantees expire. Marmitek does not accept responsibility in the case of improper usage of the product or when the product is used for purposes other than specified. Marmitek does not accept responsibility for additional damage other than covered by the legal product responsibility.

How to implement

Two - way PLC interface for OEM applications (XM10)

The XM10 is a transmitter-receiver that plugs into a regular AC outlet and connects to the controller via a modular RJ 11 telephone jack. Alternatively, the XM10 may be fitted inside the controller cabinet, connected to the 230 V AC supply before the power transformer. (This would be a typical installation with most security panels.)

It provides an opto-coupled 50 Hz. Square wave, synchronised to the zero crossing point of the AC line. The controller generates X-10 compatible codes synchronised to this zero crossing point. The two-way interface then couples the X-10 codes onto the AC line.

Two - Way transmission available

The two-way interface transmits and receives X-10 codes. It enables an O.E.M. to develop a system to control X-10 Modules, and receive X-10 signals from remote sensors (P.I.R. motion detectors for example)

X-10 Code transmission

To transmit X-10 signals the controller must supply 1 ms .envelopes. to the TX input of the interface with respect to common. These envelopes must be as close as possible to the zero crossing point of the AC line (see timing diagrams). An optocoupled output representing the zero crossing point of the power line is provided for the controller to which X-10 codes are to be synchronised.

X-10 Code reception

The two-way interface uses a custom proprietary I.C. to read X-10 codes from the power line. This takes a lot of burden off the microprocessor in the controller as it does not have to continuously monitor the powerline and check all in coming signals (and noise) for validity. Any signals applied to the controller are error-checked, valid X-10 codes. When a valid X-10 code is received, it is stored in the custom I.C. and

- 1 -

X-10 protocol for the Marmitek XM10 OEM Controller

applied (in envelope form) to the controller. This output is coincident with the second X-10 transmission. (X-10 codes are always transmitted in groups of two, except for Bright and Dim.)

Data sent to the controller is valid X-10 data. The start Code (1110) can be used to alert the controller that an X-10 Code will follow. A .1. bit from the two-way interface appears as a negative going pulse 1.1 ms long, beginning approximately 100 µs after zero crossing. The controller should sample this data between 500 and 700 µs after zero crossing.

The L.E.D. on the two-way interface gives a visual indication that X-10 codes are being received. The L.E.D. is illuminated when AC power is applied to the two-way interface and blinks off when X-10 codes are received. The two-way interface will also receive the codes it transmits, therefore the L.E.D. will also give an indication of codes being transmitted.

The ability to read X-10 codes from its own output also allows the controller to incorporate data collision detection. If the code received differs from the code transmitted, the code can be assumed to have been corrupted by noise ( or another transmission ) on the power line.

The line Monitor capability of the two-way interface allows the controller to ensure that the power line is free from X-10 signals before starting a transmission. This means that in a multitransmitter system the controller can minimise contention between transmitters. For example, if after detecting that the line is free, a transmitter waits for a random number of power line half cycles before transmitting, the chance of collision is reduced. A different priority can be assigned to each transmitter by including a fixed delay before the random delay. The shorter the fixed delay, the higher the priority.

Important Safety Notice

Zero volts in this product is directly connected to one side of the AC line.

Therefore, for safety, an ISOLATING power transformer MUST be used when attempting any internal measurements.

The power supply in the two-way interface are capacitively derived from, and directly referenced to, the 230V AC power line. Care should be taken when monitoring any internal circuitry with an oscilloscope, as the OV reference in the two-way interface are NOT isolated from 230 volts.

X-10 Protocol

The tables in Figure 1, show the Binary Codes to be transmitted for each House. Code and Key Code. The Start Code is Always 1110 which is a unique code and is the only code which does not follow the truecomplement relationship on alternate half cycles.

- 2 -

X-10 protocol for the Marmitek XM10 OEM Controller

Figure 1

House Code and Key Code Tables

	House Code									Key Codes
	H1	H2		H4		H8			D1	D2	D4	D8	D16
A	0	1		1		0		1	0	1	1	0	0
B	1	1		1		0		2	1	1	1	0	0
C	0	0		1		0		3	0	0	1	0	0
D	1	0		1		0		4	1	0	1	0	0
E	0	1		0		1		5	0	0	0	1	0
F	1	1		0		1		6	1	0	0	1	0
G	0	0		0		1		7	0	1	0	1	0
H	1	0		0		1		8	1	1	0	1	0
I	0	1		1		1		9	0	1	1	1	0
J	1	1		1		1		10	1	1	1	1	0
K	0	0		1		1		11	0	0	1	1	0
L	1	0		1		1		12	1	0	1	1	0
M	0	1		0		0		13	0	0	0	0	0
N	1	1		0		0		14	1	0	0	0	0
O	0	0		0		0		15	0	1	0	0	0
P	1	0		0		0		16	1	1	0	0	0
					All	units		off	0	0	0	0	1
					All lights on				0	0	0	1	1
								On	0	0	1	0	1
								Off	0	0	1	1	1
								Dim	0	1	0	0	1
							Bright		0	1	0	1	1
				All Lights Off					0	1	1	0	1
			Extended Code						0	1	1	1	1
			Hail Request (1)						1	0	0	0	1
		Hail Acknowledge							1	0	0	1	1
			Pre-Set Dim (2)						1	0	1	X	1
Extended Data (analog) (3)									1	1	0	0	1
					Status = on				1	1	0	1	1
					Status = off				1	1	1	0	1
			Status Request						1	1	1	1	1

(1)Hail Request is transmitted to see if there are any other X-10 transmitters within listening range. This allows the O.E.M to assign a different House code if a .Hail Acknowledge. is received.

(2)In a Pre-Set Dim instruction, the D8 bit represents the Most Significant Bit of the level and H1, H2, H4 and H8 bits represent the 4 Least Significant Bits.

(3)The Extended Data code is followed by 8 bit bytes which can represent Analog data (after A to D conversion). There should be no gaps between the Extended Data code and the actual data, and no gaps between data bytes. The first 8 bit byte can be used to say how many bytes of data will follow. If gaps are left between data bytes, these codes could be received by X-10 Modules causing erroneous operation.

Extended Code is similar to Extended Data: 8 Bit bytes which follow Extended Code (with no gaps) can represent additional codes. This allows the designer to expand beyond the 256 codes presently available.

- 3 -