Design Article

What's Required for RF4CE?

Peder Rand, Texas Instruments

8/4/2008 2:45 PM EDT

Radio Frequency for Consumer Electronics (RF4CE ) is a radio protocol standard for remote control of consumer electronics. Standardization is being driven by a consortium comprised of Panasonic, Philips, Samsung Electronics, and Sony Corporation. Their goal is to provide more value to the customer through increased reliability and novel features made possible by two-way RF communication when applied to remote controls.

The main advantage of RF4CE is that it ensures interoperability between remote controls and audio/visual (A/V) devices that IR never achieved. The protocol's upper layers are defined specifically for remote control, while the lower layers (including physical layer) uses IEEE 802.15.4, on which ZigBee and 6LowPAN are also based. IEEE 802.15.4 is used in a wide variety of proprietary protocols in both consumer and industrial markets. Advantages include low power consumption, robustness, long range, worldwide deployment in the 2.4GHz band, and a mature market of devices. When evaluating a radio for any given application, there are a multitude of parameters to consider. This article highlights those with the greatest impact on the user experience in a typical remote control application.

Achieving Longer Battery Life with RF Remote Controls
In a remote control system, usually the remote control will be battery-driven and the controlled device mains powered. This imposes different power consumption requirements for the two devices.

Remote Control
A remote control is usually powered by batteries that can easily deliver the modest peak currents used by an IEEE 802.15.4 radio (≈30mA). More significant is the average power consumption. A normal requirement for TV remote controls is that the battery life should be at least one year with 2xAA batteries. But an RF remote control with low-power implementation can easily achieve several years of battery lifetime. The IEEE 802.15.4 radio has three main power consumption categories: receive, transmit, and sleep mode.

These power consumption modes affect the average by the product of their magnitude, and the time spent in the respective mode. In effect, the time it takes a device to send a packet is as important as the current consumed in the TX mode. Remote controls are considered low-duty-cycle devices. That means that they are usually asleep, and wake up occasionally to use the radio, for example to send a command.

However, two-way RF remote control protocols like RF4CE enable advanced features such as displaying device status on the remote control and paging (e.g., user presses a button on the TV which causes the remote to beep making it easier to locate). These features require the remote control to wake up autonomously at regular intervals to poll the controlled device for data.

The calculation example in Figure 1 shows that a feature like paging can dominate the remote control's power consumption. This simplified calculation is based on numbers from the CC2430 IEEE 802.15.4 SoC, which has a CPU and Flash and can be used to implement a single-chip remote control. The example assumes a simple, generic RF remote control used for 50 button pushes per day. It also implements a paging function which requires the remote control to wake up every five seconds to check if it is being polled by the controlled device. When not active with a command or polling, the device goes into the PM2 sleep mode and waits to be woken by a button push interrupt or the sleep timer polling timeout.


Click for larger image

1. Remote Control Power Consumption Calculation Example

When paging is not implemented, then power is consumed by the current drawn during sleep. In this scenario, the radio has an average power consumption of less than 1μA. To put things in perspective, the self-discharge of two alkaline AA batteries is approximately 1μA. Another point of comparison is the power consumed by a traditional IR remote. The modulated IR LED draws around 50mA when a button is pressed, and draws that current for as long as the button is pressed. This can easily be hundreds of milliseconds. Power consumed during a button push for IR is around 1000mAmS, while an RF-based remote control would not even use 1/10th of that.

Controlled Devices
When a controlled A/V device is on, the power consumed by the RF device generally is not significant. This means that it can be left on continuously to minimize latency in receiving commands. However, when the controlled device is in standby mode, the RF device's power consumption becomes significant.

To achieve Energy Star certification, a TV must not, on average, consume more than 1W in standby mode. Future standards and regulations will have even stricter requirements. This leaves few mA in the power budget for the RF transceiver. Limiting the RF transceiver's power consumption means that it cannot be in a continuous receive state. Thus, the turn-on command's latency issued from the remote control will be higher than for commands sent when the controlled device is on.

There is in fact an almost linear trade-off between power consumption and latency exemplified by Figure 2, which shows a sample calculation of an A/V device in standby mode polling every 50ms. To put this latency into perspective, the minimum latency of a typical IR implementation is 110ms.


Click for larger image

2. Controlled Device Standby Power Consumption Calculation Example

Coexistence

Figure 3 illustrates a typical domestic setting consisting of A/V equipment surrounded by other 2.4GHz RF devices. Such devices typically include WiFi, cordless phones, microwave ovens, Bluetooth devices, ZigBee networks, etc. When many devices operate in the same frequency band, there is likely to be interference between them. RF interference causes lost packets, increased power consumption and communication latency. There are several ways of mitigating these effects in an RF remote control network.


3. Typical Domestic Wireless Environment

From a software remote control protocol standpoint, the most efficient way to alleviate the effects of interference is frequency agility. This is an algorithm that responds to an impaired RF link by changing channels until it finds a channel with little interference. IEEE 802.15.4 defines 16 channels in the 2.4GHz band numbered 11-26. Changing to a channel with little interference is usually possible; however, there will always be a risk of interference in the neighboring channels. An example is IEEE 802.11 radios (WiFi) that uses wider channels than IEEE 802.15.4. Where several WiFi networks are present, Figure 4 shows that even if your remote control has moved to channel 20 where there is little interference from WiFi channels, the adjacent channels will have interference if an active WiFi network uses channel 6.


4. IEEE 802.11 and IEEE 802.15.4 Channel Plan [1]

RF receivers are interfered with by devices operating on the same channel as well as signals transmitted at neighboring frequencies. Selectivity is a measure of how much interference the receiver can tolerate from a strong interferer transmitting in a neighboring channel without getting packet errors. Selectivity or jamming resistance is referred to as adjacent and alternate channel rejection in IEEE 802.15.4 and is measured in dB. Good selectivity in a receiver is a hardware parameter of the receiver and can be found by looking at a device's datasheet. High selectivity is achieved in devices such as the CC2520 through a combination of high-performance analog and digital filters.


Next:




Please sign in to post comment

Navigate to related information

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)

Feedback Form