Engineers sometimes joke that a cable is a source of potential trouble connecting two other sources of potential trouble. Now, with low-cost, easy-to-use RF systems on chips, you can eliminate that intervening cable in many limited-distance applications. These applications include situations in which it would just be nice to avoid a cable, such as between a handheld control box and the unit it is managing, and those in which a cable would defeat the application, such as with a remote-keyless-entry (RKE) lock for a car or house. In many ways, though, cheap and easy RF links are enabling new applications that are sometimes possible, but usually impractical, with wired links.Several forces drive wireless links. First, there's end-user convenience. Mass-market applications, such as ubiquitous infrared TV remote control, have created expectations that are hard to dismiss once you have been spoiled by the cable-free freedom that such applications provide. At the same time, IC vendors have pushed their processes, products, and clocks into the multimegahertz and even the gigahertz range, so the frequency bands you need for RF are a natural part of their components' operating range. These ICs can often function without special external circuit elements for frequency upconversion and downconversion.
You need no longer assemble your RF link from a handful of discrete—and sometimes pesky—active and passive components. Even better, these IC-based links consume little power and operate in bands for which no individual licensing and few regulatory requirements exist. As long as end users stay within the designated frequencies and power levels, they have no paperwork to deal with.
But don't think that effectively using these latest generation RF ICs for dedicated, point-to-point links is trivial. You need to study numerous issues if you make a commitment, because the various RF ICs differ in many related parameters, such as frequency, completeness, and overall performance.
Reach out and touch the receiver
Your first decision involves the range you need to reliably reach. At the milliwatt power levels of these ICs, which include the final-stage power amplifier, you can reach at least several meters and as much as 100m or more under favorable conditions. If you need longer range, you could add an external booster RF stage. However, adding this stage introduces problems, including regulatory issues, power-consumption concerns, additional components and cost, and signal overload at the receiver when you move closer. (And you could use a receiver with a wide-ranging automatic gain, which adds more complexity.)
Another alternative is to use a directional antenna. Again, this simple approach is often impractical for several reasons. It increases effective radiated power (ERP) in the target direction, which you usually must keep below some regulatory limit. You can, though, use a directional antenna at the receiver without regulatory concerns, but then you restrict the user's freedom of movement .
You also need to look at the trade-off between a simple, unidirectional, simplex link and a bidirectional, half-duplex link. Many applications, such as RF identification (RFID) and RKE, need only a simplex link but benefit from a two-way signal path. A simplex link gives you no confirmation that the system
received the signal. If you're locking or unlocking your car, the car horn gives you audible feedback, and you're all set. But if you are setting an alarm system as you leave a building, you may want either confirmation that the system properly received and implemented your arming signal or feedback about why it did, such as when an alarm zone isn't set properly. The one-way link also restricts some security algorithms (see sidebar "Proper security lets you rest better").
Although a half-duplex system requires more components than a simplex one, it luckily involves little extra design complexity on your part in these low-power links. The only common system element is the antenna, and, because the link is not full-duplex, the receiver's front end need not to be active while the transmitter is on. Therefore, your design need not filter and separate the receiving and transmitting bands, and the transmitter power-on state doesn't saturate the receiver front end.
Most of these low-power, short-distance RF links operate with low or sporadic duty cycles and short messages, so you calculate power consumption at the transmitter differently from at the receiver, which must always be at least in a standby, listening, or polling mode. You use a typical RKE unit several times a day but only for a few milliseconds each time, so battery life of one to two years is practical. Although each application is different, most target an operating life of at least two to three years from a battery.
Note that if your application involves periodic messages, such as an entry point in an alarmed system that needs to tickle its central controller to confirm that all is still OK, then transmitter power consumption and operating voltage are more critical. You have to weigh that aspect of your design and perhaps go to larger capacity cells or higher operating voltages. Also, be sure to consider any microcontroller's power needs in your power budget.
The inherent nature of wireless links is that you use them in casual, nonfixed-location applications; thus they are subject to temperature extremes, rough handling, and abuse. In these cases, the highly integrated approach gives you a distinct advantage, because every component you eliminate not only contributes to greater mean time between failures, but also keeps the link operating range at its nominal value. By their nature, RF circuits are subject to detuning, drift, and other sensitivities, and it's likely that the range you can guarantee over the long term will decrease dramatically with the amount of inevitable user abuse and environmental stress. You need to life-test your product under realistic operating conditions so you don't have irate users calling you in 12 to 18 months to complain that their garage-door-opener range is drastically shrinking or that the link operates erratically.
The design and implementation of your receiver are more difficult than those of the transmitter for several reasons. The transmitter has a deterministic task: taking a known signal, encoding and modulating it onto a known carrier only on demand by the user, and providing enough RF power. In sharp contrast, the receiver has the unenviable signal-processing task of always being alert or polling while tuning for a distorted, noise-laden signal in the spectrum. It needs to extricate this signal despite unfavorable SNR, interference, and component-parameter drift.
For these reasons and others, many vendors of RF ICs are concentrating on the receiver end of the link, because that's where they add the most value, implement circuit techniques that are most beneficial to you, and reduce most headaches for design engineers. This difference between transmitter and receiver, though, shouldn't lull you into complacency about the transmitter implementation. Unless you are confident of your ability to develop and qualify your own design, you still need to determine whether the receiver vendor offers a matching transmitter or a reference design that you can use if you want to minimize your risk.
You should also consider the frequency that fits your application and market. In general, lower frequency designs are easier to lay out and debug, but these designs have several drawbacks. They require larger passive components (some passives are inevitable), and they operate in more crowded bands. The trend for RF links in the last few years has been to migrate from the 200- to 300-MHz spectrum to the 300- to 400-MHz region and even as high as 900 MHz. Units are even available for the 2.4-GHz ISM (industrial, scientific, and medical) band. Note that the virtue of 2.4-GHz operation is regulatory as much as technical. Its operating frequencies and constraints are nearly uniform throughout the world, so you can use one design—or minor variations of that design—everywhere.
Diverse architectures to the rescue
In the world of receivers, the venerable superheterodyne architecture that EH Armstrong developed in the 1930s is the predominant design for most applications. The superhet converts any received carrier to a fixed IF, which the receiver then demodulates and processes as needed. This excellent architecture, which engineers have refined over the many years of its existence, simultaneously solves several conflicting problems. (Only in recent years has a direct-conversion, zero-IF architecture become practical for some applications.)
Unfortunately, the full superhet is too much of a good thing for low-cost, low-power receivers, which target a single-channel, single-modulation signal. RF-IC vendors thus strip whatever they don't need from the receiver, based on the fairly limited flexibility that the receiver needs in this limited-function application. In some cases, they have even abandoned the superhet for simpler designs, again with limited functions and optimized for one task only. Ironically, one of these designs is the super-regenerative receiver, which Armstrong also developed but before he did the superhet. (He soon found the operating limitations of the super-regen, despite its simplicity, too severe for general-purpose use.)
As with most components and systems, you must be aware of some element of specmanship. Especially true of receiver-sensitivity specifications, many legitimate and difficult-to-compare ways exist to specify the maximum data rate, such as determining with which bit-error-rate (BER) value, input bandwidth, modulation factors, and duty cycle you are taking the measurements. You need to question vendors about the test setup they use if you are running near the maximum potential of the link.
A good example of what you can get today is the Micrel MICRF receiver family, which comprises 418- to 433-MHz- and 900-MHz-band devices. The lower band, 16-pin MICRF002 and eight-pin MICRF022 and higher band, but otherwise similar, 16-pin MICRF003 and eight-pin MICRF033 use an architecture that eliminates the need for manual tuning of each unit (
1). These superhet receivers, which target on/off keying, or amplitude shift keying (ASK), require few external components: a 47-nF capacitor, a 4.7-µF capacitor, and an inexpensive, 6- to 7-MHz ceramic resonator. These ICs need no filters or inductors.
| It's a Rodney Dangerfield situation When you consider that the antenna in a wireless link consumes no power and costs almost nothing, it's no surprise that this vital element gets so little respect in the design process. Yet, antenna design affects the range you can achieve, as well as the packaging of your product. In most of these applications, the antenna must be entirely within the enclosure, so there is no danger of its getting bent, broken, or lost. It's easier to achieve this goal if you give the antenna design some consideration early in the design cycle. At the frequencies at which these links operate—several hundred megahertz and higher—you can build a relatively efficient antenna in a roughly 2- to 4-in. (5- to 10-cm) space as part of the pc board. The antenna can be a monopole, which is usually a quarter-wavelength long (a shorter antenna results in reduced range); a helical coil; or a simple loop. Each offers trade-offs in overall size, board area, and potential range. Also, although you probably want a nondirectional antenna, every antenna has some relative peaks and valleys in its radiation pattern, so you also have to keep that factor in mind. A directional antenna at one or both link ends has other practical drawbacks. You can't assume that the antenna points toward the complementary end of the RF link. This situation may be true for some applications, but for most, such as keyless locks, RF identification (RFID), security-system points, and operator remote controls, you have to assume a random and changing orientation between the transmitter and the receiver.
You can assess flat antennas and their various geometries using 1, which compares attributes of patch, slot, ring, spiral, bow-tie, and other configurations. Also check out 2 which, despite its title, is actually a good, practical source of information on using the vendor's components, general design considerations, and antennas; it also has a good bibliography and references.
REFERENCE
|
| Proper security lets you rest better Most RF-based links need to consider issues of security and user authentication. When you use the link as a keyless lock, for example, you need to ensure that the signal is from a legitimate user. Because it's fairly easy to eavesdrop on a link and record any user-code pattern for later playback, you also need to change the code each time you use the link, so that this recorded version is useless for spoofing the system. Even if you are not worried about security because you have a casual application, such as a remote control for a media-room music system, you still need to make sure that noise and stray RF signals don't falsely trigger the link.The bad news is that the mathematical basis for encoding data streams is complex. Don't despair, though; there is good news here, too. The actual circuitry for basic encoding and validation based on the theories is relatively simple, and advances in digital circuitry now mean that you can get fairly sophisticated algorithms embedded in ICs that implement inexpensive, easy-to-use, and highly secure code schemes.The simplest techniques use a rolling code generator, which changes the security pattern each time a user activates the link, following a starting seed code. The transmitter sends its code, and the receiver computes its own version and compares the two. Both the transmitter and receiver must be aware of this starting seed and the rolling algorithm. This method is an effective way to provide your single-direction link with a reasonably high degree of security.
For more protection, you need a two-way link. The user sends a coded signal, and the receiver executes an internal algorithm based on this signal and responds to the originator. The originator then compares the received signal with what it would expect to see returned from the target and sends an OK or a not-OK signal. Unlike basic one-way coding, this more complex challenge-and-response scheme can defeat many sophisticated break-in techniques. You also have to deal with the practical issue of replacing a lost or malfunctioning transmitter or receiver, so the security scheme needs a learning algorithm that does not require the end user to deal with the IC or remote-keyless-entry (RKE) vendor in the field.
Despite the underlying complexities of these algorithms, manufacturers are routinely using them in low-cost links, such as car and door wireless keys. For example, the HCS412 code-hopping encoder and transponder from Microchip Technology puts a 64-bit encoder key, a bidirectional challenge-and-response protocol, and code-hopping encryption into an eight-pin package (Figure A). This IC can function as the security core of a larger wireless key or can become a batteryless transponder when the battery fails. Its internal EEPROM is set at the factory with an encoder key, serial number, and configuration data and is inaccessible at any pin for additional security. The embedded technology is also available from the vendor without the associated transponder circuitry for designs in which you have your own preferred RF circuitry but need the encoder and decoder security functions. IT is a useful discussion of the characteristics and practical advantages and disadvantages of various security techniques with respect to secure learning systems.
REFERENCE
|
| For more information... | ||
| For information on subjects discussed in this article, use EDN's InfoAccess service . When you contact any of the following manufacturers directly, please let them know you read about their products in EDN. | ||
| Chipcon Components AS http://www.chipcon.com/ Circle No.323 | Digital Wireless http://www.digital-wireless.com/ Circle No. 324 | Infineon Technologies http://www.infineon.com/ Circle No. 325 |
| Level One http://www.level1.com/ Circle No. 326 | Micrel http://www.micrel.com/ Circle No. 327 | Microchip Technology http://www.microchip.com/ Circle No. 328 |
| Mitel http://www.mitelsemi.com/ Circle No.329 | Motorola http://www.motorola.com/ Circle No. 330 | National Semiconductor http://www.national.com/ Circle No. 331 |
| Philsar Electronics http://www.philsar.com/ Circle No. 332 | RF Micro Devices http://www.rfmd.com/ Circle No. 333 | RF Monolithics http://www.rfm.com/ Circle No. 334 |
| RTX Telecom A/S http://www.rtx.dk/ Circle No. 335 | Texas Instruments http://www.ti.com/ Circle No. 336 | |
Tags: air conditioning, building-department, drive wireless, energy management; and heating, RF ICs, ubiquitous infrared TV remote control, ventilation
