MerkurBoardSample

Merkur Board Device

The Merkur board is a low power wireless device communicating via the CoAP protocol. Details about the Merkur board please see http://osdwiki.open-entry.com/doku.php/en:projekte:merkur. The sample code is a CoAP proxy running on a Raspberry PI equipped with a Merkur board that acts as a proxy between CoAP and the REST protocol that M2MLabs Mainspring is using. Available CoAP resources are detected by reading from the .well-known resource. For each resource detected, the corresponding sensor models, actor models, device models and devices are created in Mainspring via the REST interface. As default a Merkur board provides sensors for cputemp and battery and an actor for the led. Addtional external sensors are detected automatically when present on the board.

Prepare Merkur and PI Expansion Board

• get a Merkur board and Merkur-Connect Pi-Expansionboard for a Raspberry PI (e.g. from https://www.iot-shop.at or https://electronics.semaf.at)
• Follow the tutorial for setting up of the Merkur board http://osdwiki.open-entry.com/doku.php/de:ideen:firststepsmerkurboard
• Follow the instructions for setting up the PI expansion board http://osdwiki.open-entry.com/doku.php/de:tutorials:installation_merkur_connect_pi_expansionboard_software

Install the Sample

• download the sample code from http://sourceforge.net/projects/m2mlabs/files/samples/samples.zip/download
• copy the samples/CoapProxy/dist directory to the Raspberry PI
• edit the config.json file in the CoapProxy directory in the RaspberryPi, following elements have to be set

* mainspringUrl : URL of the Mainspring server
* apikey: your Mainspring apikey
* neighboursFile : path to the index.html file where the auto-detection of resources stores the information, e.g.your home directory
* piAddress : IPV6 address of the expansion board
* sleepTime : time interval in milliseconds for pollling of CoAP resources

• run java -DcoapproxyConfFile=<path to="" config.json="" file=""> -jar <path to="" dist="" directory="">/CoapProxy.jar</path></path>
• check in Mainspring admin GUI that models and devices for the Merkur board were created. Models are only created if they are not present from a previous run of the CoapProxy. The device name of a Merkur board is derived from its IPV6 address by replacing the ":" in the address with a "."