Crossbow's new eKo system has not only brought wireless sensor networks into the heart of precision agriculture, the system now also offers a quick and easy solution for anyone wanting to incorporate wireless sensor networks into their own outdoor monitoring solution. Whether they are looking to use eKo for environmental monitoring and research, urban monitoring, pollution detection, etc., this system is on its way to being the wireless sensor networking solution for any outdoor sensing requirement regardless of sensor type. eKo is fully packaged for the elements, solar-powered and ready to use out-of-the-box. This platform now provides users with a solution that requires little effort for complete customization with the new ESB developer's kit. The first phase of this kit has now been released to all eKo users.
eKo nodes (EN2100) can interface to many different types of sensors. Each of the node’s four sensor ports has a 6-pin connector that programmably interfaces to either analog or digital sensors, and each port has the ability to support two different sensors. Crossbow has created a standard interface (ESB: Environmental Sensor Bus) to communicate with a wide variety of sensors through these ports.
Phase 1 of Crossbow's ESB developer’s kit allows users to interface their own simple analog sensors that do not require any additional signal or power conditioning to the eKo node. Users will only need to program the self-identification EEPROM and wire the sensors to the connector. The EEPROM embedded in the sensor’s connector is read by the port during power-up, and this information tells the node how to communicate with the sensor and contains parameters such as the required operating voltage and power-up time. After the information is read, the node programmably changes the pins according to the ESB requirements. To request details on using Phase 1 of the ESB Developer's kit with your eKo system, visit Crossbow's site here.
Phase 2 of this kit release will support simple analog sensors requiring additional signal conditioning and/or power conditioning. These sensors use the external interface circuit between the eKo node and the sensor. The self-identification EEPROM is embedded in the Switchcraft connector.
Phase 3 will provide support for complex digital sensors that require signal conditioning, power boost or intelligent communication. These sensors use an external interface circuit between the eKo node and the sensor. They do not require that the EEPROM is embedded in the cable as the self-identification information is contained in the microprocessor.
As an example of interfacing a simple sensor to eKo, Crossbow has recently integrated the MaxBotix MaxSonar range finder along with an air temperature sensor on the same connector. The MaxSonar is an accurate, very low cost, ultra-sonic range finder that can run directly from the eKo battery supply at very low current. Also, of interest is to measure the ambient air temperature at the same time. Both of these sensors can be wired to a single eKo port connector.
The entire assembly can easily be mounted in PVC pipe fixtures for outdoor deployment. Once the two sensors are wired a Dallas DS2431 1Wire EEPROM is mounted into the sensor Switchcraft connector. Finally the EEPROM is programmed with the self-identification information. This is done using a programming board and PC program from Dallas Semiconductor. A mating Switchcraft connector is wired to the board to allow the sensor cable to be attached directly and the EEPROM then programmed.
The simplicity of integrating unique sensors with eKo, a fully packaged ready-to-use outdoor wireless monitoring device, enables users to deploy wireless sensor networks quickly, easily and effectively in a way they never have before. To request details on Phase 1 of the ESB Developer's kit, visit Crossbow's site here.




thanks Do I have to be a member to post to this blog?
Posted by: chat sohbet | May 13, 2009 at 10:18 AM
This is great stuff. I need a water level sensor and a pressure sensor capability to monitor the source side of my irrigation systems. I also need a salinity sensor to monitor my fertigations. I'm sure I'll have questions as my development progresses. Specific app notes with code snippets would be great or better yet having these sensors as part of your supported sensor set.
Posted by: mark holler | February 10, 2009 at 08:47 PM