1. Manuals
  2. Brands
  3. Libelium Manuals
  4. Automobile Electronics
  5. Waspmote Smart Parking v2
  6. Technical manual

Libelium Waspmote Smart Parking v2 Technical Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Waspmote Smart Parking v2 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Libelium Waspmote Smart Parking v2

  • Page 2: Table Of Contents

    4.1. Introduction to the Libelium Services Cloud Manager - SCM ........
  • Page 3 6.5.1. Libelium’s Custom App ................

  • Page 4: Index

    ................8. Libelium Smart Parking Cloud Service .
  • Page 5 INDEX 10. Certifications ..................... . . 10.1.
  • Page 6 Introduction 1. Introduction The Smart Parking v2 solution developed by Libelium allows citizens to detect available parking slots. Figure : Smart Parking node developed by Libelium The node applies intelligent algorithms to detect changes in the state of the parking slot. Then data is transmitted with the LoRaWAN radio to the final server.

  • Page 7: Introduction

    Introduction Radar Infra-red Magnetometer Reliability against nearby vehicle movement Reliability against nearby parked vehicles Reliability against electromagnetic interferences Reliability in any lighting scenario Stability during long-duration vehicle stays Do not need an aperture in enclosure Immunity against dirt or dust on enclosure The node provides OTA-S (Over-The-Air Setup).

  • Page 8: Network Architecture

    The network architecture of Smart Parking is based on the next elements: Smart Parking node ‚ LoRaWAN base station ‚ LoRaWAN Network Server ‚ Libelium Smart Parking Cloud Service or Customer Server ‚ Figure : Smart Parking network architecture - 7 - v7.5...

  • Page 9: Smart Parking Node

    It receives data and forwards it to the LoRaWAN Network Server. Libelium distributes base stations for LoRaWAN networks. All of them have LoRaWAN connection; some feature Ethernet, WiFi or 4G connectivity too. Some base stations are ready to work outdoors (IP67 grade). Some of them come pre-configured for certain LoRaWAN network servers (see next section).

  • Page 10: Libelium Smart Parking Cloud Service And Customer Server

    Libelium Smart Parking Cloud Service or to the Customer Server. 2.4. Libelium Smart Parking Cloud Service and Customer Server The LoRaWAN Network Server connects to the final server, which can be the Libelium Smart Parking Cloud Service or the Customer Server. The LoRaWAN network servers currently supported are: Loriot ‚...
  • Page 11 Network architecture Figure : Libelium Smart Parking Cloud Service scenario Figure : Customer Server scenario - 10 - v7.5...

  • Page 12: Smart Parking Node

    Smart Parking node 3. Smart Parking node 3.1. Hardware description The Smart Parking node is based on 2 different pieces: the base and the external enclosure. The base of the Smart Parking node includes the PCB, the battery, the antenna and the internal enclosure piece. Figure : Base of a Smart Parking node The base is screwed to the external enclosure piece: Figure : External enclosure...
  • Page 13 Smart Parking node The next table shows the basic Smart Parking node characteristics. Enclosure dimensions 37.25 mm x 200 mm Power supply Built-in lithium-thionyl chloride (Li-SOCl2) batteries; expected lifetime of 4-10 years* Configurable sleep time Min: 20 s / max: 10 min Radio protocol LoRaWAN module Dual detection...

  • Page 14: Node Versions

    Smart Parking node 3.1.1. Node versions Libelium provides the next versions of Smart Parking: Reference Version Operating frequency SP-EU Smart Parking EU 863.0 to 870.0 MHz (LoRaWAN EU863-870) SP-US Smart Parking US 902.0 to 928.0 MHz (LoRaWAN US902-928) SP-APLA-AU Smart Parking APAC / LATAM / AU / AU915 915.2 to 927.8 MHz (LoRaWAN AU915-928)

  • Page 15: Identification Label

    Smart Parking node Application Key: Needed for OTAA. The 16-byte key. Needed for opening an OTAA session and exchange ‚ encryption keys. Data-rate: Defines the transmission rate (bits per second). Each data-rate settings combines different ‚ Spreading Factor (SF) and bandwidth (BW). By default, all LoRaWAN regions use the same data-rate (DR 0). However, depending on the region, that means different SF and BW: LoRaWAN EU863-870 version: SF12 / 125 kHz LoRaWAN IN865-867 version: SF12 / 125 kHz...

  • Page 16: Smart Parking Eu

    Smart Parking node 3.2.1. Smart Parking EU Power consumption Time consumption Node setup 22.9 mA 59 s Measure cycle 26 mA 340 ms Measure and send cycle 17 mA Sleep cycle 5.5 uA Depends on sleep time settings LoRaWAN EU is set to the default SF12 settings (worst case). The send process may be lower power if the node is close to the base station. 3.2.2.

  • Page 17: Reset Button

    3.5. Node setup 3.5.1. "Ready to install" state Important: Libelium provides the nodes "ready to install" so the user only needs to install the nodes and follow the “"Magnet start-up" process”. The Smart Parking node has a power-on process in order to put the device into a "ready-to-install" state: Step 1: The switches are set to "App"...

  • Page 18: How To Close The Smart Parking Node

    Smart Parking node Figure : The red LED blinks once to indicate ready-to-install state You can see how the previous steps are performed in this video: Ready to install process 3.5.2. How to close the Smart Parking node After following the previous steps, the device can be closed. In order to close the node correctly and ensure correct sealing, the following steps must be strictly followed.

  • Page 19: Magnet Start-Up" Process

    Libelium manufactures and provides all nodes configured after following all explained steps, so the node is "ready to install". By factory default, all nodes are configured with their unique LoRaWAN EUI and random private keys.

  • Page 20: How The Node Works

    Smart Parking node In the next video-clip you can see how the "magnet start-up" is performed: Magnet start-up After finishing the "magnet start-up", the node starts working normally for the rest of the time. No more three-time "magnet resets" are needed in order to reset the device properly. So if a 4th magnet reset or software reset is applied, the device will reset and continue working normally again.

  • Page 21: Frame Header

    Smart Parking node network latency. This implies that the 1st request attempt usually fails. In that case, a 2nd attempt is sent in order to retrieve the lost downlink packet. For this reason, you might see that a couple of "Start Frame 1" or "RTC update request"...
  • Page 22 The Customer Server provides the needed source code to parse this data into a more comprehensive structure. The Libelium Cloud Bridge also provides the needed tools to transmit the parsed data to a 3rd party IoT cloud. For more information, please refer to the “Customer...

  • Page 23: Node Program Flowchart

    Smart Parking node 3.6.4. Node program flowchart Figure : Smart Parking node program flowchart - 22 - v7.5...

  • Page 24: Node Parameters

    Smart Parking node 3.7. Node parameters 3.7.1. Parameters description and ranges The Smart Parking node has different parameters that change the timing and detection performance of the node. The next table shows the node parameters: Parameter Range Description Sleep time 1-10 min or 20-59 s Minutes or seconds elapsed between each measurement cycle Hours elapsed since last uplink message which triggers a new...

  • Page 25: Understanding Info And Keep-Alive Frames

    Smart Parking node 3.7.2. Understanding Info and Keep-alive frames In the regular working mode (day-mode), "Sleep" and "Keep-alive" parameters are used. So the node normally sleeps for a specific "Sleep" time then wakes-up, measures and applies the algorithm detection in order to detect changes in the parking slot.

  • Page 26: Understanding Rtc Synchronization

    Smart Parking node Night-mode duration: 10 hours (Night-mode goes from 9 PM to 7 AM) Night-mode sleep time: 10 minutes In the example, from 9 PM to 7 AM, the node will waste less battery because measurements are done every 10 minutes instead every minute.

  • Page 27: Understanding Uplink Frames Format (Real Example)

    Smart Parking node Figure : Example of RTC sync Note: The RTC sync is important for Night-mode only where it mandatory to operate with a correct timestamp in order to enter and exit from night-mode to day-mode and viceversa. 3.7.5. Understanding uplink frames format (real example) The next table shows all frames sent by a single node since it was started.

  • Page 28: Factory Default Values

    1 (Keep-alive) 04/16/19 22:32 012c0011111f00000000c8 1 (Keep-alive) 04/17/19 00:02 012d0010120100000000c7 1 (Keep-alive) 3.7.6. Factory default values Libelium provides all Smart Parking nodes with factory default parameters. Parameter Default value Sleep time 1 min Keep-alive time 2 hour Night-mode 0 (disabled)

  • Page 29: Configure New Parameter Values

    The 1st one is a desktop Java application which implies opening the node enclosure and plug a micro-USB cable to the node. The 2nd one is a form allocated in the Libelium Smart Parking Cloud Service or in the Customer Server, which permits to remotely change some of the node parameters.

  • Page 30: Libelium Cloud Management

    Libelium Cloud management 4. Libelium Cloud management 4.1. Introduction to the Libelium Services Cloud Manager - According to the Smart Parking network architecture, users can select between 2 ways of working with the Smart Parking nodes: one using the Customer Server, and the other using the Smart Parking Cloud Service. Regardless of the solution chosen, users will always need to operate with the Services Cloud Manager (SCM), which is the basis of the Libelium Cloud.

  • Page 31: Scm Account

    This is the 1st step users must follow. Anyone can create a new account in the SCM for free. This account will allow you to manage your Libelium devices and also all your licenses and services. You can access the SCM at https://cloud.libelium.com.

  • Page 32: Signing In

    Libelium Cloud management Figure : Create account form 4.2.2. Signing in To sign in the SCM, go here and click on the “Sign In” button. Figure : "Sign-in" button Complete the information in the form. The e-mail and password used when creating the account will be required: E-mail address: E-mail address used for registration ‚...

  • Page 33: Smart Parking Nodes Registration

    Libelium Cloud management Figure : Sign-in form The Terms & Conditions accepted when creating the account apply for any time you sign in the SCM. If you do not have an account yet, follow the steps described on the section “Create an account” to obtain valid credentials. If you already created an account and need a password reminder, you can click on “Forgot password?”.

  • Page 34: Editing Smart Parking Nodes

    Libelium Cloud management Figure : Activation codes e-mail By clicking on these links you will be able to complete the registration process by following the wizard: Figure : Step1. Enter device activation code Figure : Step2. Confirm activation 4.4. Editing Smart Parking nodes You can change the "name", "project", "description"...

  • Page 35: Export Csv File With Nodes Credentials

    App", then the exported credentials will not be same. In order to export the file, you must go to https://cloud.libelium.com, log in and then access "My Devices". On the website you will identify the "Smart Parking actions" button which permits to download the nodes credentials by clicking on the "Download nodes keys"...
  • Page 36 Libelium Cloud management <DevEUI_1>,<Serial>,<AppEUI_1>,<AppKey_1> <DevEUI_2>,<Serial>,<AppEUI_2>,<AppKey_2> <DevEUI_3>,<Serial>,<AppEUI_3>,<AppKey_3> <DevEUI_N>,<Serial>,<AppEUI_N>,<AppKey_N> - 35 - v7.5...

  • Page 37: Smart Devices App

    Libelium Smart Devices App is an software tool developed by Libelium that allows users install new firmware versions and program the configuration of the new Libelium devices in a few clicks. At the moment it is only available for Smart Parking and MySignals products, but the list will be incremented shortly.

  • Page 38: Start Smart Devices App On Windows

    Smart Devices App Windows systems It is important to install STM32CubeProgrammer as the software contains the drivers needed to set the USB ports in DFU mode, if you want to know more about how to install this software and know about how to set the USB in DFU mode, please see the official guide from STM32CubeProgrammer: Link to ST documentation.

  • Page 39: Start Smart Devices App On Gnu/Linux

    Smart Devices App 5.1.2. Start Smart Devices App on GNU/Linux Open a new terminal window and navigate to the folder containing the Smart Devices App application, then type: sudo ./SmartDevicesApp.sh 5.1.3. Start Smart Devices App on MacOSX Open a new terminal window and navigate to the folder containing the Smart Devices App application, then type: sudo ./SmartDevicesApp.sh 5.2.

  • Page 40: How To Plug The Smart Parking Node

    In the last tab, called Configuration, 2 parameters are available: “Username” and “Password”. These are the same credentials needed for the Libelium Cloud (SCM, https://cloud.libelium.com/login). Filling these fields is mandatory before start using the Smart Devices App with the Smart Parking node. Please remember to click the “Save”...

  • Page 41: Programmer (Change Node Parameters)

    Smart Devices App 5.3.3. Programmer (change node parameters) Figure : Smart Parking v2 Programmer section Users can read and write all node parameters 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 and switch on the node in “Boot”...

  • Page 42: Firmware Upgrade

    Smart Devices App Figure : “Load configuration from node” & “Send configuration to node” buttons Smart Parking v2 shares most of the configuration fields with Smart Parking v1 . However, it is important to know the purpose for each field on the Smart Parking v2 configuration. To know more about each field and how they work, please refer to the chapter “Smart Parking node”.
  • Page 43 Smart Devices App To summarize, the steps are: 1. Click the “Search new firmware updates” button to load new firmware updates 2. Check one or more firmwares to download from the firmware list on the left side 3. Click on “Download checked” to download the selected firmwares Figure : Download new firmware versions Now the firmware files are downloaded.

  • Page 44: Factory Reset

    Pressing the “Factory Reset” button will display a file explorer window to select the configuration file provided by Libelium. Once you selected this file, a message will show up asking if you want to start the process. If the “Yes”...

  • Page 45: Lorawan Network Server Setup

    Remember that any LoRaWAN network needs a Network Server, so you have to choose one of the options above. Not only Libelium’s Smart Parking nodes need a Network Server: any LoRaWAN device (by Libelium or other company) needs a Network Server, it’s just one piece of the LoRaWAN architecture.

  • Page 46: Create A New Loriot Application

    LoRaWAN Network Server setup Figure : Loriot login web page 6.1.2. Create a new Loriot application Once you selected the server location, a new prompt will be displayed asking your credentials. After logging in, users have to create a new application in the Loriot dashboard. To do this it is necessary to click on "Applications" in the left side bar and then in "New Application"...

  • Page 47: Manage Loriot Output Data

    LoRaWAN Network Server setup New application name: Name to identify the application. ‚ Output format: "Websocket" is selected by default and it is not possible to change it in this form. How to ‚ change it will be explained in the following step. Device capacity: Maximum number of devices to be registered in this application.

  • Page 48: How To Delete Unused Loriot Applications

    LoRaWAN Network Server setup Figure : Create a new application output Select "HTTP Push" from the list and fill the form displayed on the right side. In the "Target URL for POSTs" field, write the URL where Loriot must send data to (i.e. http://my_server.com/services/actility/). Besides, users can add an authorization header in "Custom Authorization header value"...

  • Page 49: How To Create A Single Device Manually

    LoRaWAN Network Server setup the desired ellipsis button of the application "..." and select "Delete" option. A pop-up window will ask you to confirm the operation. Figure : Delete unused application outputs 6.1.5. How to create a single device manually Click on "Devices"...

  • Page 50: Nodes Batch Provisioning In Loriot

    It asks for a CSV file which must be exported from the SCM. Please refer to “Libelium Cloud management” section for further information on how to export this CSV file which includes all nodes OTAA credentials needed for direct batch import.
  • Page 51 LoRaWAN Network Server setup Figure : Loriot bulk import The CSV file for ’N’ devices must respect the next format: <DevEUI_1>,<AppEUI_1>,<AppKey_1>,<Serial_1> <DevEUI_2>,<AppEUI_2>,<AppKey_2>,<Serial_2> <DevEUI_3>,<AppEUI_3>,<AppKey_3>,<Serial_3> <DevEUI_N>,<AppEUI_N>,<AppKey_N>,<Serial_N> - 50 - v7.5...

  • Page 52: Actility

    LoRaWAN Network Server setup 6.2. Actility This section explains how to route information on Actility to the Customer server or to the Smart Parking Cloud Service, using the HTTPS protocol. Firstly, you must access into the Actility’s ThingPark portal and log in. IN the main portal, you must go to "ThingPark Application"...
  • Page 53 LoRaWAN Network Server setup Figure : Application servers menu In "Name" field define your Application server name. In "Type" field, you must select "HTTP Application Server". Finally, click on the "Create" button to continue: Figure : Application server name A new window appears, where the name is copied from the previous pop-up. In the "Content Type" field you must select "JSON".

  • Page 54: How To Create A New As Routing Profile

    LoRaWAN Network Server setup Figure : Route form A new pop-up appears. In the "Destination" field, you must enter the URL of the server where the data is going to be sent. Click on the "Add" button to save the information: Figure : Destination form Navigate back to the Application server form, click on "Save"...
  • Page 55 LoRaWAN Network Server setup Figure : AS Routing profiles In the "Name" field write the name of the AS routing profile. In the "Type" field, select LoRaWAN. Then click on the "Create" button to continue the process: Figure : AS Routing profile name In the new window, you can read the "AS routing profile ID"...

  • Page 56: How To Create New Devices Manually

    LoRaWAN Network Server setup Figure : Add the created Application server as "destination" for the routing profile Navigate back to the AS routing profile form, click on "Save" in order to create it. This process should be completed just once. From this moment, customers can add devices to the service. 6.2.3.

  • Page 57: Nodes Batch Provisioning In Actility

    LoRaWAN Network Server setup AppKey: 16-byte Application Key (mandatory for OTAA). ‚ Network parameters Connectivity plan: Select a Connectivity plan on the drop-down menu. ‚ DevAddr: Select "Allocated by the network server". ‚ Application layer handling Application server routing profile: Select the "Application server" created before. ‚...
  • Page 58 Regarding the CSV file format, you must start from the exported CSV file from the SCM. Please refer to “Libelium Cloud management” section for further information on how to export this CSV file which includes all nodes OTAA credentials needed for direct batch import. Then, you must keep in mind that Actility needs more information to be included in that CSV file.

  • Page 59: The Things Network (Ttn)

    LoRaWAN Network Server setup CREATE_OTAA,<EUI1>,,LORA/GenericA.1.0.2a_ETSI_Rx2-SF12,<AppEUI1>,<AppKey1>,,dev-cs/testing,TWA_123,,Node1,,,,, CREATE_OTAA,<EUI2>,,LORA/GenericA.1.0.2a_ETSI_Rx2-SF12,<AppEUI2>,<AppKey2>,,dev-cs/testing,TWA_123,,Node2,,,,, CREATE_OTAA,<EUI3>,,LORA/GenericA.1.0.2a_ETSI_Rx2-SF12,<AppEUI3>,<AppKey3>,,dev-cs/testing,TWA_123,,Node3,,,,, CREATE_OTAA,<EUI4>,,LORA/GenericA.1.0.2a_ETSI_Rx2-SF12,<AppEUI4>,<AppKey4>,,dev-cs/testing,TWA_123,,Node4,,,,, CREATE_OTAA,<EUI5>,,LORA/GenericA.1.0.2a_ETSI_Rx2-SF12,<AppEUI5>,<AppKey5>,,dev-cs/testing,TWA_123,,Node5,,,,, 6.3. The Things Network (TTN) This section explains how to route information on TTN to the Customer Server or to the Smart Parking Cloud Service, using the HTTP protocol. TTN is a free and ready to use Network Server on the cloud for LoRaWAN communications.
  • Page 60 LoRaWAN Network Server setup Figure : Login credentials on TTN After a successful login, the main panel will be shown. From this screen the user can access different sections to manage her devices and view data: Figure : Main screen on TTN Click on “Console”...

  • Page 61: Manage Gateways

    LoRaWAN Network Server setup 6.3.2. Manage gateways Select "Gateways" to manage your devices. You can see a list of them (if you already created some gateways) or you can create a new gateway device: Figure : Main sections on TTN - Gateways Register a new gateway To register a new gateway, click on "Register gateway".
  • Page 62 LoRaWAN Network Server setup Figure : Create new gateway on TTN - Step 1 Figure : Create new gateway on TTN - Step 2 After filling all the fields, press "Register gateway" to confirm this new device. Gateway settings By clicking on the new created gateway, a new screen summarizing the information will appear. The user can edit the gateway information, change the settings, delete the registered gateway and see the traffic on the gateway.

  • Page 63: Manage Applications

    LoRaWAN Network Server setup Figure : Summarized information and edit settings on TTN An important option for the gateway is present on "Settings": at the bottom of the page there is a red button called "Delete gateway eui-XXX". This is used to perform a full deletion of the gateway. Do not click this option if you want to preserve your gateway as registered.
  • Page 64 LoRaWAN Network Server setup Figure : List of applications on TTN On the top right corner there is an "Add application" button to register a new application, click on this option to create a new one. Fill all the information and press "Add application" to confirm the data: Figure : Add new application on TTN Options and device registration overview There are plenty of options to configure an application.
  • Page 65 LoRaWAN Network Server setup Figure : Application overview on TTN On the top right area of the "Devices" section it is possible to register a new device for the application. Creating a new device is not required to perform the integration with the Customer Server or with the Smart Parking Cloud Service.
  • Page 66 LoRaWAN Network Server setup Figure : Form to create a new device on TTN There is also a chance to register more that one device in bulk using the "Bulk import devices" button placed on the top right: Figure : Bulk devices import on TTN The screen for a bulk import is very simple: - 65 - v7.5...
  • Page 67 LoRaWAN Network Server setup Figure : Bulk devices import form on TTN The parameters to fill are: • Device ID Prefix: This is the prefix for the generated device IDs. • App EUI: The App EUI all the devices will register to. •...
  • Page 68 LoRaWAN Network Server setup Figure : Integrations screen on TTN After clicking "Add integration", a list of third-party clouds will be displayed, choose "HTTP integration" to configure TTN to send towards the Customer Server or the Smart Parking Cloud Service: Figure : Integrations list on TTN - 67 - v7.5...
  • Page 69 LoRaWAN Network Server setup Figure : HTTP integration option on TTN The form for HTTP connection is as follows: Figure : HTTP integration form on TTN There are some fields to fill on the form: • Process ID: The unique identifier of the new integration process. Free text. - 68 - v7.5...
  • Page 70 LoRaWAN Network Server setup • Access Key: The access key used for downlink. It is the default key in most cases. • URL: The Customer Server URL: https://YOUR_CUSTOMER_SERVER_URL/api/parking/v2/services/ttn. • Method: The HTTP method to use. For Customer Server integration, it must be "POST". An example of configuration integration for Customer Server can be as shown in the image: Figure : Configuration on an HTTP integration with the Customer Server on TTN The rest of the integration fields must be blank.

  • Page 71: The Things Industries (Tti)

    LoRaWAN Network Server setup Application settings This section is a quick summary of the application settings as Handler, EUIs and Access Keys, among others. The user can change the parameters but it is possible to create here some misconfiguration on the application settings.

  • Page 72: Manage Gateways

    LoRaWAN Network Server setup Click on “Console” to open the 2 main sections on TTI: one for applications and one for gateways. 6.4.2. Manage gateways Select "Gateways" to manage your devices. You can see a list of them (if you already created some gateways) or you can create a new gateway device: Figure : Main sections on TTI - Gateways Register a new gateway...
  • Page 73 LoRaWAN Network Server setup Figure : Create new gateway on TTI - Step 1 Figure : Create new gateway on TTI - Step 2 After filling all the fields, press "Register gateway" to confirm this new device. Gateway settings By clicking on the new created gateway a new screen summarizing the information will appear. The user can edit the gateway information, change the settings, delete the registered gateway and see the traffic on the gateway.

  • Page 74: Manage Applications

    LoRaWAN Network Server setup Figure : Summarized information and edit settings on TTI An important option for the gateway is present on "Settings": at the bottom of the page there is a red button called "Delete gateway eui-XXX". This is used to perform a full deletion of the gateway. Do not click this option if you want to preserve your gateway as registered.
  • Page 75 LoRaWAN Network Server setup Figure : List of applications on TTI On the top right corner there is an "Add application" button to register a new application, click on this option to create a new one. Fill all the information and press "Add application" to confirm the data: Figure : Add new application on TTI Options and device registration overview There are plenty of options to configure an application.
  • Page 76 LoRaWAN Network Server setup Figure : Application overview on TTI On the top right area of the "Devices" section it is possible to register a new device for the application. Creating a new device is not required to perform the integration with the Customer Server or with the Smart Parking Cloud Service.
  • Page 77 LoRaWAN Network Server setup Figure : Form to create a new device on TTI There is also a chance to register more that one device in bulk using the "Bulk import devices" button placed on the top right: Figure : Bulk devices import on TTI The screen for a bulk import is very simple: - 76 - v7.5...
  • Page 78 LoRaWAN Network Server setup Figure : Bulk devices import form on TTI The parameters to fill are: • Device ID Prefix: This is the prefix for the generated device IDs. • App EUI: The App EUI all the devices will register to. •...
  • Page 79 LoRaWAN Network Server setup Figure : Integrations screen on TTI After clicking "Add integration", a list of third-party clouds will be displayed, choose "HTTP integration" to configure TTI to send towards the Customer Server or the Smart Parking Cloud Service: Figure : Integrations list on TTI - 78 - v7.5...
  • Page 80 LoRaWAN Network Server setup Figure : HTTP integration option on TTI The form for HTTP connection is as follows: Figure : HTTP integration form on TTI There are some fields to fill on the form: • Process ID: The unique identifier of the new integration process. Free text. - 79 - v7.5...
  • Page 81 LoRaWAN Network Server setup • Access Key: The access key used for downlink. It is the default key in most cases. • URL: The Customer Server URL: http://YOUR_CUSTOMER_SERVER_URL/api/parking/v2/services/tti. • Method: The HTTP method to use. For Customer Server integration, it must be "POST". An example of configuration integration for Customer Server can be as shown in the image: Figure : Configuration on an HTTP integration with the Customer Server on TTI The rest of the integration fields must be blank.
  • Page 82 LoRaWAN Network Server setup Application settings This section is a quick summary of the application settings as Handler, EUIs and Access Keys, among others. The user can change the parameters but it is possible to create here some misconfiguration on the application settings.

  • Page 83: Multitech Basestation

    Some MultiTech basestations come with the Libelium’s Custom App already installed on our facilities. Please go to the section "Installing/upgrading Libelium Custom App" if your basestation does not have it, or if you want to upgrade the version of the Custom App inside your basestation.
  • Page 84 Configs tab If you select the "Libelium Smart Parking Cloud Service" option, you must fill the "Token" field to send the node’s frames to our Smart Parking Cloud Service. Please refer to “Tools” section for further information about to how to create a token.
  • Page 85 On the Services Cloud Manager (SCM) you can download a CSV file with all your devices (all the devices associated with on your SCM account). To download the file, please refer to “Libelium Cloud management” section for further information on how to export this CSV file, which includes all nodes OTAA credentials needed for direct batch import.
  • Page 86 In order to change the password or user that the application brings by default, you have to connect through SSH to the MultiTech basestation. Once connected, navigate to where the configuration file is located at (var/config/app/libelium-multitech-app) and edit the ".env" file: # If you want to change the username and password to access de application: APP_USERNAME= 'admin' APP_PASSWORD= 'admin' Once you have changed the default username or password and saved the file, you need to stop the application and...
  • Page 87 LoRaWAN Network Server setup # If you want to use another port you must to change the APP_PORT field: APP_PORT= '3001' Once you have changed the default port and saved the file, you need to stop the application and restart it for the changes to take effect.

  • Page 88: Compatible Firmware Versions

    LoRaWAN Network Server setup Figure : Registering a device manually - 3 Restart the MultiTech basestation When you have finished the provisioning of your devices, regardless of the method you have used, you need to restart the MultiTech, so that changes take effect. We return to access the URL where we have the application installed;...
  • Page 89 LoRaWAN Network Server setup Figure : Create account or login on DeviceHQ DeviceHQ panel After a successful login, the main panel appears. The user can see many options to manage devices, install applications, upgrade the firmware, see logs, etc: Figure : DeviceHQ main panel Registering a MultiTech device on DeviceHQ Once inside the DeviceHQ panel, go to "Devices"...
  • Page 90 To add the Custom App, go to "Store" on the top menu of the DeviceHQ panel and check the "Public apps" option to see all the public apps. Then search the "libelium-multitech-app". Once you have found it, click on Add to My Apps and again on the "Add to my apps"...
  • Page 91 LoRaWAN Network Server setup Figure : Enable remote management Click on the "Submit" button. Once changes have been saved, the Multitech must be restarted for the changes to take effect, so press the "Save & Restart" button. Schedule install or upgrade the Custom App In the DeviceHQ panel, "Devices"...
  • Page 92 LoRaWAN Network Server setup Figure : Check-In to DeviceHQ - 91 - v7.5...

  • Page 93: Customer Server

    URL containing your server domain name or IP. The context should point to the web application deployment path. Note: Customers can ask for this source code to our Sales Team (sales@libelium.com) after buying the nodes. - 92 -...

  • Page 94: Installation

    In order to install the Customer Server using the server option, you will need access to your server to install all the dependencies and to configure the Apache server. 7.2. Deploying 7.2.1. Docker Step 1: Extract on your server the zip file provided by Libelium containing the Customer Server application ‚ source files. - 93 -...

  • Page 95: Server

    "8001:3306" Note: The port can be any open port on your server. 7.2.2. Server Step 1: Extract on your server the zip file provided by Libelium containing the Customer Server application ‚ source files. Step 2: Check the right owner/group and permissions of all the files extracted, usually using www-data group ‚...

  • Page 96: Configuring The Application

    Customer Server Step 4: Configure in your server the context of the callback server application with the path where the source ‚ files were extracted. Copy and paste the following text as content of the file “my_server.conf” file located on “/etc/apache2/sites-available”...
  • Page 97 Customer Server APP_NAME='Smart Parking v2 - Customer Server' APP_ENV=local APP_DEBUG=false APP_URL=http://localhost APP_TIMEZONE=UTC # Set to true to use the database: USE_DB=false # This data should match the data on the file docker-compose.yml: DB_CONNECTION=mysql DB_HOST=db DB_PORT=7001 DB_DATABASE=LoriotDB DB_USERNAME=user DB_PASSWORD=password CACHE_DRIVER=file # It is mandatory to set a service (Loriot|Actility|LwTTN|LwTTI|Multitech): SERVICE='' # If you want to use Loriot you must fill these fields: LORIOT_URI=''...

  • Page 98: How To Configure Loriot

    Customer Server # If you want to use MultiTech you must fill these fields: MTT_USERNAME= '' MTT_PASSWORD= '' MTT_URI= '' You must specify which service you want to use; you must fill all the configuration fields for the selected one. 7.3.1.

  • Page 99: How To Configure Actility

    Customer Server Figure : Loriot token Figure : Loriot API key 7.3.2. How to configure Actility Write “Actility” in the “SERVICE” field: SERVICE='Actility' And the remaining field: ACTILITY_URI='actilityURI' “actilityURI” is the downlink URL that Actility provides to send information from the server to the node. This URL is the address of the primary Actility LRC cluster.
  • Page 100 Customer Server TTN_REGION must be a valid LoRaWAN region, these regions are: • ttn-eu • ttn-brazil • ttn-us-west • ttn-asia-se For instance, for the European region the field must be ’ttn-eu’: TTN_REGION='ttn-eu' “TTN_APP_ID” is the Application ID from the application created on the TTN console. The user can find this value on the “Overview”...

  • Page 101: How To Configure The Things Industries (Tti) 1

    Customer Server Figure : Downlink port for device on TTN TTN_PORT=1 “TTN_KEY” appears at the bottom of the “Application overview” section on Access Keys. Click on the copy icon to get the key. This key is a long hexadecimal string. For instance if the key is “ttn-account-v2.HlR_fV9YsXE8TGTzFVEP-Byr”, the configuration will be: Figure : Access Key for “test_libelium”...
  • Page 102 Customer Server Figure : Application ID for “test_libelium” on TTI TTI_APP_ID='test_libelium' “TTI_PROCESS_ID” is displayed on the integration overview configuration. Go to the selected integration and the Process ID is available over the “Integration overview” section. For instance if the Process ID has the value “libelium1234”, the configuration will be as follows: Figure : Process ID on TTI TTI_PROCESS_ID='libelium1234'...

  • Page 103: How To Configure A Multitech Basestation 1

    Customer Server Figure : Access Key for “test_libelium” on TTI TTI_KEY='ttn-account-v2.HlR_fV9YsXE8TGTzFVEP-Byr' Finally if we gather all parameters, the configuration will be set as follows: TTI_URI='https://integrations.YOUR_COMPANY.thethings.industries' TTI_APP_ID='test_libelium' TTI_PROCESS_ID='libelium1234' TTI_PORT=1 TTI_KEY='ttn-account-v2.HlR_fV9YsXE8TGTzFVEP-Byr' 7.3.5. How to configure a MultiTech basestation Write ’Multitech’ in the “SERVICE” field: SERVICE='Multitech' “MTT_USERNAME”...
  • Page 104 Customer Server 7.4. Making the server accessible from anywhere 7.4.1. Configuring a domain pointing to the customer server 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 (see http://www.noip.com/). No-ip has also a client application responsible for updating any IP address changes in the background (for more information go to http://www.noip.com/download).
  • Page 105 Customer Server Figure : Smart Parking node selection Once a node is selected, its current configuration is displayed and you can modify it. For further information of the node parameters, please refer to the chapter “Smart Parking node”. Figure : Smart Parking node configuration Once you have configured the node or nodes, press the “Save configuration”...
  • Page 106 Customer Server Figure : Frame enqueued for processing So the Remote Configuration Form application allows the user to update some node parameters, just as the Smart Devices App does. However, using the Smart Devices App requires physical access to the Smart Parking node: the node must be plugged to a computer with a USB cable.
  • Page 107 Customer Server Figure : Customer Server Core Database Field Field updated by Description LW_EUI All uplink frames The node’s unique LoRaWAN EUI. LW_ts All uplink frames The uplink frame timestamp. The LoRaWAN protocol uplink counter. This field belongs LW_up_counter All uplink frames to the link level.
  • Page 108 Customer Server Field to indicate the loss of a LoRaWAN protocol lost_up_counter (*) All uplink frames sequence number. Field to indicate the loss of an application sequence lost_seq (*) All uplink frames number. Field to indicate an error in sensor management (0: no sensor_error Info, Keep-alive, RTC update error).
  • Page 109 Customer Server Figure : Database table example Once data is stored on the database, you can use any compatible tool to query the database and develop your own data analysis and visualization. This task belongs entirely to the customer or system integrator. Figure : Example of database visualization using Grafana (basic open-source application) 7.7.
  • Page 110 7.7.3. Adding a new unsupported LoRaWAN Network Server To add a new LoRaWAN Network Server (different from the officially supported by Libelium) you have to create a new PHP class that must implement the interface located on src/app/Helpers/Services/LwServiceInterface.php.
  • Page 111 7.8. Upgrading the Customer Server If you want to upgrade the Customer Server you need to download the new version from the link provided by our Sales Team (sales@libelium.com) and uncompress the files to a new folder. For example: Old version:...
  • Page 112 Customer Server /path/to/old/smart-parking-customer-server/ patch -p0 < /path/to/upgrade.diff Note: You can also add the flag ’-b’ to the “patch” command to create a backup of each modified file. Once the patch process is completed, you will have to review your “.env” file and add the new options that you can find in the patched “.env.example”...

  • Page 113: Libelium Smart Parking Cloud Service

    Smart Parking Cloud Service license. The Smart Parking Cloud Service can be understood as one of the services that we offer on our Libelium Cloud (officialy called Services Cloud Manager - SCM). Other services hosted on the SCM are the Programming Cloud Service or the Bridge.

  • Page 114: Remote Configuration 1

    Libelium Smart Parking Cloud Service Figure : Accessing the Smart Parking Cloud Service (2nd way) Once the user has a valid license, the following features will be available accessing the Smart Parking Cloud Service: configure nodes remotely, configure the LoRaWAN service, check the logs for the configured service and generate the tokens and keys needed for the LoRaWAN network server.

  • Page 115: Service Configuration 1

    Libelium Smart Parking Cloud Service Figure : Remote Configuration Form Once you have configured the node(s) and the service as explained in the section “Service configuration”, press the “Save configuration” button. A message indicates that a downlink frame with the node’s configuration has been enqueued to the LoRaWAN Network Server downlink queue.
  • Page 116 Libelium Smart Parking Cloud Service 8.1.2. Service configuration The Smart Parking Cloud Service is compatible with the following LoRaWAN Network Servers: Loriot, Actility, The Things Network (TTN), The Things Industries (TTI) and the Embedded Network Server inside MultiTech basestations. These are the URLs to be configured on the LoRaWAN Network Server: Loriot: https://api.libelium.com/cloud/parking/v2/services/loriot...
  • Page 117 Libelium Smart Parking Cloud Service Figure : Actility configuration If you want to use TTN as your LoRaWAN Network Server, you have to select it on the drop-down menu and complete the required fields. To find the information on the TTN panel, you can follow the instructions described on the “How to configure The Things Network (TTN)”...
  • Page 118 Libelium Smart Parking Cloud Service • USA: Uses value ttn-us-west • Brazil: Uses value ttn-brazil • Asia: Uses value ttn-asia-se For further information about TTN regions, please see documentation. If you want to use TTI as your LoRaWAN Network Server, you have to select it on the drop-down menu and complete the required fields.

  • Page 119: Tools 1

    Libelium Smart Parking Cloud Service Figure : MultiTech configuration Regardless of the service you have configured, click the button “Save configuration” to save your LoRaWAN service configuration. Then a message will be displayed indicating that the service has been updated or saved correctly.
  • Page 120 Libelium Smart Parking Cloud Service Step 2: Set a name for the new API key and click the “Create” button. Figure : Step 2 - TTN integration Step 3: The new API key is shown, copy it. Figure : Step 3 - TTN integration Step 4: Paste the API key on the “Authorization”...
  • Page 121 Libelium Smart Parking Cloud Service Figure : Step 4 - Authorization field on TTN HTTP integration Authentication token for HTTP integration with TTI The Smart Parking Cloud Service uses tokens for authentication. The user must 1st create a token (an API key) and then use it on TTI.
  • Page 122 The Smart Parking Cloud Service uses tokens for authentication. The user must 1st create a token (an API key) and then use it on the MultiTech basestation. Perform these steps to create a new API key and set it on the Libelium custom app in the MultiTech basestation: Step 1: Click “Create new API Key” on the “Tools” tab.
  • Page 123 Libelium Smart Parking Cloud Service Figure : Step 1 - MultiTech integration Step 2: Set a name for the new API key and click the “Create” button. Figure : Step 2 - MultiTech integration Step 3: The new API key is shown, copy it.
  • Page 124 Libelium Smart Parking Cloud Service Figure : Step 3 - MultiTech integration Step 4: Paste the API key on the “Token” field of the “Congigs” tab and press “Save configs”. Figure : Step 4: Authorization field on MultiTech integration Save Service Configuration Regardless of the service you have configured, click the button “Save configuration”...
  • Page 125 Libelium Smart Parking Cloud Service Figure : Log viewer Click the “Refresh” button to update the log view and load new messages available. The latest messages appear at the bottom of the viewer. Figure : “Refresh” button 8.1.4. Tools The “Tools” tab allows users to download the Device Node Keys associated with their account, as well as generate the necessary token to configure your Loriot network server correctly.
  • Page 126 Libelium Smart Parking Cloud Service Figure : Tools The Node Keys is a CSV-format file. It is ready to use in the LoRaWAN Network Server to configure all the Smart Parking nodes associated with their account in the SCM. It can be downloaded by clicking on the “Download Nodes Keys”...
  • Page 127 Libelium Smart Parking Cloud Service Figure : Generated key Once the token has been generated, you can use it on Loriot backend as described in the “Manage Loriot output data” section. - 126 - v7.5...

  • Page 128: Deployment And Installation

    Smart Devices App. This 2nd option increases the provisioning time. So Libelium recommends to use the default IDs and keys. If factory default keys are used, then a CSV file exported from Libelium Cloud Services Manager (SCM) can be used to ease the bulk import into the LoRaWAN Network Server.

  • Page 129: How To Place The Nodes 1

    Deployment and installation 9.2. How to place the nodes The correct installation spot is the center of the parking slot to ensure the best detection. It is possible to install the nodes on different parking slot configurations: Parallel ‚ Perpendicular ‚...

  • Page 130: Node Installation 1

    Deployment and installation Important: It is important to keep in mind that parking slots must be delimited by lines so the node is placed in the center of the parking area. Placing the nodes with no line definitions may lead into bad behaviour. 9.3.

  • Page 131: On-Surface Node Installation 1

    Deployment and installation 9.3.2. On-surface node installation Figure : Step by step chemical fixing and anchor installation Firstly, mark 4 holes in the asphalt. Select an area as flat and regular as possible, avoid irregularities on the terrain. You should place the enclosure in the final location and use the 4 holes as a reference to drill 4 little marks on the ground.
  • Page 132 Deployment and installation Figure : Drill the holes (step 1) Step 2, 3 and 4: Blow out dust and loose materials. Remove all the dust and little rocks inside the 4 holes, created during the drilling operation. This is important to allow the anchors go all the way down.
  • Page 133 Deployment and installation Step 5: Inject the chemical fixing. The chemical fixing shall be injected into the 4 holes carefully. You must keep in mind that this chemical adhesive must fill the complementary space the anchor leaves in the hole. So the whole hole does not have to be fully filled with adhesive because there is no space left for the anchor.
  • Page 134 Deployment and installation Figure : Final anchor installation (step 7) Step 8: Place the node. Place the black rubber circle on the ground. To enable the correct screwing of the screws inside the anchors, make sure that there is no dust in the internal thread of the anchor. Install the node in its final position and screw the 4 special (anti-vandalism) screws provided.
  • Page 135 Deployment and installation Figure : Final section of the anchor and screw - 134 - v7.5...

  • Page 136: Underground Node Installation 1

    Figure : Snowplow vehicle For this special installation, Libelium provides flat enclosures. Contact your Sales agent to order flat enclosures. Figure : Flat Smart Parking enclosure dimensions - 135 -...
  • Page 137 The Epoxy resin tested by Libelium provides a curing time around 6-12 hours at 20 ºC and RH 50%. So the parking installation must not be used prior this curing time.
  • Page 138 Deployment and installation Figure : Pour Epoxy curing agent into the granular resinous material Figure : Preparing the Epoxy resin mixture In this installation, it is crucial that the upper side of the enclosure is not covered with Epoxy or other material. Only the side slides can be covered, the center of the node must be clean to allow the radar signal work properly.

  • Page 139: Semi-Underground Node Installation 1

    Deployment and installation 9.3.4. Semi-underground node installation This is a possible installation in order to provide vandalism immunity and also rain/puddle immunity. So the node partially inserted in the ground and the vaulted enclosure minimizes the water issues. The same underground installation steps must be followed as seen in the previous section. In the node placement step, the vaulted enclosure must exceed the horizontal pavement layer by 6-7 mm approximately.

  • Page 140: Node Start-Up 1

    Deployment and installation 9.4. Node start-up After the node is installed, you must follow the "Magnet start-up" steps explained in the "Magnet start-up process" section. This process is based on 3 consecutive magnet resets waiting at least one second between each reset. In the future need of resetting the node manually, just a single magnet reset will be needed.

  • Page 141: Working Example 1

    Deployment and installation 9.5. Working example The next diagram explains how the node program works when the node is installed and started when the parking slot is free. On the left column you can appreciate the parking lot status during the execution. On the right side you can see the frame types that are sent to the Smart Parking Cloud Service or to the Customer Server depending on: parking slot status changes, elapsed time and user configuration changes.

  • Page 142: Certifications

    10. Certifications 10.1. CE (European Union) In accordance with the RED Directive, Libelium Comunicaciones Distribuidas S.L. declares that the “Smart Parking v2 EU” device is in conformity with the European Union legislation and with the following harmonized standards and technical specifications: EN 50581:2012 ‚...

  • Page 143: Safety Guides

    Safety Guides 11. Safety Guides 11.1. Smart Parking Chemical Fixing Cartridge - 142 - v7.5...
  • Page 144 Safety Guides - 143 - v7.5...
  • Page 145 Safety Guides - 144 - v7.5...
  • Page 146 Safety Guides - 145 - v7.5...
  • Page 147 Safety Guides - 146 - v7.5...
  • Page 148 Safety Guides - 147 - v7.5...
  • Page 149 Safety Guides - 148 - v7.5...
  • Page 150 Safety Guides - 149 - v7.5...
  • Page 151 Safety Guides - 150 - v7.5...
  • Page 152 Safety Guides - 151 - v7.5...
  • Page 153 Safety Guides - 152 - v7.5...
  • Page 154 Safety Guides - 153 - v7.5...

  • Page 155: Documentation Changelog

    Documentation changelog 12. Documentation changelog From v7.4 to v7.5: Deprecated the "Keep-alive night-mode" setting in all configuration forms: Smart Parking Cloud Service, ‚ Customer Server and Smart Devices App Added new section to describe the Smart Parking Node’s label with device’s specifications ‚...

Table of Contents