Designing low-cost wireless sensor networks for real-world applications: OEM wireless sensor solutions are "ready to go" for easy installations.
Wireless systems designers are being asked to provide low-cost, high-performance, easily deployed wireless sensors networks that change the way business processes are managed and monitored.
A designer needs to be aware that along with the wireless sensor getting the sensor's data to a manageable data processing and display system is a key part of the solution. Traditional means of doing this are through a gateway to a local or web based monitoring software.
Starting with the sensor, two traditional options are available for the development of a wireless network sensor node, build it yourself or build on something that already exists--namely a module. The recent availability of OEM wireless sensor solutions offer a "ready-to-go", robust platform that can be easily integrated into existing systems or jump start new system developments for completely customized applications.
When determining whether to design a wireless sensor system or use an OEM platform, take the following tasks into consideration; development time, development team and costs, testing and certification requirements, manufacturing processes, equipment, volumes, and costs. The next graphic shows a basic comparison of building your own wireless sensing system versus using a pre-designed OEM sensing platform.
Additional considerations for the wireless sensor node include determining the frequency and protocol at which the sensor will operate, regulatory compliance needs (FCC, CE), and power source (battery, energy harvesting, parasitic). Aside from having a base modular platform to build from, a designer needs to foresee how the devices are to be used in the real world like asking how will each sensor will function. Accelerometers can be used in a variety of ways: what RF protocol(s) should be used; what kind of sensor network architecture will be supported; how will the users interact with the sensors; how will the network communicate with users; how long will the sensors last with the selected power source; etc.
A gateway device is typically needed to aggregate and transfer the sensor's data to a software application. Gateway choices range from a simple local USB "dongle" attached to a local PC, a protocol specific gateway (Ethernet, Modbus, WiFi, etc.) and most mobile being a cellular gateway--typically referred to as a M2M gateway.
The girth of IT industry protocol and connectivity standards makes it difficult for a wireless sensors network designer to select "off the shelf" gateways for use in the networks. The designer should understand the limitations of each.
Finally, a designer must realize the true value of the wireless sensor network is not in the sensor and gateway hardware; rather in the data derived, managed and disseminated from the system. Sensors act as a data collector at an end point for historical trending or logging, but a user should reliably know when a sensor is triggered so immediate action can be taken. Only then does sensor data become a useful asset.
The collection, manipulation, ordering, and notifications derived from a sensor network software platform certainly vary on a case-by-case basis. The designer should have a clear understanding of the end user's needs and expectations. Some questions to ask are: Will the sensors be mobile? Will the sensors need to report more than sensor data-such other things as battery levels or signal strength? Will there be large numbers of sensors that need to have data charted in real time and/or historically? How many users can access the system and what permissions should they have? How complete of an application will be delivered to the customer--is it a finished, branded solution or one that they have to build from scratch?
Case study of real world design:
The authors have worked extensively in the embedded electronics design space. One case study of a real world wireless sensor network came when the team was approached with the need for a "butts in seats" sensor monitoring solution for public transportation vehicles. The customer wanted to validate fares against the number of people actually riding the buses.
The manufacturer used their existing, FCC approved, proprietary wireless RF module that operates in 915, 868 and 433 MHz.
The low power module provided a point-to-multipoint topology with about 250' non line-of-site RF range. They coupled a potentiometer sensor fitted into a seat to determine the frequency and duration of occupancy. The data is transmitted real time through a cellular (GPRS) modem to an online or cloud based monitoring platform.
By using pre-designed hardware or pre-designed system solutions like in the above example, you can decrease time to deployment, reduce engineering cost and increase your company's return on investment.
By Brad Walters and Kelly Lewis, Monnit Corp., www.monnit.com
|Printer friendly Cite/link Email Feedback|
|Title Annotation:||Remote Sensors Focus|
|Author:||Walters, Brad; Lewis, Kelly|
|Publication:||ECN-Electronic Component News|
|Date:||Sep 1, 2012|
|Previous Article:||Careful designers get the most from brushless DC motors: brushless motors have many advantages, but it takes good hardware and software engineering...|
|Next Article:||Wireless switches solve the remote sensor connection conundrum: 802.15.4 networks provide reliable, robust operation.|