We are using different sensor nodes for our project. These are:
1. TelosB
2. WaspMote
3. emote
4. Shimmer
5. IITH-mote
6. EZ 430
The selection of sensor node depends on your application. emote is quite good and powerful sensor node which includes 32 bit arm processor with 1 MB program memory.
Well internet of things would actually be having device to device communication as the basic unit. Wireless sensor networks are used and designed according to specific application. So the motes and the access points are designed according to the application. Now for IoT and D2D already available sensor nodes or motes can be used but in the future i think the functionality of motes would be integrated into the chip set of the specific device. Attached is the link to a workshop with very good presentations and documents for your help and jump start. Anyhow this topic is open and very good area for research.
http://docbox.etsi.org/Workshop/2013/201311_M2MWORKSHOP/
The most important difference between the nodes that will be part of the IoT and classical WSN nodes is the IP connectivity. Motes in IoT are IP-enabled and thus are provided with an IP adresse (6lowPAN) allowing them to interact with remote nodes in an end to end way. Contiki OS implements a lightweight IP stack into classical WSN nodes (e.g. Micaz, Tmote, ...etc.).
To get deeper into the topic 6LoWPAN I would recommend the book by Shelby and Bormann named "6LoWPAN: The Wireless Embedded Internet". It gives a very good introduction into the topic. Implementations exst for TinyOS and Contiki devices. Concerning device diversity I would recommend the page http://www.snm.ethz.ch/ where you can finde different commonly used devices and specifications. I am currently working with TelosB, OPAL, and IRIS under TinyOS.
@Corinna Schmitt : Thank you for your guidance, can you give me some idea about the results and reliability of Contiki-OS in comparision with TinyOS ?
@Abhay Bhuva: I would if I could. I have only experiences with TinyOS. I think there the advantages is in the modular structure and the big community. I currently try to transfer my existing solutions to Contiki, but I am still at the beginning. Concerning TinyOS we have very good results even on different scenarios and network sizes, as well supporting heterogenity in one running system.
Can any comment on the operational differences between TinyOs and Zigbee? Are there any benchmarking results published anywhere? We develop TinyOs based solutions but are really concerned if this is the best way to go
I would like you also to visit the attached website for applications on smart cities and internet of things and D2D communications.
http://www.libelium.com/
I'd say IEEE802.15.4k LECIM is the way to go. It is optimised for low bandwidth and critical communication, and makes for a robust self-healing network at distances beyond 10km and runs in ISM band.
We are using different sensor nodes for our project. These are:
1. TelosB
2. WaspMote
3. emote
4. Shimmer
5. IITH-mote
6. EZ 430
The selection of sensor node depends on your application. emote is quite good and powerful sensor node which includes 32 bit arm processor with 1 MB program memory.
@Chandra Shekhar: do you have any experence with motes those are more reliable, robust, low power consumption and high energy scavanging mechanisam in building underwater IoT Application?
Yes, our team (10-15 members) is working with sensor nodes. The selection of node depends on the application. You can use sensor nodes for underwater applications but packaging would be the problem. I do not have any about your network size & communication range.
@ harm Smit: Emote is a new platform jointly developed by the Ohio State University & Samraksh Company. Google it https://samraksh.com/
I just would like to say something about Contiki OS which is a lightweight WSN OS targeted to IoT applications. Maybe all the motes supported by it can meet your requirement. You can check it Wiki:
https://github.com/contiki-os/contiki/wiki
In its platform section, you can fould them, such as Sky, Avr, Z1, Senslab, arduino and etc. Perhaps, you need to notice the emerging protocols, such as 6LoWPAN, RPL and CoAP, which are the real IoT protocols. Btw, Contiki supports all of them.
If you prefer to looking for some more reliable platforms for building your own product, Atmel provides lots of solutions can help you start, especially with its Bitcloud stack.
I am here also want to present the work of our team. You can access our website and have a look at our platform, demo and etc. And our platform is totally ready for IoT/WoT applications and related deployment. The link to our team is below:
http://edss.isima.fr/sites/smir/site/index
Apart from motes (full-fledged with mem, sensors, and communication modules), the infamous Arduino MCU boards are also a good choice. You can prototype so many good things out of those using stackable shields. There are attempts to port Contiki OS to Arduinos. I myself have developed a product with Arduino Due + shields + Contiki for Calipso project http://www.ict-calipso.eu/
Naturally, Raspberry Pi is good as well, low-cost, powerful, computer-like.
Another option is to use the open-source software stack provided by UC Berkeley:
https://openwsn.atlassian.net/wiki/
And the openmote hardware:
http://www.openmote.com/openmote-cc2538/
- Badges
- Science topic