Design Article
Clearing the confusion on battery life and range for 2.4-GHz low power RF
Shone Tran, Cypress Semiconductor
1/26/2009 2:01 PM EST
This article explains why these specifications are misleading and how they can lead designers to choose non-optimal approaches. It will show how to accurately evaluate power consumption and range, how to use link budgets, and how to work with current profiles to maximize sleep time, minimize retries, and avoid interference.
Wireless embedded control applications are low data rate (less than 2Mbps), low-power (can be battery-powered for years), and typically operate over 10-50m range. Some example applications include low-power sensor networks for medical (patient monitoring), remote control, industrial process automation, home/commercial building automation, asset management, and precision agriculture. In these applications, data rate is very predictable because it is ultimately limited by just protocol overhead.
The other key aspects of a wireless technology, power and range, happen to be the most misunderstood and confusing specifications to evaluate when choosing a wireless technology. Many vendors advertise their radio's power consumption and range in numbers that are not entirely useful for designers because the figures will vary depending on the application and don't take noise and protocol into account. This makes choosing a wireless technology that predictably achieves design specifications very difficult.
Chip vendors are not entirely at fault because it's difficult to agree on a standard way to specify performance under different noise environments and wireless protocols. Therefore, to make the best decisions while evaluating wireless solutions, embedded wireless firmware engineers need to consider how they should evaluate power and range, as well as how they will optimize these parameters for a low-power RF application. This article will address these issues in the context of 2.4-GHz low-power RF technologies since the 2.4-GHz ISM band is unlicensed worldwide.
Starting with Power
For power, let's first consider the misleading information found in datasheets. Then we'll look at what parameters really affect power performance the most followed by some suggestions for how to optimize power consumption in typical environments with interference.
- Some vendors go as far as quoting years of battery life with no qualification of what conditions the radio is operating under. And really, every vendor will quote different conditions so it's difficult to have an apples-to-apples comparison between radios.
- Except for transmit/receive modes, different vendors have different names for operating modes, including: Off, Hibernate, Doze, Idle, Sleep, Standby, Standby-I, Standby-II, and Power Down. Each of these modes has different functionality available depending upon the chip, so it's very difficult to figure out which radio will give you predictable performance.
This said, most 2.4-GHz radio's datasheets will highlight transmit, receive, and sleep currents for evaluating power. To give an idea of typical ranges, you may see transmit/receive currents anywhere from about 15mA to 60mA depending on output levels, and sleep/standby currents from sub-1 uA to 30uA.
At face value, one might think that a radio which transmits at 15mA is twice as power-efficient as a radio with 30mA. Drawing this comparison would be the first of many false conclusions a designer may come to that inevitably leads to disappointment in the process of designing a long-lasting low-power wireless product.
A typical radio has the following generic modes: sleep, idle, synthesizer settle, transmit, and receive. Each operating mode has varying levels of current consumption and different radios spend different amounts of time in each mode. Also, some radios can do more in certain modes than others can, such as being able to load data into buffers or accept SPI communications to wake up the radio. Thus, calculating average power consumption over a complete transmission cycle tells a more truthful story when comparing radios.
Calculating Average Power Consumption
Unfortunately, a datasheet cannot really provide this data in a standard way. Therefore, calculating average power consumption requires some upfront work from the engineer. It's useful to map out the current profile of a high performance transceiver as the following example illustrates:

Figure 1 shows that a good radio usually spends less than 2ms to complete a transmission (from mode 2 through 5 in the figure) and most of this time is spent in crystal start-up and synthesize mode. The radio actually spends less than 518us when communicating on the air (transmit with acknowledgement received) and doesn't need to re-synthesize, leaving the crystal on and just loading the next packet for transmission. In this example, synthesize mode takes 100us on fast channels, which is actually very quick. Different channels do need different synthesize times. For most radios, you can easily expect anywhere from 200us to over 400us for the synthesizer to settle, even in fast channels. Note that for simplicity, the above diagram does not take into account up and down current ramp times.
Comparing radios using current profiles gives a much clearer picture of power performance, but we still need to consider retransmits in order to tell the complete story. Looking at the above example, transmit/receive currents are more than 20,000 times higher than sleep currents. Such a significant difference between transmit/receiver and sleep modes holds no matter what 2.4-GHz low-power RF radio is being considered. For any radio, then, each retransmission is very expensive in terms of power consumption (as well as affecting latency and throughput).
Equipped with methods to navigate through the confusion of power specs, an engineer still needs to think about implementing an intelligent protocol to take advantage of a low-power radio. As illustrated in the above example, there is clear motivation for sleeping as much as possible. This begs the point that a big part of power-efficiency is driven through reliability. Put another way, ensuring successful communication with the least number of retransmissions leads to the best power efficiency.
A power efficient radio/protocol combination may have some or preferably all of the following intelligent features:
- Frequency Agility: A way to detect interference in a channel and find a new channel. The faster a radio can find/switch channels and the more channels it has to choose from, the better. As other 2.4-GHz networks like WiFi (802.11b/g/n) occupy a broad spectrum and leave little room for other networks to operate on, narrowband signals are very desirable.
- Direct Sequence Spread Spectrum (DSSS): Instead of sending data directly onto the air to directly face interference and drop bits, a radio can minimize bit error rate using DSSS, which encodes data into pseudorandom chip-sequences known as symbols. By transmitting a chip-sequence onto the air that represents the original data, the receiving side can still recover the original data even if a number of chip errors occur. This is known as coding gain and is generally adjustable. Some radios on the market appear to consume less power compared to others because of marginally better power consumption specs, but may actually consume more power if they don't have DSSS to maximize successful transmissions.
- Dynamic Data Rate: Power-efficiency is tightly linked to reliability, but there is a delicate balance needed to achieve the lowest power because reliability could come at the expense of longer air time which in and of itself uses more power. DSSS inherently spends more time on the air to transmit the same amount of data as a raw mode of transmission like Gaussian Frequency Shift Keying. Using DSSS makes sense in an environment with noise, but typically operating environments are dynamic, with periods of both quiet and noisy time. Thus a good radio not only has DSSS, but can dynamically switch it off to take advantage of quiet times on the air and transmit faster to sleep more. A good protocol has the intelligence to decide when to use which data rate, and optimize it to minimize overall on-air time.
- Dynamic Power Amplifier Levels: Most radios have a number of power output levels to choose from, so a robust protocol can intelligently reduce the output level to transmit only as loud as needed. Such a protocol will monitor noise levels and consecutive successful transmissions to decide if a lower power output level can be used to save power and still maintain a good link.




InterestedinRF
1/28/2009 1:19 AM EST
This is an interesting article. Two points to add though - link budget is also dependent on data rate and acceptable bit error rate (BER). The higher the data rate the lower the RX sensitivity for a given BER (typically quoted as 0.1%). Secondly, Nordic's nRF24L01 is an obsolete part having been superseded by the nRF24L01+ last year. The nRF24L01+ has an RX sensitivity of -94 dBm, virtually identical to the Freescale, Atmel, Cypress and Microchip parts.
Sign in to Reply
David of Oro
1/28/2009 9:33 AM EST
No matter what the spec sheets say, the proof is in testing the finished product. Recently in the market for a "Presenter Remote," I read reviews then purchased one that had only 20% negative user remarks regarding range. Sure enough, my new remote (recently returned) had less than a 2 meter range in a very benign home environment. I completely turned off my 2.4GHz phones and had only the single PC with the USB dongle running. The transmitter appeared to have a marked orientation/polarization sensitivity. I even moved the PC to the top of a box in the middle of the room with no change in range.
Now, what do I do for a remote keyboard for my media center? Reading the reviews even for the Bluetooth keyboards, I note that even they have many negative reviews. It would seem that a low bandwidth application such as this could be made very reliable. Designers, please check your prototypes in a variety of actual user environments!
Sign in to Reply
sherifhanna
1/28/2009 7:58 PM EST
Hi Steven,
True, Nordic's nRF24L01+ part has -94 dBm...at 250Kbps. Which means that Nordic finally admitted to the trade-off of speed vs. reliability that it argued against so vigorously for so many years. It seems that Cypress had the right idea all along.
Sign in to Reply
InterestedinRF
1/29/2009 9:12 PM EST
From the CYRF7936 data sheet the figures for the Cypress part RX sensitivity are -97 dBm at 125 kbps (the figure used in the table) and -93 dBm at 250 kbps. Using GFSK at 1 Mbps the figure is -84 dBm. The Nordic nRF24L01+'s figures are -94 dbm at 250 kbps, -85 dBm at 1 Mbps and -82 dBm at 2 Mbps. In other words, a like-for-like comparison indicates there is virtually no difference in the RX sensitivity of the Cypress and Nordic parts at comparable data rates.
Sign in to Reply
sherifhanna
2/2/2009 4:51 PM EST
Hi Steven,
Oh yes, absolutely. I agree that they are comparable in terms of receive sensitivity for equivalent data rates. My point was about the fact that the Nordic parts now support a slower, more robust data rate, which is a change in its stance from before.
Sign in to Reply
InterestedinRF
2/4/2009 4:03 AM EST
The point you make is valid but remember the Nordic chips still support 1 Mbps and 2 Mbps as well as the 250 kbps rate. I guess that makes the customer the winner! Thanks for an interesting dialogue.
Sign in to Reply