Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -124,173 +124,52 @@ 124 124 125 125 126 126 127 -== 2.2 Configure the NSE01==127 +== 2.2 Quick guide to connect to LoRaWAN server (OTAA) == 128 128 129 - ===2.2.1TestRequirement===129 +Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example. 130 130 131 131 132 - To use NSE01in your city,makesure meet below requirements:132 +[[image:1654503992078-669.png]] 133 133 134 -* Your local operator has already distributed a NB-IoT Network there. 135 -* The local NB-IoT network used the band that NSE01 supports. 136 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 137 137 135 +The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server. 138 138 139 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 140 140 138 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSE01. 141 141 142 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.gif]]140 +Each LSE01 is shipped with a sticker with the default device EUI as below: 143 143 142 +[[image:image-20220606163732-6.jpeg]] 144 144 144 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: 145 145 146 - ===2.2.2sertSIMcard ===146 +**Add APP EUI in the application** 147 147 148 -Insert the NB-IoT Card get from your provider. 149 149 149 +[[image:1654504596150-405.png]] 150 150 151 -User need to take out the NB-IoT module and insert the SIM card like below: 152 152 153 153 154 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]153 +**Add APP KEY and DEV EUI** 155 155 155 +[[image:1654504683289-357.png]] 156 156 157 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 158 158 159 159 160 - User need to configure NSE01 via serial port to set the **(% style="color:blue" %)Server Address**/ **UplinkTopic**todefine where and how-to uplink packets. NSE01 supportAT Commands,user can use a USB to TTLadapter to connect to NSE01and use AT Commands to configure it, as below.159 +(% style="color:blue" %)**Step 2**(%%): Power on LSE01 161 161 162 162 162 +Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position). 163 163 164 +[[image:image-20220606163915-7.png]] 164 164 165 -Connection: 166 166 167 - background-color:yellow" %)USBTTLGND<~-~-~-~->GND167 +(% style="color:blue" %)**Step 3**(%%)**:** The LSE01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel. 168 168 169 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD169 +[[image:1654504778294-788.png]] 170 170 171 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 172 172 173 173 174 - 175 -In the PC, use below serial tool settings: 176 - 177 -* Baud: ** (% style="background-color:green" %)9600**(%%) 178 -* Data bits:** (% style="background-color:green" %)8**(%%) 179 -* Stop bits: **(% style="background-color:green" %)1**(%%) 180 -* Parity: **(% style="background-color:green" %)None**(%%) 181 -* Flow Control: **(% style="background-color:green" %)None** 182 - 183 - 184 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the **(% style="background-color:green" %)password: 12345678**(%%) to access AT Command input. 185 - 186 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]] 187 - 188 -Note: the valid AT Commands can be found at: 189 - 190 -[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 191 - 192 - 193 - 194 -=== 2.2.4 Use CoAP protocol to uplink data === 195 - 196 - 197 -(% style="background-color:red" %)Note: if you don’t have CoAP server, you can refer this link to set up one: 198 - 199 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]] 200 - 201 - 202 -Use below commands: 203 - 204 -* **(% style="color:blue" %)AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 205 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 206 -* **(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 207 - 208 - 209 -For parameter description, please refer to AT command set 210 - 211 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]] 212 - 213 - 214 -After configure the server address and **(% style="color:green" %)reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server. 215 - 216 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]] 217 - 218 - 219 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 220 - 221 - 222 -This feature is supported since firmware version v1.0.1 223 - 224 - 225 -* **(% style="color:blue" %)AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 226 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 227 -* **(% style="color:blue" %)AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 228 - 229 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]] 230 - 231 - 232 - 233 - 234 - 235 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]] 236 - 237 - 238 -=== 2.2.6 Use MQTT protocol to uplink data === 239 - 240 - 241 -This feature is supported since firmware version v110 242 - 243 - 244 -* **(% style="color:blue" %)AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 245 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 246 -* **(% style="color:blue" %)AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 247 -* **(% style="color:blue" %)AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 248 -* **(% style="color:blue" %)AT+PWD=PWD **(%%)~/~/Set the password of MQTT 249 -* **(% style="color:blue" %)AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 250 -* **(% style="color:blue" %)AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 251 - 252 - 253 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]] 254 - 255 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]] 256 - 257 - 258 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 259 - 260 - 261 -=== 2.2.7 Use TCP protocol to uplink data === 262 - 263 - 264 -This feature is supported since firmware version v110 265 - 266 - 267 -* **(% style="color:blue" %)AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 268 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 269 - 270 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]] 271 - 272 - 273 - 274 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]] 275 - 276 - 277 -=== 2.2.8 Change Update Interval === 278 - 279 -User can use below command to change the **(% style="color:green" %)uplink interval**. 280 - 281 -**~ (% style="color:blue" %)AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 282 - 283 - 284 -**(% style="color:red" %)NOTE:** 285 - 286 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 287 - 288 - 289 - 290 - 291 - 292 - 293 - 294 294 == 2.3 Uplink Payload == 295 295 296 296