Libelium Waspmote Plug & Sense! Smart Parking Technical Manual

Hide thumbs Also See for Waspmote Plug & Sense! Smart Parking:

Advertisement

Quick Links

Plug & Sense! Smart Parking
Technical Guide
wasp
mote

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Waspmote Plug & Sense! Smart Parking and is the answer not in the manual?

Questions and answers

Summary of Contents for Libelium Waspmote Plug & Sense! Smart Parking

  • Page 1 Plug & Sense! Smart Parking Technical Guide wasp mote...
  • Page 2: Table Of Contents

    Index Document version: v7.0 - 10/2016 © Libelium Comunicaciones Distribuidas S.L. INDEX 1. Introduction ............................4 2. General ..............................5 2.1. General and safety information ..............................5 2.2. Conditions of use ..................................5 3. Hardware .............................. 6 3.1. Hardware description .................................6 3.2. Power consumption ..................................6 4.
  • Page 3 Index 10. Developing the network ......................... 27 10.1. Application considerations ..............................27 10.1.1. Deployment of the motes ............................27 10.1.2. Interference of other vehicles ..........................28 11. Device Installation ........................... 29 11.1. Assembly and set up ................................29 11.2. Installation and boot ................................31 11.3.
  • Page 4: Introduction

    Introduction 1. Introduction The new version of Waspmote Plug & Sense! Smart Parking, the solution for Smart Cities that allows citizens to detect available parking spots. The new device is easier and cheaper to deploy as it is mounted on the road surface. Unlike most market versions, it does not need to dig a hole in the ground for installation, reducing installation time from 30 to 5 minutes and allowing to be replaced by another unit in case of maintenance in just 10 minutes.
  • Page 5: General

    Check the product specifications section for the maximum allowed power voltage and amperage range and consequently always use a current transformer and a battery which works within that range. Libelium is only responsible for the correct operation of the device with the batteries, power supplies and chargers which it supplies.
  • Page 6: Hardware

    Hardware 3. Hardware 3.1. Hardware description Figure : Plug & Sense! Smart Parking Sigfox radio for Europe: 868.0 to 869.7 MHz LoRaWAN radio for Europe: 863.0 to 870.0 MHz Operating frequency Sigfox radio for USA: 902.0 to 928.0 MHz LoRaWAN radio for USA: 902.0 to 928.0 MHz Power supply Built-in Lithium batteries, expected lifetime of 4-6 years * Antenna...
  • Page 7: How The Node Works

    How the node works 4. How the node works Figure : Basic working loop diagram As the diagram indicate, the basic loop of the node consists in read the sensor and send a frame when the parking slot change it status. Then, it sleeps a desired time and starts the loop again. Some events can forced the node to send a frame to the cloud.
  • Page 8: Sleep Modes

    Sleep modes 5. Sleep modes Plug & Sense! Smart Parking has 2 sleep modes: day mode and night mode. The second one has been developed to use when the parking slot is expected to have fewer changes (i.e. at night). Each mode has its own configuration parameters. The figure below shows an example for the node transmissions in a day.
  • Page 9: Night Mode

    Sleep modes 5.2. Night mode This mode has been developed to use when the parking slot is expected to have fewer changes (i.e. at night) and it has 4 configurable parameters: Night Mode start hour: Beginning hour of the night mode. 22 hours option is configured by default. •...
  • Page 10: Transmission Modes

    Transmission modes 6. Transmission modes Plug & Sense! Smart Parking has 5 transmission modes allowing to the user to choose between Sigfox, LoRaWAN y their combinations: • Sigfox. This mode only use the Sigfox radio to send the data collected by the node. This mode is selected by default. LoRaWAN.
  • Page 11: Frames

    Frames 7. Frames Plug & Sense! Smart Parking node can send 6 defined frames. All frames are 12 bytes length and they are the same for Sigfox and LoRaWAN. Bytes 0 and 1 are common for all frames. Byte 0 has the basic data from the node and frame and byte 1 its a frame counter.
  • Page 12: Info Frame

    Frames 7.1. Info frame It is the most common frame sent by the node. The node will send this kind of frame each time it detects that the parking slot changed from empty to occupied or vice-versa. The other bytes are used to give additional data to the user. Byte Name Description...
  • Page 13: Daily Update Frame

    Frames 7.3. Daily update frame This frame is sent daily at 1 AM. It contains a little summary. This frame can be deactivated using the Plug & Sense! Smart Parking USB Programmer or via radio, with the response given by the Remote Manager, hosted in the cloud. Byte Name Description...
  • Page 14: Error Frame

    Frames 7.4. Error frame In some cases the node could send a frame if some internal components or processes fail. Byte Name Description Basic data Detailed description in section “Frame” Frame counter Detailed description in section “Frame” Error data Detailed description below Raw temperature from the node’s internal sensor.
  • Page 15: Start Frames

    Frames Name Description Reserved Reserved bits. Do not consider. Set to '1' when an error related with the Sigfox radio is detected. Clear Error Sigfox when no issues detected. Set to '1' when an error related with the LoRaWAN radio is detected. Error LoRaWAN Clear when no issues detected.
  • Page 16: Start Frame Number 2

    Frames 7.5.2. Start frame number 2 Byte Name Description Basic data Detailed description in section “Frame” Frame counter Detailed description in section “Frame” CODE_ID Firmware version NM_START Beginning hour of the night mode NM_PERIOD Duration in hours of the night mode Sleep time between consecutive sensor measurements (during night NM_SLEEP_TIME mode)
  • Page 17: Smart Devices App

    First of all and before installing anything, users have to take into account the platform where the application is going to be installed. To install the Libelium Smart Devices App, it is compulsory to have installed the JDK 1.8. If it is not installed in the computer, you can follow the steps and download it from this website: https://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html...
  • Page 18 Smart Devices App Users can read and write all configuration parameters of their devices in this section. The process is quite simple. Just connect the device to the computer where the Smart Devices App is installed using the USB cable provided. Figure : USB settings Then, refresh the “USB settings”...
  • Page 19: Firmware Upgrade

    Smart Devices App Sigfox ID: Sigfox ID that will be loaded from the device. LoRaWAN EUI: LoRaWAN EUI that will be loaded from the device. • USB SETTINGS • USB Port: In this list will be displayed all available USB ports to work out with the device. If you plug your device and the port is not listed, you have click on “Refresh”...
  • Page 20 Smart Devices App The list with all available firmware is loaded when the program starts, but users can update it on demand, clicking on “Search new firmware updates” button. Before installing the firmware, it is necessary to download it. This process is very simple, just mark the check of the version you want to install from the list IMAGEN app_check.png and click on “Download checked”...
  • Page 21: Configuration

    In this case, there is only one parameter available, the API key to connect to Libelium Cloud. This value is provided by Libelium and it is very important to control the access and get some results needed in the programmer tab. If users don’t fill this field, the software don’t work.
  • Page 22: Callback Server

    URL: https://my_server.com/path/zip/extracted No need of DB is needed for this simple implementation provided by Libelium but it is very easy to extend its functionality implementing connections to MySQL, PostgreSQL or any other DB storage if required. NOTE: Customers have to ask for this source code to Libelium Sales Department after buying the nodes.
  • Page 23: Making The Server Accessible From Anywhere

    Callback Server <VirtualHost *:80> ServerAdmin webmaster@localhost ServerName my_server.com ServerAlias my_server.com DirectoryIndex index.html index.php DocumentRoot /path/zip/extracted ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined <Directory /path/zip/extracted> Options Indexes FollowSymLinks AllowOverride All Require all granted </Directory> </VirtualHost> Check the right owner/group and permissions of all the files extracted in order to be accessible. Usually using www-data group is default in Ubuntu environment.
  • Page 24 USB Programmer. Figure : Libelium Callback Configurator screen-shot Users can create, update and delete the same configuration for several devices. To do that, just type the ID separated by semicolons (;) like this: 00145F;001460;001461 and the rest configuration parameters will be saved with each device ID.
  • Page 25 Callback Server TIME SETTINGS Sleep time: Sleep time between consecutive sensor measurements. • Keep-Alive: Elapsed time since last transmission to send a Keep-Alive frame. • NIGHT MODE Enabled: Button to activate/deactivate this option. If it is not active, the following fields will not be effective. •...
  • Page 26 ID exists, it will be updated like if you select the device from the list. Getting the IDs from the node is quite easy from the Libelium Smart Devices App. The IDs to be created in your web server are...
  • Page 27: Developing The Network

    Developing the network 10. Developing the network 10.1. Application considerations 10.1.1. Deployment of the motes The optimum deployment point will be the one where the probability of detection is maximum, which means minimizing the probabilities of false detection (caused by other vehicles or objects near the lot under control) and false rejection (owed to a not high enough variation in the magnetic field above the mote with a vehicle parked in the spot).
  • Page 28: Interference Of Other Vehicles

    Developing the network Figure : Diagram of the deployment points of the motes for perpendicular parking lots Figure : Placement options of the motes for parallel parking lots Figure : Placement options of the motes for perpendicular parking lots Other consideration to be taken into account in mote deployment is the communication between this one and the gateway or router that will receive the data and process or redirect it.
  • Page 29: Device Installation

    Device Installation 11. Device Installation Important: Before deploying the nodes on the street, make sure that enough tests have been performed in order to achieve a 100% functional network and that all the necessary information related to the mote, such as identification numbers of the radios, has been compiled and stored, since once the mote is installed, the access will be very limited.
  • Page 30 Device Installation Step 3: Now the node is configured. Turn off the node . Figure : Battery connection Step 4: Before closing the enclosure, the node must be powered on. It’s mandatory that the node is powered off before this step.
  • Page 31: Installation And Boot

    Device Installation 11.2. Installation and boot Step 1: Indicate the 4 holes in the asphalt. Figure : Indicating the holes for the node Step 2: Drill the holes. Figure : Drilling the holes -31- v7.0...
  • Page 32 Device Installation Step 3: Install the node in its final position and screw with the 4 special screws. Anti-vandalic screws are recommended to avoid problems: anyone could unscrew the node from the ground. Figure : Screwing the node Figure : The node finally screwed -32- v7.0...
  • Page 33: Configuring The Parking Nodes In The Callback Server

    Device Installation Step 4: Use the magnet to reset the node. Once the node has been reset, it will start to configure the radios and get a calibration of the parking slot. In this stage the parking slot must be empty, so the node learns when the slot is not occupied. Figure : Using the magnet to reset the node Step 5: When the node gets the reference calibration, it will send two frames to the cloud: Start frame 1 and Start frame 2.
  • Page 34: Sigfox

    Sigfox 12. Sigfox This section explains how to route the information received from the Sigfox platform to the back-end web server application installed,deployed and configured in section 3 generating a response when needed. 12.1. Device configuration In first place, configuring a new Group in the Sigfox back-end is a must: •...
  • Page 35 Sigfox Is time now to create the Device Type in the back-end, clicking on “Device Type” in the top menu and then on “New” button. Figure : Device type creation schema A new pop-up window will be shown to select the group where you want to create the Device Type, usually the group created previously.
  • Page 36 Sigfox A new form that must be completed will be displayed as you see in the next image. Figure : Callback form “Url pattern” field should be filled with the URL to the back-end web server application deployed in your server following steps described in section 3, that provides access to the Sigfox service.Some extra variables has been added following the information displayed in the form, in order to send to the service as much information as possible.
  • Page 37 Sigfox Finally it is time for creating the device, clicking on “Device” option in the top menu and, once loaded the next window, on “New” button. Figure : Device creation As it happened with the Device Type, we have to select the group first after continue with the process. Then, in the new device form, we have to fill the following information: Figure : Device form Identifier: Device ID in hexadecimal format, given by the manufacturer.
  • Page 38: Server Configuration

    Sigfox 12.2. Server configuration Configuration parameters to be modified in order to be able to communicate to the node and run the whole system. file, located in folder, has to be updated with the following information in the section. services.ini data sigfox [sigfox]...
  • Page 39: Loriot

    Loriot 13. Loriot This section explains how to route the information received from the Loriot platform to the back-end web server application installed,deployed and configured in section 3, generating a response when needed. 13.1. Device configuration Create a new application in the dashboard after log in the Loriot dashboard. Figure : Create an application In this application all devices have to be added clicking on “Devices”...
  • Page 40: Server Configuration

    Loriot Clicking on “Edit output”, all information available about the selected output option will be displayed. To change the data output click on “Change” button in the detailed window and select one of the multiple choices from the emergent list. Figure : Selecting the output application For this project, we have chosen “Websocket”...
  • Page 41: Start The Web-Socket Connection

    Loriot Clicking in “Authentication token” link, a new window will be shown with the tokens generated in the Loriot application. To create a new one, just click on “Generate another authentication token” button, and a new record will be created in the table. Finally, copy the full URL hitting on “Show full URL”...
  • Page 42: Actility

    Actility 14. Actility This section explains how to route the information received from the Actility platform to the customer server and generate a response if it is needed. 14.1. Device configuration Firstly, it is necessary to configure a new AS routing profile in the Device Manager clicking on “AS routing profiles” on the left sidebar menu.
  • Page 43 Actility A name must be typed in the new window displayed. Clicking on Create button to continue the process. Figure : AS Routing profile name In the new window, it is necessary to mark the check “Is default” and click the “Add button” in the Add a route section. Figure : AS Routing profile route A new section “Route”...
  • Page 44 You have to right-click on “Devices” option in the left menu, and then hit on “Create device”. It is necessary to fill in all compulsory fields in the form displayed in the new window, according to the values in the Libelium Smart Devices App.
  • Page 45: Server Configuration

    Actility On the other hand, if the device is created, changing the network routing to the AS Routing profile is quite easy. First, select a device from the list and hit on “Edit” button. Then click on Network section in the left menu. Figure : Steps to follow when the device is created In the “Network/cloud routing”...
  • Page 46: Troubleshooting

    Troubleshooting 15. Troubleshooting 15.1. Windows does not recognize USB ports Sometimes it is possible that your computer does not recognize the USB port where the board is plugged. The reason could be that the driver for the device is missing in your Operating System. Proceed as described to fix this issue. Open the Device Manager in order to see what device is not being detected.
  • Page 47 Troubleshooting Then, the driver must be searched in the computer, in particular the same path where the Smart Devices App has been installed. Figure : Search the driver in the computer Once validated the path, the next pop-up will be displayed, noticing the driver is not verified. Users have to confirm clicking on “Install this driver software anyway”.
  • Page 48 Troubleshooting The process is not finished. The first driver installed is “USB Serial Converter”,check the Device Manager list to verify the status. If the warning remains near the USB serial port, the “Update driver software”process must be repeated again. Figure : USB devices to verify When the process is finished, check that both drivers have been installed.
  • Page 49: Certifications

    Certifications 16. Certifications Libelium offers 2 types of IoT sensor platforms, Waspmote OEM and Plug & Sense!: • Waspmote OEM is intended to be used for research purposes or as part of a major product so it needs final certification on the client side.
  • Page 50: Disposal And Recycling

    Disposal and recycling 17. Disposal and recycling In this section, the term “Waspmote” encompasses both the Waspmote device itself as well as it enclosure. When Waspmote reaches the end of its useful life, it must be taken to an electronic equipment recycling point. The equipment must be disposed of in a selective waste collection system, and not that for urban solid residue.

Table of Contents