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 Plug & Sense! Smart Parking and is the answer not in the manual?

Questions and answers

Summary of Contents for Waspmote Plug & Sense! Smart Parking

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

    Index © 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. How the node works ..........................7 5.
  • Page 3 Index 9. Callback Server ..........................24 9.1. Installation ....................................24 9.2. Deploying ....................................25 9.3. Making the server accessible from anywhere ........................ 26 9.4. Web form ...................................... 26 9.5. How to extend the remote node con guration web application ................29 10.
  • Page 4: Introduction

    Smart Parking US XKM-PARKING-V1 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

    • Keep the device in a dry place and away from any liquid which may spill. Waspmote consists of highly sensitive electronics which is accessible to the exterior, handle with great care • and avoid bangs or hard brushing against surfaces.
  • Page 6: Hardware

    Hardware 3. Hardware 3.1. Hardware description Figure : Plug & Sense! Smart Parking Power supply Built-in Lithium batteries, expected lifetime of 4-6 years* Antenna Included Detection Magnetic Mounting Dimensions 230 mm diameter, 28 mm height IP68 strictly under right closing (see section “Device Protection installation”) Operating temperature...
  • 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 AM and 12 AM (in light gray) indicates that the node is working in day mode. In this mode, the sampling of the parking slot is made more regular (1 minute) and the Keep-Alive is only 2 hours.
  • 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). It • Night Mode start hour: Night Mode duration: • Night Mode Sleep Time: Sleep time between consecutive sensor measurements (during night mode). 10 •...
  • Page 10: Transmission Modes

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

    Frames 7. Frames 7.1. Firmware version v2.x.x same for Sigfox and LoRaWAN. Bytes 0 and 1 are common for all frames. Byte 0 has the basic information of the node and frame. Name Description '0' indicates that the parking slot is empty Parking slot status '1' indicates that the slot is in occupied '0' indicates that the battery has a good level of charge...
  • Page 12: Keep-Alive Frame

    Frames 7.1.2. Keep-Alive frame This frame is used to indicate that the parking slot has not changed, but the node is still working. Byte Name Description Basic data Detailed description in section “Frame” Frame counter Detailed description in section “Frame” Timestamp (hh) Current hours Timestamp (mm)
  • Page 13: Error Frame

    Frames 7.1.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 Temperature (Celsius degrees) from the node's internal sensor.
  • Page 14: Start Frames

    Frames 7.1.5. Start frames 7.1.5.1. Start frame number 1 Byte Name Description Basic data Detailed description in section “Frame” Frame counter Detailed description in section “Frame” Temperature (Celsius degrees) from the node's internal sensor. The value Temperature of temperature is a signed integer. X axis reference MSB Reference value from the sensor associated to the X axis.
  • Page 15: Firmware Version V1.X.x

    Frames 7.2. Firmware version v1.x.x same for Sigfox and LoRaWAN. Bytes 0 and 1 are common for all frames. Byte 0 has the basic information of the node, and frame and byte 1 is a frame counter. It can be used to detect lost frames. Name Description '0' indicates that the parking slot is empty...
  • Page 16: Keep-Alive Frame

    Frames 7.2.2. Keep-Alive frame This frame is used to indicate that the parking slot has not changed, but the node is still working. Byte Name Description Basic data Detailed description in section “Frame” Frame counter Detailed description in section “Frame” Timestamp (hh) Current hours Timestamp (mm)
  • Page 17: Error Frame

    Frames 7.2.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 Temperature MSB Raw temperature from the parking internal sensor.
  • Page 18: Start Frames

    Frames 7.2.5. Start frames 7.2.5.1. Start frame number 1 Byte Name Description Basic data Detailed description in section “Frame” Frame counter Detailed description in section “Frame” Temperature MSB Raw temperature from the parking internal sensor. The value stored in these two bytes is a 16-bit value in 2’s complement form. To convert to Celsius degrees use the next formula: Temperature LSB X axis reference MSB...
  • Page 19: Smart Devices App

    Smart Devices App 8. Smart Devices App available for Smart Parking and MySignals products, but the list will be incremented shortly. 8.1. Installation First of all and before installing anything, users have to take into account the platform where the application is going to be installed.
  • Page 20 Smart Devices App Just connect the device to the computer where the Smart Devices App is installed using the USB cable provided and switch the node on. Then, refresh the “USB settings” block which is in the bottom-right corner, clicking in “refresh” button. Once done it, the port where the device has been connected must be selected.
  • Page 21: 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 •...
  • Page 22 Smart Devices App process is very simple, just mark the check of the version you want to install from the list and click on “Download checked” button. Figure : When this item is downloaded, a disk will be displayed near it downloaded, it is ready to install using the “Install Firmware”...
  • Page 23: Con Guration

    Smart Devices App 8.2.3. modify these values in order to get the wished application behavior. 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 Figure : -23-...
  • Page 24: Callback Server

    Callback Server 9. Callback Server Sigfox and LoRaWAN callback service requirements include a server with a web application up and running, this web application will receive Sigfox and LoRaWAN requests. Sigfox and LoRaWAN callback service will relay messages via POST/GET requests to your web application running in your server. of the Smart Parking nodes, and a background process to deal with the Sigfox and LoRaWAN callback services previously stored using the web form.
  • Page 25: Deploying

    Callback Server 9.2. Deploying default in Ubuntu environment. in Ubuntu environment. <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>...
  • Page 26: Making The Server Accessible From Anywhere

    Callback Server 9.3. Making the server accessible from anywhere Compulsory for Sigfox and Actility platforms. Optimal deployment includes a server name pointing to a public and static IP, using dynamic DNS could be done with services like no-ip which has a free package http://www.noip.com/. No-ip has also a client application responsible for updating any IP address changes in the background, more information in: http://www.noip.com/download with the server name and the paths:...
  • Page 27 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: Duration: Night mode duration time. • Start hour: Night Mode start hour. •...
  • Page 28 Callback Server Note: Sigfox and LoRaWAN radios unique ID must be known previously to use the web form. There are several ways those unique ID are provided. Additionally the Libelium Smart Devices App can be used to read those ID pointed in the following picture: Figure : Device IDs read from the Smart Devices App Using the Smart Java App requires physical access to the Smart Parking node, the node must be attached to the...
  • Page 29: How To Extend The Remote Node Con Guration Web Application

    Callback Server 9.5. application previously stored using the web form. The background process could be improved, or totally recoded using other programming languages, sharing with node information in a database, grouping the nodes in zones, adding user credentials, etc. For improvements on the web form, it is important to pay special attention to the endpoints described in this Figure : Backend working diagram Endpoints description: endpoint...
  • Page 30 Callback Server BAT_READING value [0-7] Text Description Number of daily battery level checking App values [0 = 1 | 1 = 2 | 2 = 3 | 3 = 4 | 4 = 5 | 5 = 6 | 6 = 7 | 7 = 8] RADIO_MODE value [0-4]...
  • Page 31 Callback Server NM_PERIOD value [0-15] Text Description Night mode duration time Night mode - Duration [0 = 0h | 1 = 1h | 2 = 2h | 3 = 3h | 4 = 4h | 5 = 5h | 6 = 6h | 7 = 7h | 8 = 8h | 9 = 9h | 10 = 10h | 11 = 11h | 12 = 12h | 13 = 13h | 14 App values = 14h | 15 = 15h]...
  • Page 32: 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 the spot).
  • Page 33: 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 34: 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 will be very limited.
  • Page 35 Device Installation Step 3: Figure : Battery connection Step 4: before this step. The node blinks the onboard red LED (1 second) and it will go to deepsleep state. In this state the node must not be reset with the magnetic switch before the node is deployed. If it is reseted, the node starts to work and will send frames, generating an unwanted consumption.
  • Page 36: How To Close The Smart Parking Enclosure To Keep The Waterproof Ip68 Features

    Device Installation 11.2. How to close the Smart Parking enclosure to keep the waterproof IP68 features In order to close the node correctly and ensure correct sealing, the following steps must be strictly followed. Step 1: Make sure that the screws have the o-rings to prevent water ingress. Figure : Screws with o-ring Step 2: Ensure that the top surface of the gasket is clean and contains no foreign objects.
  • Page 37: Installation And Boot

    Device Installation Step 4: Insert the screws and tighten them halfway Figure : Screws in their position Step 5: screws), because the o-rings could be ejected from the screws, and then the waterproof feature would NOT be valid. Besides, do not screw too hard and keep on screwing, because the screws could carve the female sockets, expanding their inner diameter;...
  • Page 38 Device Installation Step 2: Drill the holes. Warning: The drill diameter must be 10 mm maximum to prevent the anchor from rotating freely in the hole. Try to drill as vertical as possible, to enable the best enclosure installation. The length of the hole must be about 42 mm.
  • Page 39 Device Installation Step 3: The anchoring mechanism of these anchors is based on the expansion of the metal body against the base material. This expansion occurs when the expansion cylinder is propelled down, hitting on a punch with a hammer. First, insert the anchors in the holes and take them all the way down.
  • Page 40 Device Installation Once the anchor is totally inserted, make sure that it is at least 12 mm below the ground. Then take a sharp punch (few mm), put it inside the anchor and hit some very hard blows with a hammer. Figure : Hammering with a punch inside the anchor Figure : Anchor installed Warning: The anchors provided are indicated for concrete with at least 50 mm of depth, depending on the material of...
  • Page 41 Device Installation Figure : Setting anchors instructions Step 4: Place the black circle rubber on the ground. To enable the correct screwing of the screws inside the anchors, make sure that there is no dust in the inner thread of the anchor (you can use the spray duster again). Figure : Screwing the node Figure : Final section of the anchor and screw -41-...
  • Page 42 Device Installation Figure : Step 5: 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 6: When the node gets the reference calibration, it will send two frames to the cloud: Start frame 1 and Start frame 2.
  • Page 43: Con Guring The Parking Nodes In The Callback Server

    Device Installation Figure : Start frames received in the Sigfox backend 11.4. on-line form available. depending on the group that each node belong to. This can be achieved if the cloud keeps record of the groups, and which nodes are inside each group. -43-...
  • Page 44: Services

    Services 12. Services company not already implemented, we include in this section the instructions to develop that new service. 12.1. Sigfox This section explains how to route the information received from the Sigfox platform to the callback server and generate the needed response. 12.1.1.
  • Page 45 Services The next step is creating 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 for the new Device Type, usually the group created previously.
  • Page 46 Services Figure : Callback form your server. Some extra variables have been added (to send to the service as much information as possible) following the information displayed in the form. http://my_server.com/services/sigfox/?id={device}&time={time}&duplicate={duplicate}&snr= {snr}&station={station}&data={data}&avgSnr={avgSnr}&lat={lat}&lng={lng}&rssi={rssi}&seq- Number={seqNumber}&ack=true After the callback form is saved, the list of all available callbacks will be shown. Enable this entry with a downlink, the service running in your server will receive the information: 1.
  • Page 47 Services Finally it is time for creating the device node itself, click on “Device” option in the top menu, wait for the next window to be loaded, click on “New” button. Figure : Device creation As it happened with the Device Type, the parent group of the device must be selected. Fill the following information in the new device form: Figure : Device form •...
  • Page 48: Server Con Guration

    Services 12.1.2. with the node. [sigfox] log_level: This level is the minimum level to save logs in the system. Select among these levels: • OFF: This option deactivate the log. ERROR : It only reports ERROR messages. INFO: It reports ERROR + INFO messages. DEBUG: it reports ERROR + INFO + DEBUG messages.
  • Page 49: Loriot

    Services 12.2. Loriot This section explains how to route the information received from the Loriot platform to the callback server and generate a response if it is needed. 12.2.1. Log in and create a new application in the Loriot dashboard. Figure : Creating an application In this application all devices have to be added clicking on “Devices”...
  • Page 50: Server Con Guration

    Services Click on “Edit output” to display all the information available about the selected output option.Click on “Change” button in the detailed window to change the data output, select one of the multiple choices from the list. Figure : Selecting the output application “Websocket”...
  • Page 51: Start The Web-Socket Connection

    Services Figure : Output setup 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.
  • Page 52: Actility

    Services 12.4. Actility This section explains how to route the information received from the Actility platform to the callback server and generate a response if it is needed. 12.4.1. Figure : Figure : -52-...
  • Page 53 Services A name must be typed in the new window displayed. Clicking on Create button to continue the process. Figure : In the new window, mark the check “Is default” and click the “Add button” in the Add a route section. Figure : A new section “Route”...
  • Page 54 Services After the default route has been deleted, create the destination URL. 1. Hitting on “Add” button a new pop up window will be displayed. • • • • Figure : Route destination created. Right-click on “Devices” option in the left menu, and then hit on “Create device”. Figure : Create a new device -54-...
  • Page 55: Server Con Guration

    Services click on Network section in the left menu. Figure : Steps to follow when the device is created click on the “Save” button. Figure : Select the AS Routing created 12.4.2. with the node. [actility] log_level: This level is the minimum level to save logs in the system. Users can select one among these levels: •...
  • Page 56: Saving The Information Received

    Services 12.5. Saving the information received This section explains how to get the information sent by the Smart Parking nodes to the callback server. Sigfox: your_callback_server_path/services/sigfox/index.php • Loriot: your_callback_server_path/services/loriot/websocket_response.php • Actility: your_callback_server_path/services/actility/index.php • your_callback_server_path has to be replaced with the path where the callback server was previously installed. //To-Do: get the information received: $frame->get_data();...
  • Page 57 Services Methods Name Description Class constructor. void __construct (String device_ID) Device ID has to be sent as a parameter. It will be saved in the attribute device_id Reset all attributes. void reset (void) Decode the information received from the node and store it in the attribute info.
  • Page 58 Services Frame type 1 = Keep-Alive frame Name Description sensor_msb Times that the sensor is used in the las 24 hours. sensor_lsb sigfox_msb Times that the Sigfox radio is used in the last 24 hours. sigfox_lsb lorawan_msb Times that the LoRaWAN radio is used in the last 24 hours. lorawan_lsb resets_today Number of resets generated in the last 24 hours.
  • Page 59 Services x_msb Reference value from the sensor associated to the X axis. x_lsb y_msb Reference value from the sensor associated to the Y axis. y_lsb z_msb Reference value from the sensor associated to the Z axis. z_lsb Battery voltage in millivolts. To convert to millivolts, use the next formula: battery_level Frame type 4 = Start frame number 1 Name...
  • Page 60 Services Frame type 5 = Start frame number 2 Name Firmware version. CODE_ID Firmware version. NM_START Beginning hour of the night mode. Duration in hours of the night mode. NM_PERIOD Sleep time between consecutive sensor measurements (during night NM_SLEEP_TIME mode). Elapsed time since last transmission to trigger a Keep-Alive frame NM_KEEP_ALIVE (during night mode).
  • Page 61 Services Byte 0 has always the same format in all frames and it is compulsory to start with it in order to know which frame type is. byte 0 byte value The information obtained in this step is: Parking slot (bit 7) 0 ® free •...
  • Page 62: Troubleshooting

    Troubleshooting 13. Troubleshooting 13.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. It is this issue. Firstly, it is necessary to open the Device Manager in order to see what device is not being detected. To open this window depends on the Windows version you have, but usually typing “Device Manager”...
  • Page 63 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 clicking on “Install this driver software anyway”. Figure : Security warning After a while, the driver is installed.
  • Page 64 Troubleshooting Device Manager list to verify the status. If the warning remains near the USB serial port, users have to repeat the “Update driver software” process again. Figure : USB devices to verify Figure : USB devices with all drivers installed Now, the Smart Device App is ready to detect the ports and make the operation you want to do.
  • Page 65: How To Know The Port Where The Device Is Plugged In

    Troubleshooting 13.2. How to know the port where the device is plugged in Users have to select in the Smart Devices App the port assigned to the Smart Parking node in the computers to make any operation with the Smart Parking node. The assigned port depends on the USB devices that the users have plugged in their computers.
  • Page 66: Certi Cations

    This document applies to the following Smart Parking model, approved for FCC: Model FCC ID Smart Parking US XKM-PARKING-V1 14.1. could void the user’s authority to operate the equipment. Interference statement This device complies with Part 15 of the FCC Rules license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.
  • Page 67: 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