Yesterday we presented our project, and seems that some confusion was made around the stone, but I’ll get there latter in the post.
For now, we have well defined the problem we want to solve:
We want to create something that will make communication in places that have no network possible, and we seems to be favoring hostile places.
Some of the key points we will be dealing with will be:
– Rounting a message trough a network where every node may change it’s position (what complicates a lot the idea of sub-networks and the facilities it creates for routing)
– Easely creation of rounting points (even though we must work without them, we must make good use if we have one)
– Long distance (If you are lost it is important to find anyone that may be around you and it reduces the need of fix routing points between the nodes)
– Long battery (If you are in a place with no other network, it seems fair to believe you won’t have many means to recharge your device, so the battery life may become a life-death issue)
– Obstacle penetration (As said, we want to keep in mind the hostile places)
In the first days, we were thinking about creating 2 different devices:
The zombies: A device we could use to send and receive messages (with authentication and other crypto functionalities if needed) and that would also route messages to other nodes of the network.
The stones: Devices that would only route the messages.
Now we come to the point of the confusion:
The part of routing the message will be the hardest one to make, and once it is done, every device that implements it can use the network. We started thinking in the possibility of making the stone an inteligent device, which we could branch other peripheral ones, and the zombie would be but a stone with a peripheric. We then thought that this would increase a lot the stone complexity, so an other option would be:
The stone would be something like a wireless adapter, or the xbee, something you could develop whatever device you want and just branch the stone in it so it would be compatible with the WaDeD network.
With this philosophy, we would make easy and cheap to develop devices compatible with the WaDeD network and the battery would become a problem to the device developer.
Since this was an idea that was constructed over an other, we ended up with the same name for both concepts: “stone”
Which is very confusing indeed.
We will make sure to see this trough and separate both concepts in a more clear way.
As for the technology we’ll be using, we are very favorable for using Dash7 since it fits like a glove in all our needs. Now we need make some tests and research just to verify if it has blinded us with all it’s powers or if it really is the most shining thing we can find. (Although reaching trough all the nine flors from maisel is was quite something!)
Other dangerous options (but cheap) would be making our own dash7 by using the MCU CC430 (CC430F5137) and using opensource softwares that implements the dash7 on it. (As I said, a dangerous option, but we’ll be living with zombies anyway)