Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "image-20220908154949-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 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*. 28 +))) 25 25 30 +((( 26 26 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. 32 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 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). 40 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,6 +41,7 @@ 41 41 42 42 == 1.2 Features == 43 43 59 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 45 45 * Monitor Temperature & Humidity via SHT31 46 46 * AT Commands to change parameters ... ... @@ -63,6 +63,8 @@ 63 63 * Supply Voltage: 2.1v ~~ 3.6v 64 64 * Operating Temperature: -40 ~~ 85°C 65 65 82 + 83 + 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,9 +72,10 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 75 -(% style="color:#037691" %)**Battery:** 76 76 77 77 95 +(% style="color:#037691" %)**Battery:** 96 + 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -86,6 +86,7 @@ 86 86 87 87 == 1.4 Applications == 88 88 108 + 89 89 * Smart Buildings & Home Automation 90 90 * Logistics and Supply Chain Management 91 91 * Smart Metering ... ... @@ -97,15 +97,20 @@ 97 97 98 98 99 99 100 -== 1.5 Pin Definitions == 101 101 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 102 102 N95S31B use the mother board from NBSN95 which as below. 103 103 126 + 104 104 [[image:image-20220709144723-1.png]] 105 105 106 106 130 + 107 107 === 1.5.1 Jumper JP2 === 108 108 133 + 109 109 Power on Device when put this jumper. 110 110 111 111 ... ... @@ -112,14 +112,20 @@ 112 112 113 113 === 1.5.2 BOOT MODE / SW1 === 114 114 140 + 141 +((( 115 115 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. 143 +))) 116 116 145 +((( 117 117 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 118 118 119 119 120 120 121 121 === 1.5.3 Reset Button === 122 122 153 + 123 123 Press to reboot the device. 124 124 125 125 ... ... @@ -126,6 +126,7 @@ 126 126 127 127 === 1.5.4 LED === 128 128 160 + 129 129 It will flash: 130 130 131 131 1. When boot the device in flash mode ... ... @@ -132,8 +132,11 @@ 132 132 1. Send an uplink packet 133 133 134 134 167 + 168 + 135 135 = 2. Use N95S31B to communicate with IoT Server = 136 136 171 + 137 137 == 2.1 How it works == 138 138 139 139 ... ... @@ -150,7 +150,7 @@ 150 150 151 151 ))) 152 152 153 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 154 154 155 155 ((( 156 156 ... ... @@ -166,26 +166,49 @@ 166 166 [[image:image-20220709150546-2.png]] 167 167 168 168 204 + 169 169 === 2.2.1 Test Requirement === 170 170 171 171 208 +((( 172 172 To use N95S31B in your city, make sure meet below requirements: 210 +))) 173 173 174 -* Your local operator has already distributed a NB-IoT Network there. 175 -* The local NB-IoT network used the band that N95S31B supports. 176 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 212 +* ((( 213 +Your local operator has already distributed a NB-IoT Network there. 214 +))) 215 +* ((( 216 +The local NB-IoT network used the band that N95S31B supports. 217 +))) 218 +* ((( 219 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 +))) 177 177 222 +((( 178 178 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 179 179 226 +((( 180 180 N95S31B supports different communication protocol such as : 228 +))) 181 181 182 182 ((( 183 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 231 +* ((( 232 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 +))) 234 +* ((( 235 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 +))) 237 +* ((( 238 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 +))) 240 +* ((( 241 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 +))) 187 187 244 +((( 188 188 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. 246 +))) 189 189 190 190 191 191 ))) ... ... @@ -196,6 +196,7 @@ 196 196 197 197 === 2.2.3 Insert SIM card === 198 198 257 + 199 199 ((( 200 200 Insert the NB-IoT Card get from your provider. 201 201 ))) ... ... @@ -211,14 +211,18 @@ 211 211 212 212 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 213 213 273 + 214 214 ((( 215 215 ((( 216 216 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. 277 + 278 + 217 217 ))) 218 218 ))) 219 219 220 220 [[image:1657351312545-300.png]] 221 221 284 + 222 222 **Connection:** 223 223 224 224 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -242,8 +242,9 @@ 242 242 243 243 [[image:1657329814315-101.png]] 244 244 308 + 245 245 ((( 246 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]310 +(% 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]]** 247 247 ))) 248 248 249 249 ... ... @@ -250,9 +250,10 @@ 250 250 251 251 === 2.2.5 Use CoAP protocol to uplink data === 252 252 253 -(% 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/]] 254 254 318 +(% 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 255 320 + 256 256 ((( 257 257 **Use below commands:** 258 258 ))) ... ... @@ -291,6 +291,8 @@ 291 291 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 292 292 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 293 293 359 + 360 + 294 294 [[image:1657352391268-297.png]] 295 295 296 296 ... ... @@ -300,6 +300,7 @@ 300 300 301 301 === 2.2.7 Use MQTT protocol to uplink data === 302 302 370 + 303 303 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 304 304 305 305 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -310,11 +310,14 @@ 310 310 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 311 311 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 312 312 381 + 382 + 313 313 [[image:1657352634421-276.png]] 314 314 315 315 316 316 [[image:1657352645687-385.png]] 317 317 388 + 318 318 ((( 319 319 To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 320 320 ))) ... ... @@ -328,11 +328,14 @@ 328 328 329 329 === 2.2.8 Use TCP protocol to uplink data === 330 330 402 + 331 331 This feature is supported since firmware version v110 332 332 333 333 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 334 334 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 335 335 408 + 409 + 336 336 [[image:1657352898400-901.png]] 337 337 338 338 ... ... @@ -342,6 +342,7 @@ 342 342 343 343 === 2.2.9 Change Update Interval === 344 344 419 + 345 345 User can use below command to change the (% style="color:green" %)**uplink interval**. 346 346 347 347 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -355,53 +355,88 @@ 355 355 == 2.3 Uplink Payload == 356 356 357 357 358 -NBSN95 has different working mode for the connections of different type 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. 433 +((( 434 +N95S31B has different working mode for the connections of different type 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. 435 +))) 359 359 360 360 438 +((( 361 361 For example: 440 +))) 362 362 363 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 442 +((( 443 + (% 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. 444 +))) 364 364 365 365 447 +((( 366 366 The uplink payloads are composed in ASCII String. For example: 449 +))) 367 367 451 +((( 368 368 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 +))) 369 369 455 +((( 370 370 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 +))) 371 371 372 372 460 +((( 373 373 (% style="color:red" %)**NOTE:** 462 +))) 374 374 375 375 (% style="color:red" %) 376 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 -1. By default, the device will send an uplink message every 1 hour. 465 +1. ((( 466 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 467 +))) 468 +1. ((( 469 +**By default, the device will send an uplink message every 1 hour.** 378 378 379 379 380 380 473 + 474 +))) 475 + 381 381 === 2.3.1 Payload Analyze === 382 382 478 + 383 383 N95S31B uplink payload includes in total 21 bytes 384 384 385 385 386 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)482 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 387 387 |=(% style="width: 60px;" %)((( 388 388 **Size(bytes)** 389 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 -|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 485 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 486 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 487 +((( 391 391 Reserve/ Same as NBSN95 CFGMOD=1 489 +))) 392 392 491 +((( 393 393 No function here. 493 +))) 394 394 )))|(% style="width:77px" %)((( 395 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 495 +((( 496 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 497 +))) 396 396 499 +((( 397 397 By SHT31 501 +))) 398 398 )))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 503 +((( 504 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 505 +))) 400 400 507 +((( 401 401 By SHT31 402 402 ))) 510 +))) 403 403 404 404 ((( 513 + 514 + 405 405 ((( 406 406 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 407 407 ))) ... ... @@ -434,6 +434,7 @@ 434 434 435 435 === 2.3.2 Device ID === 436 436 547 + 437 437 ((( 438 438 By default, the Device ID equal to the last 6 bytes of IMEI. 439 439 ))) ... ... @@ -459,14 +459,25 @@ 459 459 === 2.3.3 Version Info === 460 460 461 461 573 +((( 462 462 These bytes include the hardware and software version. 575 +))) 463 463 577 +((( 464 464 Higher byte: Specify hardware version: always 0x00 for N95S31B 579 +))) 465 465 581 +((( 466 466 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 583 +))) 467 467 585 +((( 586 + 587 +))) 468 468 589 +((( 469 469 For example: 0x00 6E: this device is N95S31B with firmware version 110. 591 +))) 470 470 471 471 ((( 472 472 ... ... @@ -475,6 +475,7 @@ 475 475 476 476 === 2.3.4 Battery Info === 477 477 600 + 478 478 ((( 479 479 Ex1: 0x0B45 = 2885mV 480 480 ))) ... ... @@ -487,6 +487,7 @@ 487 487 488 488 === 2.3.5 Signal Strength === 489 489 613 + 490 490 ((( 491 491 NB-IoT Network signal Strength. 492 492 ))) ... ... @@ -519,6 +519,7 @@ 519 519 520 520 === 2.3.6 Temperature & Humidity === 521 521 646 + 522 522 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 523 523 524 524 [[image:image-20220709161741-3.png]] ... ... @@ -535,10 +535,11 @@ 535 535 536 536 537 537 538 -== 2. 5Downlink Payload ==663 +== 2.4 Downlink Payload == 539 539 540 -By default, NDDS75 prints the downlink payload to console port. 541 541 666 +By default, N95S31B prints the downlink payload to console port. 667 + 542 542 [[image:image-20220709100028-1.png]] 543 543 544 544 ... ... @@ -575,7 +575,7 @@ 575 575 ))) 576 576 577 577 ((( 578 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 579 579 ))) 580 580 581 581 ... ... @@ -589,6 +589,7 @@ 589 589 590 590 == 2.5 Battery Analysis == 591 591 718 + 592 592 === 2.5.1 Battery Type === 593 593 594 594 ... ... @@ -616,8 +616,9 @@ 616 616 617 617 === 2.5.2 Power consumption Analyze === 618 618 746 + 619 619 ((( 620 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]748 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 621 621 ))) 622 622 623 623 ((( ... ... @@ -627,6 +627,7 @@ 627 627 628 628 === 2.5.3 Battery Note === 629 629 758 + 630 630 ((( 631 631 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 uplink data, then the battery life may be decreased. 632 632 ))) ... ... @@ -649,6 +649,7 @@ 649 649 650 650 = 3. Access NB-IoT Module = 651 651 781 + 652 652 ((( 653 653 Users can directly access the AT command set of the NB-IoT module. 654 654 ))) ... ... @@ -655,6 +655,8 @@ 655 655 656 656 ((( 657 657 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/]] 788 + 789 + 658 658 ))) 659 659 660 660 [[image:1657333200519-600.png]] ... ... @@ -663,11 +663,13 @@ 663 663 664 664 = 4. Using the AT Commands = 665 665 798 + 666 666 == 4.1 Access AT Commands == 667 667 668 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 669 669 802 +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]] 670 670 804 + 671 671 AT+<CMD>? : Help on <CMD> 672 672 673 673 AT+<CMD> : Run <CMD> ... ... @@ -741,6 +741,7 @@ 741 741 742 742 = 5. FAQ = 743 743 878 + 744 744 == 5.1 How to Upgrade Firmware == 745 745 746 746 ... ... @@ -753,13 +753,18 @@ 753 753 ))) 754 754 755 755 ((( 756 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 891 + 892 + 893 +((( 894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 757 757 ))) 896 +))) 758 758 759 759 760 760 761 761 = 6. Trouble Shooting = 762 762 902 + 763 763 == 6.1 Connection problem when uploading firmware == 764 764 765 765 ... ... @@ -775,6 +775,7 @@ 775 775 776 776 == 6.2 AT Command input doesn't work == 777 777 918 + 778 778 ((( 779 779 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. 780 780 ... ... @@ -785,7 +785,7 @@ 785 785 = 7. Order Info = 786 786 787 787 788 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**929 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 789 789 790 790 791 791 (% class="wikigeneratedid" %) ... ... @@ -800,7 +800,7 @@ 800 800 801 801 (% style="color:#037691" %)**Package Includes**: 802 802 803 -* NS E01DistanceDetectSensorNode x 1944 +* N95S31B NB-IoT Temperature and Humidity Sensor 804 804 * External antenna x 1 805 805 ))) 806 806 ... ... @@ -809,11 +809,10 @@ 809 809 810 810 (% style="color:#037691" %)**Dimension and weight**: 811 811 812 - 813 813 * Device Size: 13.0 x 5 x 4.5 cm 814 814 * Device Weight: 150g 815 -* Package Size / pcs : 1 5x12x 5.5cm816 -* Weight / pcs : 220g955 +* Package Size / pcs : 14.0 x 8x 5 cm 956 +* Weight / pcs : 180g 817 817 ))) 818 818 819 819 ((( ... ... @@ -825,5 +825,9 @@ 825 825 826 826 = 9. Support = 827 827 968 + 828 828 * 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. 829 829 * 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]] 971 + 972 + 973 +
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +58.5 KB - Content