Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 14 removed)
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- 1657520100595-569.png
- image-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
- image-20221009001045-1.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N95S31B --NB-IoT Temperature & Humidity Sensor User Manual1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual - Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -19,31 +19,27 @@ 19 19 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 - 23 23 ((( 22 + 23 + 24 24 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 25 -))) 26 26 27 -((( 28 28 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 29 -))) 30 30 31 -((( 32 32 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 33 -))) 34 34 35 -((( 36 36 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 37 -))) 38 38 39 - (((32 + 40 40 ~* make sure you have NB-IoT coverage locally. 34 + 35 + 41 41 ))) 42 42 43 - 44 44 [[image:1657348284168-431.png]] 45 45 46 46 41 + 47 47 == 1.2 Features == 48 48 49 49 ... ... @@ -59,6 +59,7 @@ 59 59 * 8500mAh Battery for long term use 60 60 61 61 57 + 62 62 == 1.3 Specification == 63 63 64 64 ... ... @@ -69,15 +69,16 @@ 69 69 70 70 (% style="color:#037691" %)**NB-IoT Spec:** 71 71 72 -* B1 @H-FDD: 2100MHz 73 -* B3 @H-FDD: 1800MHz 74 -* B8 @H-FDD: 900MHz 75 -* B5 @H-FDD: 850MHz 76 -* B20 @H-FDD: 800MHz 77 -* B28 @H-FDD: 700MHz 68 +* - B1 @H-FDD: 2100MHz 69 +* - B3 @H-FDD: 1800MHz 70 +* - B8 @H-FDD: 900MHz 71 +* - B5 @H-FDD: 850MHz 72 +* - B20 @H-FDD: 800MHz 73 +* - B28 @H-FDD: 700MHz 78 78 79 79 (% style="color:#037691" %)**Battery:** 80 80 77 + 81 81 * Li/SOCI2 un-chargeable battery 82 82 * Capacity: 8500mAh 83 83 * Self Discharge: <1% / Year @ 25°C ... ... @@ -85,9 +85,9 @@ 85 85 * Max boost current: 2A, 1 second 86 86 87 87 85 + 88 88 == 1.4 Applications == 89 89 90 - 91 91 * Smart Buildings & Home Automation 92 92 * Logistics and Supply Chain Management 93 93 * Smart Metering ... ... @@ -99,49 +99,43 @@ 99 99 100 100 101 101 102 -== 1.5 Pin Definitions & Switch==99 +== 1.5 Pin Definitions == 103 103 104 - 105 105 N95S31B use the mother board from NBSN95 which as below. 106 106 107 - 108 108 [[image:image-20220709144723-1.png]] 109 109 110 110 111 111 === 1.5.1 Jumper JP2 === 112 112 113 - 114 114 Power on Device when put this jumper. 115 115 116 116 111 + 117 117 === 1.5.2 BOOT MODE / SW1 === 118 118 114 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 119 119 120 -((( 121 -**1) ISP: ** upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 122 -))) 116 +2) Flash: work mode, device starts to work and send out console output for further debug 123 123 124 -((( 125 -**2) Flash:** work mode, device starts to work and send out console output for further debug 126 -))) 127 127 128 128 129 129 === 1.5.3 Reset Button === 130 130 131 - 132 132 Press to reboot the device. 133 133 134 134 125 + 135 135 === 1.5.4 LED === 136 136 137 - 138 138 It will flash: 139 139 140 -1. When boot the device in flash mode 130 +1. When boot the device in flash mode 131 +1. Send an uplink packet 141 141 142 -2. Send an uplink packet 143 143 144 144 135 + 145 145 = 2. Use N95S31B to communicate with IoT Server = 146 146 147 147 == 2.1 How it works == ... ... @@ -160,14 +160,16 @@ 160 160 161 161 ))) 162 162 163 -[[image:16575 20100595-569.png]]154 +[[image:1657350248151-650.png]] 164 164 165 165 ((( 166 166 167 167 ))) 168 168 160 + 169 169 == 2.2 Configure the N95S31B == 170 170 163 + 171 171 === 2.2.1 Power On N95S31B === 172 172 173 173 ... ... @@ -174,48 +174,27 @@ 174 174 [[image:image-20220709150546-2.png]] 175 175 176 176 177 -=== 2.2. 2Test Requirement ===170 +=== 2.2.1 Test Requirement === 178 178 179 179 180 -((( 181 181 To use N95S31B in your city, make sure meet below requirements: 182 -))) 183 183 184 -* ((( 185 -Your local operator has already distributed a NB-IoT Network there. 186 -))) 187 -* ((( 188 -The local NB-IoT network used the band that N95S31B supports. 189 -))) 190 -* ((( 191 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 192 -))) 175 +* Your local operator has already distributed a NB-IoT Network there. 176 +* The local NB-IoT network used the band that N95S31B supports. 177 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 193 193 194 - (((179 + 195 195 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 196 -))) 197 197 198 -((( 199 199 N95S31B supports different communication protocol such as : 200 -))) 201 201 202 202 ((( 203 -* ((( 204 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 205 -))) 206 -* ((( 207 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 208 -))) 209 -* ((( 210 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 211 -))) 212 -* ((( 213 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 214 -))) 185 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 215 215 216 -((( 217 217 We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 218 -))) 219 219 220 220 221 221 ))) ... ... @@ -223,9 +223,9 @@ 223 223 [[image:1657350625843-586.png]] 224 224 225 225 198 + 226 226 === 2.2.3 Insert SIM card === 227 227 228 - 229 229 ((( 230 230 Insert the NB-IoT Card get from your provider. 231 231 ))) ... ... @@ -238,29 +238,26 @@ 238 238 [[image:1657351240556-536.png]] 239 239 240 240 241 -=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 242 242 214 +=== 2.2.3 Connect USB – TTL to N95S31B to configure it === 243 243 244 244 ((( 245 245 ((( 246 246 User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 247 - 248 - 249 249 ))) 250 250 ))) 251 251 252 252 [[image:1657351312545-300.png]] 253 253 224 +**Connection:** 254 254 255 -(% style="color: blue" %)**Connection:**226 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 256 256 257 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**228 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 258 258 259 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**230 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 260 260 261 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 262 262 263 - 264 264 In the PC, use below serial tool settings: 265 265 266 266 * Baud: (% style="color:green" %)**9600** ... ... @@ -275,16 +275,15 @@ 275 275 276 276 [[image:1657329814315-101.png]] 277 277 278 - 279 279 ((( 280 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**248 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 281 281 ))) 282 282 283 283 284 -=== 2.2.5 Use CoAP protocol to uplink data === 285 285 253 +=== 2.2.4 Use CoAP protocol to uplink data === 286 286 287 -(% style="color:red" %) **Note: if you don't have CoAP server, you can refer this link to set up one:**(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**255 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 288 288 289 289 290 290 ((( ... ... @@ -295,19 +295,17 @@ 295 295 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 296 296 ))) 297 297 * ((( 298 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 266 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 299 299 ))) 300 300 * ((( 301 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 269 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 302 302 ))) 303 303 304 304 ((( 305 - 306 - 307 307 For parameter description, please refer to AT command set 308 308 ))) 309 309 310 -[[image:1657352 146020-183.png]]276 +[[image:1657330452568-615.png]] 311 311 312 312 313 313 ((( ... ... @@ -314,66 +314,61 @@ 314 314 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 315 315 ))) 316 316 317 -[[image:16573 52185396-303.png]]283 +[[image:1657330472797-498.png]] 318 318 319 319 320 -=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 321 321 287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 322 322 289 + 323 323 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 324 324 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 325 325 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 326 326 327 -[[image:16573 52391268-297.png]]294 +[[image:1657330501006-241.png]] 328 328 329 329 330 -[[image:16573 52403317-397.png]]297 +[[image:1657330533775-472.png]] 331 331 332 332 333 -=== 2.2.7 Use MQTT protocol to uplink data === 334 334 301 +=== 2.2.6 Use MQTT protocol to uplink data === 335 335 336 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 337 337 338 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 339 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 340 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 341 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 342 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 343 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527344 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)304 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 305 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 306 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 307 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 308 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 345 345 346 -[[image:1657 352634421-276.png]]312 +[[image:1657249978444-674.png]] 347 347 348 348 349 -[[image:16573 52645687-385.png]]315 +[[image:1657330723006-866.png]] 350 350 351 351 352 352 ((( 353 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.319 +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. 354 354 ))) 355 355 356 -((( 357 -MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 358 -))) 359 359 360 360 361 -=== 2.2. 8Use TCP protocol to uplink data ===324 +=== 2.2.7 Use TCP protocol to uplink data === 362 362 363 363 364 -This feature is supported since firmware version v110 365 - 366 366 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 367 367 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 368 368 369 -[[image: 1657352898400-901.png]]330 +[[image:image-20220709093918-1.png]] 370 370 371 371 372 -[[image: 1657352914475-252.png]]333 +[[image:image-20220709093918-2.png]] 373 373 374 374 375 -=== 2.2.9 Change Update Interval === 376 376 337 +=== 2.2.8 Change Update Interval === 377 377 378 378 User can use below command to change the (% style="color:green" %)**uplink interval**. 379 379 ... ... @@ -380,241 +380,164 @@ 380 380 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 381 381 382 382 ((( 383 - 344 +(% style="color:red" %)**NOTE:** 384 384 ))) 385 385 386 386 ((( 387 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 388 388 ))) 389 389 390 -((( 391 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 392 -))) 393 393 394 394 395 395 == 2.3 Uplink Payload == 396 396 355 +In this mode, uplink payload includes in total 14 bytes 397 397 398 -((( 399 -N95S31B has different working modes for the connections of different types of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 400 -))) 401 401 358 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 359 +|=(% style="width: 60px;" %)((( 360 +**Size(bytes)** 361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 362 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 402 402 403 403 ((( 404 - For example:365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 405 405 ))) 406 406 407 -((( 408 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/ will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 409 -))) 410 410 369 +[[image:1657331036973-987.png]] 411 411 412 412 ((( 413 -The uplink payloadsare composedinASCIIString.Forxample:372 +The payload is ASCII string, representative same HEX: 414 414 ))) 415 415 416 416 ((( 417 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:376 +0x72403155615900640c6c19029200 where: 418 418 ))) 419 419 420 -((( 421 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes379 +* ((( 380 +Device ID: 0x724031556159 = 724031556159 422 422 ))) 423 - 424 - 425 -((( 426 -(% style="color:red" %)**NOTE:** 382 +* ((( 383 +Version: 0x0064=100=1.0.0 427 427 ))) 428 428 429 -(% style="color:red" %) 430 -1. ((( 431 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 386 +* ((( 387 +BAT: 0x0c6c = 3180 mV = 3.180V 432 432 ))) 433 -1. ((( 434 -**By default, the device will send an uplink message every 1 hour.** 389 +* ((( 390 +Signal: 0x19 = 25 391 +))) 392 +* ((( 393 +Distance: 0x0292= 658 mm 394 +))) 395 +* ((( 396 +Interrupt: 0x00 = 0 435 435 436 436 399 + 437 437 438 438 ))) 439 439 440 -== =2.3.1PayloadAnalyze ===403 +== 2.4 Payload Explanation and Sensor Interface == 441 441 442 -==== 2.3.1.1 Before Firmware v1.2 ==== 443 443 406 +=== 2.4.1 Device ID === 444 444 445 -N95S31B uplink payload includes in total 21 bytes. 446 - 447 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 448 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2** 449 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 450 450 ((( 451 - Reserve/Same asNBSN95CFGMOD=1409 +By default, the Device ID equal to the last 6 bytes of IMEI. 452 452 ))) 453 453 454 454 ((( 455 - Nofunctionhere.413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 456 456 ))) 457 -)))|(% style="width:102px" %)((( 458 -((( 459 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 460 -))) 461 461 462 462 ((( 463 - By SHT31417 +**Example:** 464 464 ))) 465 -)))|(% style="width:81px" %)((( 466 -((( 467 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 468 -))) 469 469 470 470 ((( 471 - By SHT31421 +AT+DEUI=A84041F15612 472 472 ))) 473 -))) 474 474 475 475 ((( 476 - 477 - 478 -((( 479 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 480 480 ))) 481 -))) 482 482 483 483 484 -[[image:1657354294009-643.png]] 485 485 430 +=== 2.4.2 Version Info === 486 486 487 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 432 +((( 433 +Specify the software version: 0x64=100, means firmware version 1.00. 434 +))) 488 488 489 -**where:** 436 +((( 437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 438 +))) 490 490 491 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 492 492 493 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 494 494 495 - *(%style="color:#037691"%)**BAT:**(%%) 0x0ccd=3277 mV=3.277V442 +=== 2.4.3 Battery Info === 496 496 497 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 498 - 499 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 500 - 501 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 502 - 503 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 504 - 505 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 506 - 507 507 ((( 508 - 445 +Ex1: 0x0B45 = 2885mV 446 +))) 509 509 510 - 448 +((( 449 +Ex2: 0x0B49 = 2889mV 511 511 ))) 512 512 513 -==== 2.3.1.2 Since Firmware v1.2 ==== 514 514 515 515 516 - Inthismode, uplink payloadincludes 91 bytes inotalby default.454 +=== 2.4.4 Signal Strength === 517 517 518 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 519 - 520 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 521 -|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**4** 522 -|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 523 - 524 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 525 - 526 - 527 -[[image:image-20220908154949-1.png]] 528 - 529 - 530 -The payload is ASCII string, representative same HEX: 531 - 532 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ ** 533 - 534 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 535 - 536 -**where:** 537 - 538 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 539 - 540 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 541 - 542 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 543 - 544 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 545 - 546 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 547 - 548 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 549 - 550 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 551 - 552 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 553 - 554 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 555 - 556 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 557 - 558 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 559 - 560 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 561 - 562 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 563 - 564 - 565 -=== 2.3.2 Device ID === 566 - 567 - 568 568 ((( 569 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.457 +NB-IoT Network signal Strength. 570 570 ))) 571 571 572 572 ((( 573 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 461 +**Ex1: 0x1d = 29** 462 +))) 574 574 575 - 464 +((( 465 +(% style="color:blue" %)**0**(%%) -113dBm or less 576 576 ))) 577 577 578 578 ((( 579 -(% style="color:blue" %)** Example:**469 +(% style="color:blue" %)**1**(%%) -111dBm 580 580 ))) 581 581 582 582 ((( 583 - AT+DEUI=A84041F15612473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 584 584 ))) 585 585 586 586 ((( 587 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 477 +(% style="color:blue" %)**31** (%%) -51dBm or greater 478 +))) 588 588 589 - 480 +((( 481 +(% style="color:blue" %)**99** (%%) Not known or not detectable 590 590 ))) 591 591 592 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 593 593 594 594 595 - Bydefault,theDeviceID equal to the last 15 bits of IMEI.486 +=== 2.4.5 Distance === 596 596 597 - Usercan use**(%style="color:blue"%)AT+DEUI(%%)**tosetDeviceID488 +Get the distance. Flat object range 280mm - 7500mm. 598 598 599 - 600 -(% style="color:blue" %)**Example:** 601 - 602 -AT+DEUI=868411056754138 603 - 604 - 605 -=== 2.3.3 Version Info === 606 - 607 - 608 608 ((( 609 - Thesebytes include the hardware andsoftwareversion.491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 610 610 ))) 611 611 612 612 ((( 613 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B 495 +((( 496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 614 614 ))) 498 +))) 615 615 616 616 ((( 617 - **Lowerbyte:** Specify the software version: 0x6E=110, means firmware version 110501 + 618 618 ))) 619 619 620 620 ((( ... ... @@ -621,87 +621,68 @@ 621 621 622 622 ))) 623 623 508 +=== 2.4.6 Digital Interrupt === 509 + 624 624 ((( 625 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.511 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 626 626 ))) 627 627 628 628 ((( 629 - 515 +The command is: 630 630 ))) 631 631 632 -=== 2.3.4 Battery Info === 633 - 634 - 635 635 ((( 636 - Ex1:0x0B45=2885mV519 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 637 637 ))) 638 638 522 + 639 639 ((( 640 - Ex2:0x0B49=2889mV524 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 641 641 ))) 642 642 643 643 644 -=== 2.3.5 Signal Strength === 645 - 646 - 647 647 ((( 648 - NB-IoT Network signalStrength.529 +Example: 649 649 ))) 650 650 651 651 ((( 652 - **Ex1:0x1d=29**533 +0x(00): Normal uplink packet. 653 653 ))) 654 654 655 655 ((( 656 -( %style="color:blue"%)**0**(%%) -113dBm orless537 +0x(01): Interrupt Uplink Packet. 657 657 ))) 658 658 540 + 541 + 542 +=== 2.4.7 +5V Output === 543 + 659 659 ((( 660 - (%style="color:blue"%)**1**(%%)-111dBm545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 661 661 ))) 662 662 548 + 663 663 ((( 664 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm550 +The 5V output time can be controlled by AT Command. 665 665 ))) 666 666 667 667 ((( 668 -(% style="color:blue" %)** 31**(%%) -51dBm or greater554 +(% style="color:blue" %)**AT+5VT=1000** 669 669 ))) 670 670 671 671 ((( 672 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 673 673 ))) 674 674 675 675 676 -=== 2.3.6 Temperature & Humidity === 677 677 563 +== 2.5 Downlink Payload == 678 678 679 - Thedevice will beabletoget theSHT31temperature and humiditydatanowandupload toIoT Server.565 +By default, NDDS75 prints the downlink payload to console port. 680 680 681 -[[image:image-202207091 61741-3.png]]567 +[[image:image-20220709100028-1.png]] 682 682 683 683 684 -Convert the read byte to decimal and divide it by ten. 685 - 686 - 687 -**Example:** 688 - 689 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 690 - 691 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 692 - 693 - 694 -== 2.4 Downlink Payload == 695 - 696 - 697 -By default, N95S31B prints the downlink payload to console port. 698 - 699 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 700 -|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)** 701 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4 702 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2 703 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4 704 - 705 705 ((( 706 706 (% style="color:blue" %)**Examples:** 707 707 ))) ... ... @@ -735,7 +735,7 @@ 735 735 ))) 736 736 737 737 ((( 738 -If payload = 0x04FF, it will reset the 95S31B603 +If payload = 0x04FF, it will reset the NDDS75 739 739 ))) 740 740 741 741 ... ... @@ -746,97 +746,144 @@ 746 746 ))) 747 747 748 748 749 -== 2.5 Humidity and Temperature alarm function == 750 750 615 +== 2.6 LED Indicator == 751 751 752 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 753 753 618 +The NDDS75 has an internal LED which is to show the status of different state. 754 754 755 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 756 756 621 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 622 +* Then the LED will be on for 1 second means device is boot normally. 623 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 624 +* For each uplink probe, LED will be on for 500ms. 757 757 758 -² When min=0, and max≠0, Alarm higher than max 626 +((( 627 + 628 +))) 759 759 760 -² When min≠0, and max=0, Alarm lower than min 761 761 762 -² When min≠0 and max≠0, Alarm higher than max or lower than min 763 763 632 +== 2.7 Firmware Change Log == 764 764 765 - (% style="color:blue" %)**Example:** 766 766 767 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 635 +((( 636 +Download URL & Firmware Change log 637 +))) 768 768 639 +((( 640 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 641 +))) 769 769 770 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 771 771 772 -² When min=0, and max≠0, Alarm higher than max 644 +((( 645 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 646 +))) 773 773 774 -² When min≠0, and max=0, Alarm lower than min 775 775 776 -² When min≠0 and max≠0, Alarm higher than max or lower than min 777 777 650 +== 2.8 Battery Analysis == 778 778 779 - **~(%style="color:blue"%)Example:(%%)**652 +=== 2.8.1 Battery Type === 780 780 781 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 782 782 655 +((( 656 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 657 +))) 783 783 784 -== 2.6 Set the number of data to be uploaded and the recording time == 659 +((( 660 +The battery is designed to last for several years depends on the actually use environment and update interval. 661 +))) 785 785 663 +((( 664 +The battery related documents as below: 665 +))) 786 786 787 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 667 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 668 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 669 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 788 788 789 -* (% style="color:#037691" %)**AT+TR=900** (%%)~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 790 -* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 671 +((( 672 +[[image:image-20220709101450-2.png]] 673 +))) 791 791 792 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 793 793 794 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 795 795 677 +=== 2.8.2 Power consumption Analyze === 796 796 797 -== 2.7 Read or Clear cached data == 679 +((( 680 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 681 +))) 798 798 799 799 800 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 684 +((( 685 +Instruction to use as below: 686 +))) 801 801 802 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 803 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 688 +((( 689 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 690 +))) 804 804 805 -[[image:image-20220908163102-2.png]] 806 806 693 +((( 694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 695 +))) 807 807 808 -== 2.8 Battery & Power Consumption == 697 +* ((( 698 +Product Model 699 +))) 700 +* ((( 701 +Uplink Interval 702 +))) 703 +* ((( 704 +Working Mode 705 +))) 809 809 707 +((( 708 +And the Life expectation in difference case will be shown on the right. 709 +))) 810 810 811 - N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about thebatteryinfoand how to replace.711 +[[image:image-20220709110451-3.png]] 812 812 813 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 814 814 815 815 816 -= 3. AccessNB-IoT Module =715 +=== 2.8.3 Battery Note === 817 817 717 +((( 718 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased. 719 +))) 818 818 721 + 722 + 723 +=== 2.8.4 Replace the battery === 724 + 819 819 ((( 726 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 727 +))) 728 + 729 + 730 + 731 += 3. Access NB-IoT Module = 732 + 733 +((( 820 820 Users can directly access the AT command set of the NB-IoT module. 821 821 ))) 822 822 823 823 ((( 824 824 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 825 - 826 - 827 827 ))) 828 828 829 829 [[image:1657333200519-600.png]] 830 830 831 831 744 + 832 832 = 4. Using the AT Commands = 833 833 834 834 == 4.1 Access AT Commands == 835 835 749 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 836 836 837 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 838 838 839 - 840 840 AT+<CMD>? : Help on <CMD> 841 841 842 842 AT+<CMD> : Run <CMD> ... ... @@ -876,24 +876,7 @@ 876 876 877 877 AT+SERVADDR : Server Address 878 878 879 -AT+TR : Get or Set record time 880 880 881 -AT+APN : Get or set the APN 882 - 883 -AT+FBAND : Get or Set whether to automatically modify the frequency band 884 - 885 -AT+DNSCFG : Get or Set DNS Server 886 - 887 -AT+GETSENSORVALUE : Returns the current sensor measurement 888 - 889 -AT+NOUD : Get or Set the number of data to be uploaded 890 - 891 -AT+CDP : Read or Clear cached data 892 - 893 -AT+SHTEMP: Get or Set alarm of temp 894 - 895 -AT+SHHUM: Get or Set alarm of moisture 896 - 897 897 (% style="color:#037691" %)**COAP Management** 898 898 899 899 AT+URI : Resource parameters ... ... @@ -924,6 +924,7 @@ 924 924 AT+PWORD : Serial Access Password 925 925 926 926 822 + 927 927 = 5. FAQ = 928 928 929 929 == 5.1 How to Upgrade Firmware == ... ... @@ -938,12 +938,11 @@ 938 938 ))) 939 939 940 940 ((( 941 -Firmware Download:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]] 942 - 943 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 944 944 ))) 945 945 946 946 841 + 947 947 = 6. Trouble Shooting = 948 948 949 949 == 6.1 Connection problem when uploading firmware == ... ... @@ -953,10 +953,14 @@ 953 953 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 954 954 ))) 955 955 851 +(% class="wikigeneratedid" %) 852 +((( 853 + 854 +))) 956 956 856 + 957 957 == 6.2 AT Command input doesn't work == 958 958 959 - 960 960 ((( 961 961 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 962 962 ... ... @@ -963,18 +963,18 @@ 963 963 964 964 ))) 965 965 966 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 967 967 968 - 969 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 970 - 971 - 972 972 = 7. Order Info = 973 973 974 974 975 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 976 976 977 977 872 +(% class="wikigeneratedid" %) 873 +((( 874 + 875 +))) 876 + 978 978 = 8. Packing Info = 979 979 980 980 ((( ... ... @@ -982,7 +982,7 @@ 982 982 983 983 (% style="color:#037691" %)**Package Includes**: 984 984 985 -* N 95S31BNB-IoTTemperatureandHumiditySensor884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 986 986 * External antenna x 1 987 987 ))) 988 988 ... ... @@ -991,19 +991,21 @@ 991 991 992 992 (% style="color:#037691" %)**Dimension and weight**: 993 993 893 + 994 994 * Device Size: 13.0 x 5 x 4.5 cm 995 995 * Device Weight: 150g 996 -* Package Size / pcs : 1 4.0x8x 5 cm997 -* Weight / pcs : 180g896 +* Package Size / pcs : 15 x 12x 5.5 cm 897 +* Weight / pcs : 220g 998 998 ))) 999 999 900 +((( 901 + 1000 1000 1001 1001 904 + 905 +))) 906 + 1002 1002 = 9. Support = 1003 1003 1004 - 1005 1005 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1006 - 1007 1007 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 1008 - 1009 -
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content