PSC05
From CT.wiki
Contents |
Description
The PSC05 Two-Way Powerline Interface Module allows the developer to interface their equipment with the 120V power line using standard X10 protocol. The Powerline Interface connects to a (non-PC) serial type data port using its standard RJ11 telephone jack. The interface cable is defined by the OEM manufacturer or private user according to their specific input connections on their equipment. X10 PRO does not sell this cable. This Two-Way Version allows developer to send X10 Commands to an X10 Receiver Module as well as Receive an X10 Command from a Controller in the installation.
Specific Requirements
120VAC Power
Electrical Protocol
Nearly all residential homes are wired SPLIT-PHASE. Each 120V Phase is NOT directly connected with the other 120V phase. If after installation, an X10 Receiver does not respond to a remote Controller, then check to ensure that the breaker serving the X10 Receiver is on the same phase as the Controller. If not, the breaker can be changed to the opposite phase. An alternative solution is recommended, to install a Phase Coupler for improving remote communications throughout the home. See www.x10pro.com, then select Technical Support and PLC Troubleshooting.
Installation
Create a cord to match the manufacturer's pin-outs to the PSC05 pin-outs below. 1. Zero Crossing Detect 2. Zero Crossing Common 3. X10 Data Output to OEM 4. X10 Data Input from OEM
Led Status
- Constant LED - ON: The PSC05 is AC powered and ready. After plugging in the RJ11 cable to the OEM device, the LED should stay constant ON.
- Short Wink: Indicates that a valid command has been received by the PSC05 from the OEM Equipment and re-transmitted over the AC powerline, or a valid X10 Command has been transmitted in the installation and received by the PSC05 and assed to the OEM Equipment. This occurs each time a valid X10 Command is sent from or received by the OEM equipment. The PSC05 is a bi-directional pass-thru module having no buffer.
Note: If the LED goes out after you plug in the OEM device and cable, you may have a defective OEM port, or the wrong cable. Make sure you have identified each pin (1-4) to match that of the manufacturer's communications pin-out requirements
