Libelium Waspmote Smart Parking v2 Quick start guide

INDEX
Document version: v7.5 - November 27, 2019
© Libelium Comunicaciones Distribuidas S.L.
INDEX
1. Introduction ......................................................................................................... 6
2. Network architecture ........................................................................................... 7
2.1. Smart Parking node ............................................................................................. 8
2.2. LoRaWAN base station ......................................................................................... 8
2.3. LoRaWAN Network Server ..................................................................................... 8
2.4. Libelium Smart Parking Cloud Service and Customer Server ........................................ 9
3. Smart Parking node .............................................................................................. 11
3.1. Hardware description........................................................................................... 11
3.1.1. Node versions ......................................................................................... 13
3.1.2. LoRaWAN regions..................................................................................... 13
3.1.3. LoRaWAN protocol and parameters ............................................................. 13
3.1.4. Identification label.................................................................................... 14
3.2. Power and time consumption ................................................................................ 14
3.2.1. Smart Parking EU ..................................................................................... 15
3.2.2. Smart Parking US ..................................................................................... 15
3.3. User switches ..................................................................................................... 15
3.4. Reset button ...................................................................................................... 16
3.5. Node setup ........................................................................................................ 16
3.5.1. "Ready to install" state .............................................................................. 16
3.5.2. How to close the Smart Parking node........................................................... 17
3.5.3. "Magnet start-up" process ......................................................................... 18
3.6. How the node works ............................................................................................ 19
3.6.1. Frame types ............................................................................................ 19
3.6.2. Frame header.......................................................................................... 20
3.6.3. Frame payload ........................................................................................ 20
3.6.4. Node program flowchart ........................................................................... 22
3.7. Node parameters ................................................................................................ 23
3.7.1. Parameters description and ranges ............................................................. 23
3.7.2. Understanding Info and Keep-alive frames ................................................... 24
3.7.3. Understanding night-mode ........................................................................ 24
3.7.4. Understanding RTC synchronization ............................................................ 25
3.7.5. Understanding uplink frames format (real example) ....................................... 26
3.7.6. Factory default values ............................................................................... 27
3.7.7. Configure new parameter values................................................................. 28
4. Libelium Cloud management ................................................................................ 29
4.1. Introduction to the Libelium Services Cloud Manager - SCM ........................................ 29
4.2. SCM account ...................................................................................................... 30
- 2 - v7.5

INDEX
4.2.1. Creating an account.................................................................................. 30
4.2.2. Signing in ............................................................................................... 31
4.3. Smart Parking nodes registration ........................................................................... 32
4.4. Editing Smart Parking nodes.................................................................................. 33
4.5. Export CSV file with nodes credentials ..................................................................... 34
5. Smart Devices App................................................................................................ 36
5.1. How to install the Smart Devices App ...................................................................... 36
5.1.1. Start Smart Devices App on Windows........................................................... 37
5.1.2. Start Smart Devices App on GNU/Linux ........................................................ 38
5.1.3. Start Smart Devices App on MacOSX ............................................................ 38
5.2. Upgrading the Smart Devices App .......................................................................... 38
5.3. Smart Parking v2 ................................................................................................ 38
5.3.1. How to plug the Smart Parking node............................................................ 39
5.3.2. Configuration .......................................................................................... 39
5.3.3. Programmer (change node parameters) ....................................................... 40
5.3.4. Firmware upgrade .................................................................................... 41
5.3.5. Factory Reset .......................................................................................... 43
6. LoRaWAN Network Server setup . . .... .... . .... .... . .... .... . .... .... . .... .... . .... ... ..... .... ..... .... ... 44
6.1. Loriot ................................................................................................................ 44
6.1.1. Log in .................................................................................................... 44
6.1.2. Create a new Loriot application................................................................... 45
6.1.3. Manage Loriot output data ........................................................................ 46
6.1.4. How to delete unused Loriot applications ..................................................... 47
6.1.5. How to create a single device manually ........................................................ 48
6.1.6. Nodes batch provisioning in Loriot .............................................................. 49
6.2. Actility ............................................................................................................... 51
6.2.1. How to create a new Application Server........................................................ 51
6.2.2. How to create a new AS routing profile ......................................................... 53
6.2.3. How to create new devices manually............................................................ 55
6.2.4. Nodes batch provisioning in Actility ............................................................. 56
6.3. The Things Network (TTN) ..................................................................................... 58
6.3.1. Log in .................................................................................................... 58
6.3.2. Manage gateways .................................................................................... 60
6.3.3. Manage applications................................................................................. 62
6.4. The Things Industries (TTI) .................................................................................... 70
6.4.1. Log in .................................................................................................... 70
6.4.2. Manage gateways .................................................................................... 71
6.4.3. Manage applications................................................................................. 73
6.5. MultiTech basestation .......................................................................................... 82
6.5.1. Libelium’s Custom App .............................................................................. 82
6.5.2. Compatible firmware versions .................................................................... 87
6.5.3. Installing/upgrading Custom App ................................................................ 87
- 3 - v7.5

INDEX
7. Customer Server................................................................................................... 92
7.1. Installation ......................................................................................................... 93
7.1.1. Docker ................................................................................................... 93
7.1.2. Server .................................................................................................... 93
7.2. Deploying .......................................................................................................... 93
7.2.1. Docker ................................................................................................... 93
7.2.2. Server .................................................................................................... 94
7.3. Configuring the application ................................................................................... 95
7.3.1. How to configure Loriot............................................................................. 97
7.3.2. How to configure Actility............................................................................ 98
7.3.3. How to configure The Things Network (TTN) .................................................. 98
7.3.4. How to configure The Things Industries (TTI).................................................100
7.3.5. How to configure a MultiTech basestation.....................................................102
7.4. Making the server accessible from anywhere ............................................................103
7.4.1. Configuring a domain pointing to the customer server ....................................103
7.5. Remote Configuration Form ..................................................................................103
7.6. Customer Server Core ..........................................................................................105
7.6.1. End-point ...............................................................................................105
7.6.2. Data Parser.............................................................................................105
7.6.3. Database ................................................................................................105
7.7. Modifying the Customer Server..............................................................................108
7.7.1. Extracting data from the Customer Server ....................................................108
7.7.2. Modifying the Database ............................................................................109
7.7.3. Adding a new unsupported LoRaWAN Network Server ....................................109
7.8. Upgrading the Customer Server .............................................................................110
8. Libelium Smart Parking Cloud Service .. . ... . .... .... . .... .... . .... .... . .... .... . .... .... .... .... . .... ...112
8.1. Smart Parking Cloud Service ..................................................................................112
8.1.1. Remote configuration ...............................................................................113
8.1.2. Service configuration ................................................................................115
8.1.3. Log........................................................................................................123
8.1.4. Tools .....................................................................................................124
9. Deployment and installation .................................................................................127
9.1. Step-by-step guideline..........................................................................................127
9.2. How to place the nodes ........................................................................................128
9.3. Node installation .................................................................................................129
9.3.1. Triple installation option ............................................................................129
9.3.2. On-surface node installation ......................................................................130
9.3.3. Underground node installation ...................................................................135
9.3.4. Semi-underground node installation............................................................138
9.4. Node start-up .....................................................................................................139
9.5. Working example ................................................................................................140
- 4 - v7.5

INDEX
10.Certifications .......................................................................................................141
10.1. CE (European Union) ............................................................................................141
10.2. FCC (United States) ..............................................................................................141
11.Safety Guides .......................................................................................................142
11.1. Smart Parking Chemical Fixing Cartridge..................................................................142
12.Documentation changelog ....................................................................................154
- 5 - v7.5

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.
Figure : Simplified Smart Parking network architecture
The nodes provisioning has been enormously improved. The nodes are delivered with default time settings and
also unique LoRaWAN identifiers and keys. So it is easy to use the default settings to register all nodes in the
LoRaWAN network server at a time.
The Smart Parking node improves the detection and stability performance thanks to a radar sensor which permits
to certainly know when objects are placed over the device. The next table shows a comparative analysis of the
current sensor technologies in the Smart Parking market:
- 6 - v7.5

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). This allows the user to remotely configure the node parameters
(sleep time, keep-alive, night-mode, etc) via the Remote Configuration Form. That makes it possible to directly
install the nodes with factory default settings and then update them from the server side.
Figure : Remote Configuration Form
- 6 - v7.5

Network architecture
2. 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

Network architecture
2.1. Smart Parking node
The Smart Parking node is the device installed in each parking slot. When the device detects a change of the parking
slot status (free/occupied), it sends a frame to the LoRaWAN base station.
Figure : Smart Parking node
2.2. LoRaWAN base station
The LoRaWAN base station (also known as gateway) must be installed in the surrounding area next to the parking
nodes. 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). Also, some of them integrate an
embedded LoRaWAN Network Server.
Figure : LoRaWAN base station
2.3. LoRaWAN Network Server
The nodes registration must be done in the Network Server in order to receive LoRaWAN data from all nodes in
the network. Each node must be registered with an identifier and some encryption keys so the Network Server can
receive and decrypt the packets successfully.
The LoRaWAN Network Server purpose is to translate data from the LoRaWAN wireless network to an IP network.
Therefore, when Smart Parking nodes packets are received, a callback is performed in order to send data to the
- 8 - v7.5

Network architecture
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
‚Actility
‚The Things Network
‚The Things Industries
‚The Embedded Network Server inside MultiTech base stations
If the customer wants to use a new LoRaWAN Network Server, then the Data Parser block must be modified in
order to receive data properly. Keep in mind that each Network Server implements its own HTTPS callback using a
different format.
The Remote Configuration Form allows the user to update the settings of each node (sleep time, keep-alive time,
night-mode, etc). The update is done remotely via LoRaWAN downlink radio packets.
The difference between the 2 types of server differ in the the possible client needs:
‚The Customer Server is a software system provided by Libelium which permits to receive, decode and insert
data into a standard MySQL database. It is mandatory that the user sets up her own server to host the
Customer Server. Read the “Customer Server” chapter for further information.
‚The Smart Parking Cloud Service is a software service provided by Libelium which permits to receive,
decode and redirect the data to the final 3rd party IoT cloud (Amazon, Azure, etc). This retransmission is
done thanks to the cloud connectors running on another Libelium Cloud’s service: the Bridge. Read the
“Libelium Smart Parking Cloud Service”chapter for further information.
- 9 - v7.5

Network architecture
Figure : Libelium Smart Parking Cloud Service scenario
Figure : Customer Server scenario
- 10 - v7.5

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
- 11 - v7.5

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 Radar (main) and magnetic (backup)
Provisioning Ready to install (default LoRaWAN OTAA IDs and key are loaded to each node)
Node configuration Via "Remote Configuration Form" (web form)
LoRaWAN configuration Via "Smart Devices App" (Java desktop application)
Operating temperature -20 to +65 °C
(*) Under normal circumstances and depending on settings
Figure : Vaulted enclosure dimensions
- 12 - v7.5

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)
SP-IN Smart Parking IN 865.0 to 867.0 MHz (LoRaWAN IN865-867)
SP-APLA-AS Smart Parking APAC / LATAM / AU / AS923 923 MHz (LoRaWAN AS923)
3.1.2. LoRaWAN regions
The Smart Parking node supports the next LoRaWAN regions:
LoRaWAN region Supported by
EU 863-870 MHz ISM Band (Europe) Smart Parking EU
US 902-928 MHz ISM Band (United States) Smart Parking US
AU 915-928 MHz ISM Band (Australia) Smart Parking APAC / LATAM / AU / AU915
IN 865-867 MHz ISM Band (India) Smart Parking IN
AS 923 MHz ISM Band (Asia and ASEAN region) Smart Parking APAC / LATAM / AU / AS923
CN 779-787 MHz ISM Band (China) Not available
CN 470-510 MHz ISM Band (China) Not available
KR 920-923 MHz ISM Band (South Korea) Not available
433 MHz ISM Band (Worldwide) Not available
If you are interested in further information about LoRaWAN country regulations, please refer to the LoRa Alliance
regional parameters document.
3.1.3. LoRaWAN protocol and parameters
LoRaWAN is a Low Power Wide Area Network (LPWAN) protocol. It is a spread-spectrum modulation technique at
extremely low data-rates which permits sending data achieving long ranges.
The most important LoRaWAN parameters are:
‚LoRaWAN EUI: Read-only, 8-byte, unique identifier which defines each LoRaWAN module in the market.
‚Device EUI: Read/write, 8-byte identifier configured into the LoRaWAN module to be used as operating
identifier. By default, the "LoRaWAN EUI" of the module is factory-configured as "Device EUI" in the Smart
Parking node.
‚Join mode: ABP or OTAA. Defines how the module joins the network. Different keys are needed for each
method.
‚Device address: Needed for ABP. The 4-byte address of the the LoRaWAN module. Must be unique in its own
sub-network.
‚Network Session Key: Needed for ABP. The 16-byte AES key. Used to generate Message Integrity Check.
‚Application Session Key: Needed for ABP. The 16-byte AES key. Used to encrypt data.
‚Application EUI: Needed for OTAA. The 8-byte application identifier. Needed for opening an OTAA session and
exchange encryption keys.
- 13 - v7.5

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
-LoRaWAN AS923 version: SF12 / 125 kHz
-LoRaWAN US902-928 version: SF10 / 125 kHz
-LoRaWAN AU915-928 version: SF10 / 125 kHz
‚ADR: Adaptive Data Rate setting which can be enabled or disabled. If ADR is enabled, the server will optimize
the data-rate based on the information collected from the network: the RSSI/ SNR of the last received packets.
If you are interested in further information about LoRaWAN specifications, please refer to the LoRa Alliance
specifications document.
3.1.4. Identification label
There is a sticker on the bottom side of the Smart Parking node base. In this sticker, several device specifications
can be seen. For example the "Model" which refers to the device’s region. Also, the unique "LoRaWAN EUI" is
displayed so each node can be distinguished.
Figure : Smart Parking node label
3.2. Power and time consumption
The Smart Parking node firmware executes different steps since the node is started. Firstly, the node’s setup and
then an infinite loop where every cycle is based on measuring, sending if needed and sleeping. The next tables
show the power and time consumption of each step modelled as a pulse of a specific time duration and average
power consumption.
- 14 - v7.5

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 6 s
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. Smart Parking US
Power consumption Time consumption
Node setup 21.8 mA 53 s
Measure cycle 26 mA 340 ms
Measure and send cycle 20 mA 3.6 s
Sleep cycle 5.5 uA Depends on sleep time settings
(*) LoRaWAN US is set to the default SF10 settings (worst case). The send process may be lower power if the node is close to the base station.
3.3. User switches
The Smart Parking node has 2 switches to manage the working mode:
‚On/Offswitch: Determines whether the node is powered-on or powered-off
‚App/Boot switch: When the node is powered-on, this switch determines the performance state of the device
-App position must be used for a normal operation mode, so the device executes the firmware within it
-Boot position must be used for configuring purposes only
Figure : Smart Parking node "user switches"
When the node is powered-on (On switch), you can change from App to Boot or viceversa by changing the state
of the App/Boot switch. However, you must press the reset button to apply the operation mode change. Another
- 15 - v7.5

Smart Parking node
possibility to successfully change the operation mode step-by-step would be to: power down the device (Offswitch),
change the App/Boot switch, press the reset button and then power on the device.
Important:
Never leave the device set to On and Boot for more time than needed. The bootloader does not provide any sleep
mode and it will waste the battery of the device. So when you finish reconfiguring the device, please set the node
in off state.
3.4. Reset button
The reset button can be used to re-start the node in the corresponding operation mode (App or Boot). If the node
is set up to "App" (normal operation mode), pressing the reset button will re-start the program execution. On the
other hand, if the node is set up to Boot (configuration mode), pressing the reset button will re-start the MCU
bootloader for reconfiguration or firmware update.
Figure : 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" and "Off" (press the reset button to make sure you discharge capacitors)
‚Step 2: You power the device on by sliding the switch from "Off" to "On"
‚Step 3: Both LEDs (red and green) blink rapidly for 5 times
‚Step 4: Red LED blinks once for 1 second to indicate that the device enters sleep mode for the 1st time. Now
the node is in a "ready to install" state. The customer should install the node on the real scenario and perform
the "Magnet start-up" process.
- 16 - v7.5

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.
‚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.
‚Step 3: Place the inner casing inside the outer casing and make sure that the 2 position marks match.
Figure : Enclosure position marks
- 17 - v7.5

Smart Parking node
‚Step 4: Insert the screws and tighten them halfway.
Figure : Screws in their position
‚Step 5: Finally, tighten the 4 screws firmly. Do not use the maximum pressure (do not go all the way with the
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; this would cancel the waterproof quality too.
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 EUIand random private keys.
On the other hand, if different LoRaWAN parameters are desired, “Smart Devices App”must be used to change the
settings and repeat the previously explained steps.
3.5.3. "Magnet start-up" process
Once the node has been set to "ready to install" state and it has been closed and placed on the parking slot, the
"magnet start-up" must be done. This process consists on resetting the device using the magnet for 3 consecutive
times. Each magnet reset must be separated by at least one second period.
The best way to proceed with the magnet is to go over the enclosure from left to right in a one-motion movement.
Then wait for at least one second (although you can wait more) and proceed again until you complete 3 magnet
resets.
Figure : Magnet reset
- 18 - v7.5

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.
Important:
The "magnet start-up" is only mandatory when the node is powered from a power-off state. In other words, when
the device is set to a "ready to install" state.
3.6. How the node works
3.6.1. Frame types
The Smart Parking architecture manages different uplink and downlink frames.
The next table shows the Uplink frames:
Frame type #num Description
Start frame 1 4 First frame sent by the node when starting (with params settings)
Start frame 2 5 Second frame sent by the node when starting (with params settings)
Info frame 0 Used to inform a Parking Status change
Keep-alive frame 1 Used to inform the device keeps working since last reported status
Configuration uplink 2 Used to confirm a "Configuration downlink" was applied or not
RTC update request 7 Used to request for an RTC sync once every day
The next table shows the Downlink frames:
Frame type #num Description
Configuration downlink 3
Used to update the node parameters. After the customer sets up a new
node configuration in the Remote Configuration Form a new "Configuration
downlink" frame is enqueued into the LoRaWAN network server’s downlink
queue.
RTC sync frame 6 Used to sync the node’s RTC to the server’s timestamp. It is the mandatory
response to "Start frame 1" and "RTC update request" uplink frames.
The uplink frames are 11-byte long to always comply with the LoRaWAN datarate worst case scenario. Their
structure consists on 2 parts: header and payload. The "header" format is always the same for all uplink frame
types. On the other hand, the "payload" format may be different for each frame type.
Header Payload
2 bytes 9 bytes
Regarding the downlink frames, they have variable length and its format is private to the customer. The "RTC sync
frame" is the mandatory response for both "Start Frame 1" and "RTC update request" frames. The "RTC sync frame"
provides the server time to the nodes in order to keep the RTC updated. Also, the "Configuration downlink" is an
asynchronous frame sent by the server when the Remote Configuration Form is managed by the customer.
You must keep in mind that when a downlink packet is requested there are usually some issues related to LoRaWAN
- 19 - v7.5