Meshbean development board. We have used this
mote because they have leds, buttons, additional
sensors and can easily be connected other sensors
that can be used for different purpose applications of
the indoor position system, ambient living and smart
buildings, so for prototyping works quite well. They
also have a USART accessible by a USB connector,
so a PC can be connected via USB port, emulating
it a COM port, for both programming and receiving
information, in our case beacons and sensor values.
A MeshNetics´s mote is shown in Figure 2, in
this case, it has an integrated PCB antenna, but we
have used others that aren´t, this affects only the
range of coverage. This mote has a MCU wireless,
called ZigBit, a compact 802.15.4/ZigBee module
featuring record-breaking range performance and
exceptional ease of integration. It integrates both the
ATmega1281 microcontroller and AT86RF212
transceiver of ATMEL (www.atmel.com) so the
AVR tools are necessary for programming purposes.
Figure 2: Meshbean development board.
In ZigBee there are three kinds of devices, each
one having its own purpose:
1. Coordinator (C): A full function device
(FFD) that it is in charge of creating the PAN
(Personal Area Network) and typically is the point
of the WSN to acquire all sensors information from
all the other motes to be shown in a computer. The
icon uses to represent this device is a filled circle,
Figure 1 shown one.
2. Router (R): A FFD that it is in charge of
routing when the range of coverage requires this
capability, so it is possible to have dynamic
topologies. The icon uses to represent this device is
a small filled circle inside a circle, Figure 1 shown
six ones.
3. End device (ED): A reduced function
device (RFD) that is always slept (to reduce
consumption) and only wakes up to do a specific
task, for instance, to send sensor information to the
WSN, typically directed towards C. The icon use is a
not filled circle, this is, like the R icon in Figure 1,
but no filled circle inside (Figure 7).
So a ZigBee WSN is composed of one C, many
EDs and many Rs. Each kind of devices can receive
what the other transmit, if they are in the same range
of coverage, because the transmission media is share
by all one, but not all the information receive is
processed (the explanation of why this is that way is
out of the scope of this paper).
As explained in the previous section, to determinate
position, we require to kinds of beacons, beacon1
and beacon2. Beacon 1 is used to inform other
devices that a mobile mote is present and beacon2 is
used to inform C the RSSI value that a fixed mote
receives from a mobile one for location estimation.
To send both beacons in BitCloud Stack, we have to
use the information saved in a table at the network
layer called neighbor table. This table registered all
the FFD, this is, motes that are C o R, that are in the
range of coverage of a determinated mote and for
each one it registers the RSSI value of the received
signal from that mote. Periodically, a FFD device
sends a MAC layer message to inform other that is
in the PAN, so that message is used by neighbor
motes to measure the RSSI value of the received
signal and to save it in their own neighbor table. So
beacon 1 is sent automatically by the protocol stack.
As only FFD sends this kind of message the mobile
motes have to be R, as shown in Figure 1.
To send periodically beacon 2 messages, each
fixed motes search in its neighbour table to find out
if the mobile mote is in its range of coverage, if so,
the beacon 2 is sent to C with the information
required as explained in section 2. As neighbour
table is only in FFD, fixed motes have also to be R.
We deployed BitCloud solution over half floor
of our Department Area, measuring roughly 225 m.
To cover all this area we required 7 fixed motes
strategically placed. An off-line phase was required
to fill in the signature database, once it was full, the
system was ready to be tested.
Figure 3 shows the PC interface to show mobile
mote position, four in this case. It also shows the
mobile mote sensor information.
Although results were as expected as shown in
(Medina, 2011), this solution has two drawbacks, in
order to fix it correctly:
1. The mobile node has to be FFD so the power
consumption is very high and it is a problem because
mobile node is battery power.
2. The periodicity of beacon 1 messages can´t be
controlled as it is a MAC parameter not accessible
by BitCloud Stack.
FINGERPRINT INDOOR POSITION SYSTEM BASED ON OPENMAC
49