How it Works
Libelium
Loading...
Waspmote Smart Parking v2
Technical Manual
155 pgs36.74 Mb0
Table of contents
Loading...

Libelium Waspmote Smart Parking v2 Technical Manual

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.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.1. Smart Parking EU . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . .. . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. 15
3.2.2. Smart Parking US . . . . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. 15
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.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.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
- 2 - v7.5
INDEX
4.2.1. Creating an account. .. . .. . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . .. . .. . .. . . 30
4.2.2. Signing in .. . .. . . . .. . .. . .. . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. 31
4.3. Smart Parking nodes registration . . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . . . . . . . .. . .. . . . .. . .. . . . . . . .. 32
5. 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.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.1. Log in . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . . . . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . .. . .. . .. . . . .. . .. 58
6.3.2. Manage gateways . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . 60
6.3.3. Manage applications. . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . .. . .. . . . . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . 62
6.4.1. Log in . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . . . . . . . . . .. . .. . . . .. . .. . .. . . . .. . .. . . . .. . .. . .. . . . .. . .. 70
6.4.2. Manage gateways . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . 71
6.4.3. Manage applications. . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . .. . .. . . . . . . .. . .. . .. . . . .. . .. . . . . . . .. . .. . . . .. . .. . 73
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.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

1. Introduction

The Smart Parking v2 solution developed by Libelium allows citizens to detect available parking slots.
Introduction
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

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
Network architecture
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 “
‚
The Smart Parking Cloud Service is a software service provided by Libelium which permits to receive,
Customer Server” chapter for further information.
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
Figure : Libelium Smart Parking Cloud Service scenario
Network architecture
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/Off switch: 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 (Off switch),
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
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
Smart Parking node

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 EUI and 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
Used to update the node parameters. After the customer sets up a new
Configuration downlink 3
RTC sync frame 6
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.
node configuration in the Remote Configuration Form a new "Configuration downlink" frame is enqueued into the LoRaWAN network server’s downlink queue.
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.
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
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" frames are sent sequentially during the execution of the program.

3.6.2. Frame header

The "Header" included in each uplink frame contains 2 bytes:
Byte Bit Field
0 7 Parking lot status
0 6 Battery state
0 5 Configuration uplink acknowledgement
0 4 Sensor recalibration
0 3-0 Frame type
1 7-0 Sequence number
The meaning of each field is:
‚
Parking slot status:
-
0: Free
-
1: Occupied
‚
Battery status:
-
0: OK
-
1: Warning. The battery level measured is below the warning threshold (3340 mV)
‚
Configuration uplink frame acknowledgement status:
-
0: ACK
-
1: NACK
‚
Sensor recalibration:
-
0: No calibration was done since the last uplink
-
1: At least one calibration was done since the last uplink
‚
Frame type: Number related to frame type
-
0: Info frame
-
1: Keep-alive frame
-
2: Configuration uplink frame
-
3: Configuration downlink
-
4: Start frame 1
-
5: Start frame 2
-
6: RTC sync frame
-
7: RTC update request
‚
Sequence number: This is a 1-byte field so the sequence number goes from 0 to 255. When 255 is reached, the counter starts from zero again.

3.6.3. Frame payload

The "Payload" contents vary depending on each frame type.
- 20 - v7.5
The Start frame 1 frame contents are:
‚
Header ("Parking slot status" does not provide valid data)
‚
Firmware version:
-
From 1 to 8: Not released firmware versions
-
9: v1.0.0
-
10: v1.0.1
-
11: v1.0.2
-
13: v1.0.4
-
14: v1.0.5
-
16: v1.0.6 (last stable version)
‚
Battery level
‚
Radar settings (threshold and range)
‚
LoRaWAN settings (join mode and ADR)
The Start frame 2 frame contents are:
‚
Header ("Parking slot status" does not provide valid data)
‚
Sleep and Keep-alive time settings
‚
Night-mode settings (enabled/disabled, start hour, duration, sleep time)
Smart Parking node
The Info frame contents are:
‚
Header
‚
Sensor error
‚
Temperature
‚
Timestamp (hour and minutes)
‚
Radar measurement (Distance, amplitude and number of reflections)
The Keep-alive frame contents are:
‚
Header
‚
Sensor error
‚
Temperature
‚
Timestamp (hour and minutes)
‚
Radar measurement (Distance, amplitude)
‚
Battery level
The RTC update request frame contents are the same as Keep-alive frame.
Important:
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 Server” section.
- 21 - v7.5
3.6.4. Node program flowchart
Smart Parking node
Figure : Smart Parking node program flowchart
- 22 - v7.5
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
Keep-alive time 0.5, 1, 2,..., 23 hour
Night-mode 0 or 1 Night-mode disabled/enabled
Night-mode start 0, 1,..., 23 hour Night-mode starts when RTC reaches this parameter field
Night-mode duration 1, 2,..., 15 hour Night-mode period is equal to this field
Night-mode sleep 1, 2,..., 10 min Sleep time applied during night-mode
Radar range start 20 to 50 cm
Radar range length 50 to 100 cm Range of measurement to be added to "range start" value
Radar threshold 5 to 100
LoRaWAN join mode 0 (ABP) or 1 (OTAA) Join mode used by the LoRaWAN radio module
LoRaWAN DevEUI 8-byte identifier Defines the device EUI used by the LoRaWAN radio
LoRaWAN DevAddr 4-byte identifier
LoRaWAN NwkSKey 16-byte key
LoRaWAN AppSKey 16-byte key
Hours elapsed since last uplink message which triggers a new Keep-alive frame
Starting measurement distance (objects below this value are not
detected)
Threshold used in detection algorithm, so higher threshold imply less sensitive detection
Defines the device address used by the LoRaWAN radio in ABP mode
Defines the LoRaWAN Network Session Key used by the LoRaWAN radio in ABP mode
Defines the LoRaWAN Application Session Key used by the LoRaWAN radio in ABP mode
LoRaWAN AppKey 16-byte key
LoRaWAN AppEUI 8-byte identifier
LoRaWAN port 1 to 223 Defines the port used for uplink sendings
LoRaWAN ADR 0 (off) or 1 (on) Defines if Adaptive Data Rate is enabled or disabled
LoRaWAN RX1 Delay 0 to 65536 Defines the delay after first LoRaWAN rx window
LoRaWAN Subband 8-bit bitmap
Important:
The LoRaWAN identifiers and keys must be registered in the LoRaWAN network server before starting the node in order to receive data. For OTAA mode: DevEUI, AppEUI and Appkey. For ABP mode: DevEUI, DevAddr, NwkSKey and AppSKey.
Defines the LoRaWAN Application Key used by the LoRaWAN radio in OTAA mode
Defines the LoRaWAN Application EUI used by the LoRaWAN radio in OTAA mode
Defines the sub-band used by the LoRaWAN radio (only applies to US and AU versions)
- 23 - v7.5
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.
If a change is detected from ’free’ to ’occupied’ or viceversa, then an "Info" frame is sent. If no change occurred during the last "Keep-alive" time, then a Keep-alive frame is sent. Besides, if a sensor error is detected, a Keep-alive frame sending is forced in order to inform about this issue.
Example parameters used:
‚
Sleep: 7 minutes
‚
Keep-alive: 1 hour
Figure : Example Info and Keep-alive frames

3.7.3. Understanding night-mode

As shown in the parameters table, there are some parameters that allow the user to configure the node to use 2 working modes depending on time settings: day-mode and night-mode.
The night-mode is a secondary and optional working mode that allows the user to configure a different time basis parameters in order to reduce the battery impact. So, it was developed to use it when the parking slot is expected to have fewer changes (i.e. at night). Therefore, a different night-mode "Sleep" setting is used.
It is not mandatory to use the night-mode during night. This mode is thought to be used when less vehicle movement is expected in the parking slots. Which could be during day time.
Example:
‚
Day-mode:
-
Sleep: 1 minute
‚
Night-mode:
-
Night-mode start hour: 21 hours (9 PM)
- 24 - v7.5
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. Keep-alive events are not shown but a Keep-alive event would be triggered if no change occurs in the parking slot.
Figure : Example of day and night mode
The conclusion is that the Night-mode is interesting for customers who certainly know the parking slot is expected to have fewer changes during large periods of time every day.
Note: From October 2019 the "keep-alive night-mode" setting was deprecated to simplify the parameter management. Since then, there is a single keep-alive setting, for both "normal mode" and "night mode".

3.7.4. Understanding RTC synchronization

There are specific frame types that allow the node to synchronize the RTC to the server timestamp.
The "Start Frame 1" expects an answer from the server with the timestamp (hours and minutes). This frame is sent after starting the node or a software reset.
Besides, the node’s firmware provides a mechanism which an "RTC update request" frame is sent every 24 hours since the node was started or reset. This frame waits for a downlink frame which brings the current server timestamp (hour and minutes).
- 25 - v7.5
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. The different columns display the parsed data from the received "uplink data".
Example:
‚
Day-mode:
-
Sleep: 1 minute
-
Keep-alive: 2 hour
‚
Night-mode:
-
Night-mode start hour: 22 hours (10 PM)
-
Night-mode duration: 8 hours (Night-mode goes from 10 PM to 6 AM)
-
Night-mode sleep time: 5 minutes
It is possible to distinguish the starting frames at the beginning of the execution. Then the node informs with a new Keep-alive every 2 hours. Any change of Parking slot status implies a new Info frame. And after 24 hours working, you can see the RTC request performed by the node.
Timestamp Uplink data F. Type Parking lot Battery Recal Seq
04/15/19 15:59 040009c419143c01000000 4 (Start 1) NULL 0 0 0
04/15/19 15:59 0501010000011608050200 5 (Start 2) NULL 0 0 1
04/15/19 15:59 110200170f3b00000000b0 1 (Keep-alive) 0 0 1 2
04/15/19 17:29 01030013101d00000000c8 1 (Keep-alive) 0 0 0 3
04/15/19 19:29 1104000d131d00000000d4 1 (Keep-alive) 0 0 1 4
04/15/19 21:29 0105000a151d00000000d4 1 (Keep-alive) 0 0 0 5
04/16/19 23:29 0106000a173b00000000d5 1 (Keep-alive) 0 0 0 6
04/16/19 01:29 01070009040000000000d4 1 (Keep-alive) 0 0 0 7
- 26 - v7.5
Smart Parking node
04/16/19 03:29 01080008060000000000d5 1 (Keep-alive) 0 0 0 8
04/16/19 05:29 01090008060000000000d5 1 (Keep-alive) 0 0 0 9
04/16/19 06:04 800a000906040172410005 0 (Info) 1 0 0 10
04/16/19 08:04 810b000a0804016d4268d4 1 (Keep-alive) 1 0 0 11
04/16/19 10:04 810c000b0a04017b3e00d4 1 (Keep-alive) 1 0 0 12
04/16/19 12:04 810d000c0c04016d3e58d4 1 (Keep-alive) 1 0 0 13
04/16/19 14:05 810e000e0e05016f3e80d4 1 (Keep-alive) 1 0 0 14
04/16/19 15:58 870f000f0f3b016b3dd0d4 7 (RTC request) 1 0 0 15
04/16/19 15:59 8710000f0f3b016b3dd0d4 7 (RTC request) 1 0 0 16
04/16/19 17:59 8111000f101c016e3c98c7 1 (Keep-alive) 1 0 0 17
04/16/19 18:32 002a000f101f0000000000 0 (Info) 0 0 0 18
04/16/19 20:02 012b0010110100000000c7 1 (Keep-alive) 0 0 0 19
04/16/19 22:32 012c0011111f00000000c8 1 (Keep-alive) 0 0 0 20
04/17/19 00:02 012d0010120100000000c7 1 (Keep-alive) 0 0 0 21

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)
Night-mode start 0 hour
Night-mode duration 6 hour
Night-mode sleep 5 min
Radar range start 20 cm (should not be changed)
Radar range length 60 cm (should not be changed)
Radar threshold 25 (should not be changed)
LoRaWAN join mode 1 (OTAA)
LoRaWAN DevEUI unique factory default value
LoRaWAN DevAddr unique factory default value
LoRaWAN NwkSKey unique factory default value
LoRaWAN AppSKey unique factory default value
LoRaWAN AppKey unique factory default value
LoRaWAN AppEUI unique factory default value
LoRaWAN port 3
LoRaWAN ADR 0 (off)
- 27 - v7.5
Smart Parking node
LoRaWAN RX1 Delay 1000 (should not be changed)
LoRaWAN Subband 8-bit bitmap
3.7.7. Configure new parameter values
The Smart Devices App and the Remote Configuration Form allow the user to configure new parameters to the node. 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.
Regarding the time and sensor parameters, the same values are set to all nodes manufactured by Libelium. The default values can be seen in the previous section. However, the customer can configure the time and sensor settings using both Smart Devices App and Remote Configuration Form.
Regarding the LoRaWAN parameters, all keys are randomly generated for each node and kept secret. The DevEUI set to the node is the LoRaWAN hardcoded EUI which is unique for each radio chipset. However, the client can configure/modify all LoRaWAN parameters using the Smart Devices App only (the Remote Configuration Form does not permit it).
Note: For further information about this matter please refer to the “
Remote Configuration Form” sections.
“
Smart Devices App” and
- 28 - v7.5
Libelium Cloud management

4. Libelium Cloud management

4.1. Introduction to the Libelium Services Cloud Manager ­SCM
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.
Figure : Smart Parking network architecture
- 29 - v7.5
Loading...
+ 125 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use