Multidrop buses began to appear in the late 70s and early 80s. One of these, Modbus from Modicon (Schneider Auto mation, North Andover, Massa chusetts), led the way into the industrial sphere, followed by several proprietary and open buses (e.g., the Manufacturing Auto mation Protocol, QBus, and VME Bus).
The emergence of intelligent sensors and microcomputers capable of operating in industrial environments irrevocably changed the sensor network landscape. Multidrop networks (buses) reduced the number of wires required to connect field devices to the host, but they also introduced another single point of failure—the cable. Several suppliers of industrial-grade products offered redundant cabling designs, but these came with an increase in complexity (see Figure 2).
Once the industry began the migration to multidrop buses, problems associated with digitization began to emerge. With the previous point-to-point systems, digitization occurred in the host, where a single clock could be used to time stamp when the analog signals from multiple sensors were acquired. With the distributed intelligence required to implement a multidrop network, synchronization of clocks became a critical issue in some applications. This remains an important design parameter for any distributed digital system.
Figure 4. An architecture consisting of a decoder for each channel and a direct-sequence spread-spectrum receiver can perform simultaneous sampling because the same baseband signal goes to each decoder. But the decoders represent a significant cost, power, and size limitation.
The introduction of Ethernet in the mid-80s was a landmark in standardization, if not technological innovation. A group of large companies agreed that the future of computer networking required an open interconnect standard that would allow multiple-vendor systems to work together with minimal difficulty.
Researchers looked closely at the carrier sense multiple access with collision detection (CSMA/CD) protocol when they investigated the behavior of networks under stress. But they considered most industrial applications too time critical for such a nondeterministic protocol. Now, fifteen years later, most factories have converted their shop floor networks to Ethernet because it is the best compromise between cost and performance. Many companies now offer solutions that use Ethernet to implement suitable robust industrial networks.
Wireless systems use the same types of protocols to implement multidrop topologies, simulating hard-wired connections with RF links. The IEEE-802.11 standard was the first wireless standard that promised to bring the interoperability of Ethernet connectivity to wireless networks. Many of these, however, are not compatible at the over-the-air level.
Point-to-Point Networks
Theoretically, these systems are the most reliable because there is only one single point of failure in the topology—the host itself (see Figure 1). You can improve the system by adding redundant hosts, but wiring two hosts can be a problem. The 4–20 mA standard allows multiple readout circuits if the standard loads are used at each readout. Problems can arise if readout devices load the circuit beyond its capability, but most designers are familiar with the limitations and are sufficiently careful.
Figure 2. In a multidrop network, each sensor node puts its information onto a common medium. This requires careful attention to protocols in hardware and software. The single-wire connection represents a potential single-point failure. But some vendors supply redundant connections to mitigate this potential problem.
Some networks provide frequency-modulated (FM) signals on the wires to carry multiple sensor readings on separate FM channels. Some standards (e.g., the HART bus) support multiplexing of digital signals on the existing analog wiring in older plants. These architectures blur the distinction between point-to-point and multidrop networks.
Early wireless networks were simple radio-frequency (RF) implementations of this topology. These networks used RF modems to convert the RS-232 signal to a radio signal and back again. Fluke (Everett, Wash ington) developed a digital voltmeter that could be configured to accept a voltage signal and transmit the signal over a dedicated radio frequency channel. The reliability of these implementations was sometimes suspect because most were designed with simple FM coding. Interference and multipath propagation effects caused significant degradation in factory environments, so many networks proved to be unreliable unless designers were particularly careful. The Federal Communications Commission licensed companies and devices to operate at the allocated frequencies.
Complete wireless local area networks (LANs) were implemented using this technique.These were successful in the office environment but didn’t fare as well in factories. Many designers implemented remote data acquisition systems with this topology by using a data concentrator in the field to feed the data to a radio transmitter for transmission to the hosts, where the signals were demultiplexed into the original sensor signals.
Figure 2. In a multidrop network, each sensor node puts its information onto a common medium. This requires careful attention to protocols in hardware and software. The single-wire connection represents a potential single-point failure. But some vendors supply redundant connections to mitigate this potential problem.
Some networks provide frequency-modulated (FM) signals on the wires to carry multiple sensor readings on separate FM channels. Some standards (e.g., the HART bus) support multiplexing of digital signals on the existing analog wiring in older plants. These architectures blur the distinction between point-to-point and multidrop networks.
Early wireless networks were simple radio-frequency (RF) implementations of this topology. These networks used RF modems to convert the RS-232 signal to a radio signal and back again. Fluke (Everett, Wash ington) developed a digital voltmeter that could be configured to accept a voltage signal and transmit the signal over a dedicated radio frequency channel. The reliability of these implementations was sometimes suspect because most were designed with simple FM coding. Interference and multipath propagation effects caused significant degradation in factory environments, so many networks proved to be unreliable unless designers were particularly careful. The Federal Communications Commission licensed companies and devices to operate at the allocated frequencies.
Complete wireless local area networks (LANs) were implemented using this technique.These were successful in the office environment but didn’t fare as well in factories. Many designers implemented remote data acquisition systems with this topology by using a data concentrator in the field to feed the data to a radio transmitter for transmission to the hosts, where the signals were demultiplexed into the original sensor signals.
The development of network technologies has prompted sensor folks to consider alternatives that reduce costs and complexity and improve reliability. Early sensor networks used simple twisted shielded–pair (TSP) implementations for each sensor. Later, the industry adopted multidrop buses (e.g., Ethernet). Now we’re starting to see true web-based networks (e.g., the World Wide Web) implemented on the factory floor.
Figure 1. In point-to-point network topologies, each sensor node requires a separate twisted shielded–pair wire connection. The cost is high, configuration management is difficult, and nearly all the information processing is done by the host.
As wireless sensors become real commodities on the market, new options or new arguments for old options are causing professionals to consider network strategies once ruled out. Let’s look at the three classic network topologies (point-to-point, multidrop, and web), assess their strengths and weaknesses, and look at how the rules have changed now that wireless systems are coming online.
In addition, to build functional sensor networks, you’ll probable have to integrate hardware and software from multiple vendors (see the sidebar “Network Questions,”). So along with everything else, you have to come to terms with standards and protocols—those that exist, those that are emerging, and those needed to ensure interoperability on the factory floor.
Figure 1. In point-to-point network topologies, each sensor node requires a separate twisted shielded–pair wire connection. The cost is high, configuration management is difficult, and nearly all the information processing is done by the host.
As wireless sensors become real commodities on the market, new options or new arguments for old options are causing professionals to consider network strategies once ruled out. Let’s look at the three classic network topologies (point-to-point, multidrop, and web), assess their strengths and weaknesses, and look at how the rules have changed now that wireless systems are coming online.
In addition, to build functional sensor networks, you’ll probable have to integrate hardware and software from multiple vendors (see the sidebar “Network Questions,”). So along with everything else, you have to come to terms with standards and protocols—those that exist, those that are emerging, and those needed to ensure interoperability on the factory floor.
definition
A sensor network is a group of specialized transducers with a communications infrastructure intended to monitor and record conditions at diverse locations. Commonly monitored parameters are temperature, humidity, pressure, wind direction and speed, illumination intensity, vibration intensity, sound intensity, power-line voltage, chemical concentrations, pollutant levels and vital body functions.
A sensor network consists of multiple detection stations called sensor nodes, each of which is small, lightweight and portable. Every sensor node is equipped with a transducer, microcomputer, transceiver and power source. The transducer generates electrical signals based on sensed physical effects and phenomena. The microcomputer processes and stores the sensor output. The transceiver, which can be hard-wired or wireless, receives commands from a central computer and transmits data to that computer. The power for each sensor node is derived from the electric utility or from a battery.
Potential applications of sensor networks include:
* Industrial automation
* Automated and smart homes
* Video surveillance
* Traffic monitoring
* Medical device monitoring
* Monitoring of weather conditions
* Air traffic control
* Robot control.
A sensor network consists of multiple detection stations called sensor nodes, each of which is small, lightweight and portable. Every sensor node is equipped with a transducer, microcomputer, transceiver and power source. The transducer generates electrical signals based on sensed physical effects and phenomena. The microcomputer processes and stores the sensor output. The transceiver, which can be hard-wired or wireless, receives commands from a central computer and transmits data to that computer. The power for each sensor node is derived from the electric utility or from a battery.
Potential applications of sensor networks include:
* Industrial automation
* Automated and smart homes
* Video surveillance
* Traffic monitoring
* Medical device monitoring
* Monitoring of weather conditions
* Air traffic control
* Robot control.
Subscribe to:
Posts (Atom)
