-126-
v5.8
Interacting with Waspmote Plug & Sense!
•
Capturing and storing sensor data
As said before, in a kit containing Waspmotes, Gateway and Meshlium, the Waspmotes come already configured to send frames
to the Gateway. Later, once the user has developed the code for transmitting to Gateway, he can switch to Meshlium.
Meshlium will receive the sensor data sent by Waspmote using the radio and it will store the frames in the Local Data Base. That
can be done in an automatic way thanks to the new
Sensor Parser
.
The
Sensor Parser
is a software system which is able to do the following tasks in an easy and transparent way:
•
receive frames from XBee and LoRa (with the Data Frame format)
•
receive frames from 3G/GPRS, WiFi and Ethernet via HTTP protocol (Manager System version 3.1.4 and above)
•
parse these frames
•
store the data in local Database
•
synchronize the local Database with an external Database
Besides, the user can add his own sensors.
The initial frames sent by Waspmote contain the next sequence (XBee API frame characters are removed here):
~\0x00I\0x90\0x00}3\0xa2\0x00@z\0xcb\0x92\0xd8\0xd3\0x02<=>\0x80\0x03#35689722##7#ACC:80;10
;987#IN_TEMP:22.50#BAT:93#\0xb4
Initially there are some hexadecimal characters, which belong to the XBee API frame, followed by the message. In the above
example the message is:
<=>\0x80\0x03#35689722##7#ACC:80;10;987#IN_TEMP:22.50#BAT:93#
They are formed by the accelerometer values, RTC internal temperature value, and battery level. The MAC address is added and
other helpful information.
In order to add your own sensor frames properly go to the section “Sensors”. All frames captured will be able to stored on Local
Database, however the frame has not been defined is stored in the database. See the picture below in order to see different
frames types and how they are saved in the database.
Figure : Different frames types
If you change any of the parameters in Waspmote or Meshlium you will have to do it in both platforms so that they still can
communicate.
