Beruflich Dokumente
Kultur Dokumente
By Ashish Garg, Product Marketing Manager & Angad Singh Gill, Product Marketing Engineer, Cypress Semiconductor Corp. Powerline Communication (PLC) is a communication technology that uses powerlines as its communication medium. The data travels over the same powerline that provides electricity, thus allowing the existing powerline infrastructure in homes or cars to be used for the purpose of transporting data without adding new wires. PLC technology is experiencing a period of rapid growth and finding its way into multiple applications and market segments including smart grid, lighting control, solar panel monitoring, energy metering, in-home video distribution, and electric cars. The global push for energy conservation is driving the need for intelligently communicating with energy generation and energy consuming devices. PLC offers a unique no-newinfrastructure approach to enabling rapid deployment of smart energy management technology around the world. Unlike wireless solutions, PLC does not have limitations of line-of-sight and short transmission range. PLC is also a cost-effective and easy-to-install technology for many applications. Today, systems designers can source PLC devices from more than ten different semiconductor vendors. Many of these devices are optimized for particular applications and markets. With such a wide range of choices, developers need to understand the factors that affect the performance and reliability of PLC systems and the different options for overcoming common design challenges. Any communication system consists of four major components: 1. 2. 3. 4. Transmitter Receiver Communication medium and The signal itself.
As mentioned earlier, the communication medium in PLC is the powerline. Figure 1 shows a block diagram of a generic Powerline Communication system. The Transmitter modulates and injects the signal into the powerline. The receiver at the opposite end of the link demodulates the signals and retrieves the data. The impedance of the powerline attenuates the signal as it travels to the receiver. Any noise in the medium also corrupts the signal as it moves through the powerline.
Figure 1: Block diagram of a typical Powerline Communication System. Impedance of the Powerline attenuates the transmitted signal. Noise in the line can significantly affect the signal.
Designing Reliable Powerline Communications Published in EDN (http://www.edn.com/article/511709-Designing_reliable_power_line_communications.php) Page 1 of 8 December 2010
Having briefly covered the basics, let us dive one-by-one into the factors that affect the performance and reliability of a PLC system. These factors include: 1. 2. 3. 4. 5. Transmit signal strength Noise on the powerline Impedance of the powerline network Network Protocol Receiver sensitivity
Recommendations regarding each of these factors are made along the way. In the end, multiple phases and system costs are also discussed.
Figure 2: Impulse noise on the Powerline Continuous noise, on the other hand, is more predictable than impulse noise (see Figure 3). Continuous noise is usually a function of the quality of the powerline installation in a neighborhood, city, or a country. As the powerline infrastructure was originally designed to efficiently carry power and not data, little attention was paid to noise levels on the line when powerlines were installed. Depending upon what part of the world a system operates in, powerlines can be more or less noisy.
Continuous Noise
Time
PLC Signal
Figure 3: Continuous noise on the Powerline To enable robust communication over the powerline, the Signal to Noise Ratio (SNR) needs to be maintained above a certain threshold. If there is high-amplitude, continuous noise within the frequency range of the PLC system, it is best to isolate that noise either by moving it away from PLC receivers, or by adding a blocking inductor to the power supply of the noisegenerating equipment to attenuate that noise frequency below the SNR of the receiver. There are several other techniques that developers can use to overcome the effects of noise: Bidirectional communication: If a PLC system communicates in only one direction, then there is no way for the transmitter to know whether communication was successful or not. This was one of the biggest shortcomings of the original unidirectional X10 PLC technology. Bidirectional communication allows the receiver to send an acknowledgement after successful reception of data. In case an acknowledgment is not received, the transmitter can take corrective action. Retries: In a bidirectional system, communications can be confirmed through an acknowledgment mechanism: if the transmitter does not receive an acknowledgement from the receiver, then an intelligent transmitter can re-send data packets. Retries, if automatically built into a PLC implementation, can be a very powerful means for achieving high reliability communication over the powerline. Error detection: Even after a data packet is successfully received, it needs to be checked for any damage by noise. This is where Cyclic Redundancy Checks (CRC) comes into play. CRC enables the receiver to detect any errors in data packets as they are received. When an erroneous data packet is detected, the receiver can choose to either request the transmitter to resend the packet or to not acknowledge the data (with the result of triggering an automatic data packet retry by the transmitter). Adaptive gain control: To overcome the effects of continuous noise, some PLC devices implement adaptive gain control (AGC). Using AGC, the receiver dynamically adjusts its sensitivity above the noise floor so that it can better differentiate between noise and data.
Clearly, the more ways a system can accommodate or overcome noise, the more reliable the system. It is beneficial to have acknowledgement-based bidirectional communication coupled with retries and CRC.
Network Protocol
A robust and error-free network protocol perhaps has the greatest impact on the reliability of PLC communication. While the system design has very little to no control over physical factors like noise and powerline impedance, a powerline-optimized network protocol implementation can significantly improve PLC performance. A network protocol can make or break a PLC system and it is possible to achieve 100% successful PLC communication with the right network protocol. Consider that most PLC applications support tens to hundreds of nodes connected on the same powerline. The network protocol arbitrates data packets between nodes so that all nodes can share the available bandwidth on the line fairly and no one node can monopolize the communication channel. The definition and implementation of the network protocol also determines the maximum number of PLC nodes that can communicate over the same line. Most techniques discussed in the Noise section of this article can be built into the network protocol; for example, acknowledgement, retries, and CRC. This way the application running on the PLC system will not have to worry about implementing these techniques. From an application standpoint, the software will receive only valid PLC data. Some PLC devices come with a built-in network protocol while others require developers to define, code, and manage their own. If the protocol cannot be run on the PLC device itself, developers will need to take into account having to specify another processor to implement the protocol. Another important aspect is interoperability and co-existence. The CENELEC-mandated Carrier Sense Multiple Access (CSMA) implementation (see Figure 4) ensures that one set of PLC nodes can co-exist with those of other vendors. With the incredible growth in PLC-enabled devices, this is an important way to future-proof the deployment of PLC devices.
Figure 4: Multiple PLC nodes sharing the same Powerline. The CENELEC-mandated Carrier Sense Multiple Access (CSMA) scheme ensures that multiple nodes can co-exist on the same Powerline and efficiently share access.
effective communication distance. However, high sensitivity is not always good. A high-sensitivity receiver, for example, will not only detect smaller signals, it will also detect smaller noise in the channel. Therefore it is important to have a mechanism in place that will prevent the receiver from confusing noise for the actual signal. Adaptive Gain Control (AGC) is one such mechanism for achieving this. As discussed earlier, using AGC the receiver dynamically adjusts its sensitivity above the noise floor so that it can better differentiate between noise and data.
Multiple Phases
Most buildings have multiple phases produced by a transformer which is rated for 50Hz/60Hz. As most PLC signals operate at a much higher frequency, there is a possibility that the signal will get filtered out at the transformer and consequently not be able to jump to the adjacent phase. This adjacent phase may be in the same house. This creates a potential problem where the PLC signal cannot reach all sockets in a house or structure. However, this is completely dependent upon the design of the transformer. The way to solve this problem is to couple the PLC signal from one phase to another. Two well-known techniques to do this are: 1. Capacitive phase coupling: This technique requires connecting a capacitor across the phases at the transformer, and this will allow the PLC signal to pass. Physical access to the transformer is required here and in many circumstances this approach might not be feasible or cost-effective. Wireless phase coupling: In this technique, the PLC data is transmitted from one phase to another using two Radio Frequency devices one connected to each phase. These two devices can be connected to any sockets on the phases, as long as they are in range of each other. Physical access to the transformer is not required to implement this technique.
2.
Wireless coupling is much less intrusive to the transformer and is thus preferred over capacitive coupling, in most cases. Some PLC devices come bundled with wireless coupling options while others leave it to designers to develop a way to couple phases on their own.
System Cost
While reliability is a key design factor, PLC architectures must also minimize system cost in order to compete in the market. When adding PLC to a system, some designers aggressively negotiate chip price while ignoring the overall cost of adding PLC functionality to their systems. A more holistic look at PLC cost adder to a system is warranted. PLC costs can be broadly categorized into bill of material (BOM) costs and development costs as broken out in Figure 5. The BOM cost includes the cost for all the ICs and components that make up the system including PLC and other system relevant functions. Development cost, on the other hand, includes the cost of other resources, including: Network Protocol implementation Board and layout design Certifying product to FCC, CENELEC, and UL standards.
SystemCost
BOM
Development
PLC
System Functions
Network Protocol
Powerline ReferenceDesign
Certification
MODEMIC
Energy Measurement
FCC
Network ProtocolIC
DisplayLCD
CENELEC
CouplingCircuit
UL
Network Protocol
CSMA Retries ACK
Cypress Semiconductor 198 Champion Court San Jose, CA 95134-1709 Phone: 408-943-2600 Fax: 408-943-4730 http://www.cypress.com
Cypress Semiconductor Corporation, 2007. The information contained herein is subject to change without notice. Cypress Semiconductor Corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a Cypress product. Nor does it convey or imply any license under patent or other rights. Cypress products are not warranted nor intended to be used for medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement with Cypress. Furthermore, Cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress products in life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies Cypress against all charges. PSoC Designer, Programmable System-on-Chip, and PSoC Express are trademarks and PSoC is a registered trademark of Cypress Semiconductor Corp. All other trademarks or registered trademarks referenced herein are property of the respective corporations. This Source Code (software and/or firmware) is owned by Cypress Semiconductor Corporation (Cypress) and is protected by and subject to worldwide patent protection (United States and foreign), United States copyright laws and international treaty provisions. Cypress hereby grants to licensee a personal, non-exclusive, non-transferable license to copy, use, modify, create derivative works of, and compile the Cypress Source Code and derivative works for the sole purpose of creating custom software and or firmware in support of licensee product to be used only in conjunction with a Cypress integrated circuit as specified in the applicable agreement. Any reproduction, modification, translation, compilation, or representation of this Source Code except as specified above is prohibited without the express written permission of Cypress. Disclaimer: CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Cypress reserves the right to make changes without further notice to the materials described herein. Cypress does not assume any liability arising out of the application or use of any product or circuit described herein. Cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress product in a life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies Cypress against all charges. Use may be limited by and subject to the applicable Cypress software license agreement.