Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.2 >
edited by Xiaoling
on 2022/07/09 16:18
To version < 119.3 >
edited by Xiaoling
on 2022/08/22 15:05
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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  )))
... ... @@ -54,6 +54,8 @@
54 54  * 8500mAh Battery for long term use
55 55  
56 56  
72 +
73 +
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -62,6 +62,8 @@
62 62  * Supply Voltage: 2.1v ~~ 3.6v
63 63  * Operating Temperature: -40 ~~ 85°C
64 64  
82 +
83 +
65 65  (% style="color:#037691" %)**NB-IoT Spec:**
66 66  
67 67  * - B1 @H-FDD: 2100MHz
... ... @@ -71,9 +71,10 @@
71 71  * - B20 @H-FDD: 800MHz
72 72  * - B28 @H-FDD: 700MHz
73 73  
74 -(% style="color:#037691" %)**Battery:**
75 75  
76 76  
95 +(% style="color:#037691" %)**Battery:**
96 +
77 77  * Li/SOCI2 un-chargeable battery
78 78  * Capacity: 8500mAh
79 79  * Self Discharge: <1% / Year @ 25°C
... ... @@ -81,8 +81,11 @@
81 81  * Max boost current: 2A, 1 second
82 82  
83 83  
104 +
105 +
84 84  == ​1.4  Applications ==
85 85  
108 +
86 86  * Smart Buildings & Home Automation
87 87  * Logistics and Supply Chain Management
88 88  * Smart Metering
... ... @@ -94,15 +94,20 @@
94 94  ​
95 95  
96 96  
97 -== 1.5  Pin Definitions ==
98 98  
121 +== 1.5  Pin Definitions & Switch ==
122 +
123 +
99 99  N95S31B use the mother board from NBSN95 which as below.
100 100  
126 +
101 101  [[image:image-20220709144723-1.png]]
102 102  
103 103  
130 +
104 104  === 1.5.1 Jumper JP2 ===
105 105  
133 +
106 106  Power on Device when put this jumper.
107 107  
108 108  
... ... @@ -109,14 +109,20 @@
109 109  
110 110  === 1.5.2 BOOT MODE / SW1 ===
111 111  
140 +
141 +(((
112 112  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 +)))
113 113  
145 +(((
114 114  2) Flash: work mode, device starts to work and send out console output for further debug
147 +)))
115 115  
116 116  
117 117  
118 118  === 1.5.3 Reset Button ===
119 119  
153 +
120 120  Press to reboot the device.
121 121  
122 122  
... ... @@ -123,6 +123,7 @@
123 123  
124 124  === 1.5.4 LED ===
125 125  
160 +
126 126  It will flash:
127 127  
128 128  1. When boot the device in flash mode
... ... @@ -130,8 +130,10 @@
130 130  
131 131  
132 132  
168 +
133 133  = 2.  Use N95S31B to communicate with IoT Server =
134 134  
171 +
135 135  == 2.1  How it works ==
136 136  
137 137  
... ... @@ -148,7 +148,7 @@
148 148  
149 149  )))
150 150  
151 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
152 152  
153 153  (((
154 154  
... ... @@ -164,26 +164,49 @@
164 164  [[image:image-20220709150546-2.png]]
165 165  
166 166  
204 +
167 167  === 2.2.1 Test Requirement ===
168 168  
169 169  
208 +(((
170 170  To use N95S31B in your city, make sure meet below requirements:
210 +)))
171 171  
172 -* Your local operator has already distributed a NB-IoT Network there.
173 -* The local NB-IoT network used the band that N95S31B supports.
174 -* 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 +)))
175 175  
222 +(((
176 176  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
177 177  
226 +(((
178 178  N95S31B supports different communication protocol such as :
228 +)))
179 179  
180 180  (((
181 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 -* 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 +)))
185 185  
244 +(((
186 186  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 +)))
187 187  
188 188  
189 189  )))
... ... @@ -194,6 +194,7 @@
194 194  
195 195  === 2.2.3  Insert SIM card ===
196 196  
257 +
197 197  (((
198 198  Insert the NB-IoT Card get from your provider.
199 199  )))
... ... @@ -209,14 +209,18 @@
209 209  
210 210  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
211 211  
273 +
212 212  (((
213 213  (((
214 214  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 +
215 215  )))
216 216  )))
217 217  
218 218  [[image:1657351312545-300.png]]
219 219  
284 +
220 220  **Connection:**
221 221  
222 222   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -240,8 +240,9 @@
240 240  
241 241  [[image:1657329814315-101.png]]
242 242  
308 +
243 243  (((
244 -(% 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/]]
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]]**
245 245  )))
246 246  
247 247  
... ... @@ -248,9 +248,10 @@
248 248  
249 249  === 2.2.5  Use CoAP protocol to uplink data ===
250 250  
251 -(% 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/]]
252 252  
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/]]**
253 253  
320 +
254 254  (((
255 255  **Use below commands:**
256 256  )))
... ... @@ -289,6 +289,8 @@
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 290  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
291 291  
359 +
360 +
292 292  [[image:1657352391268-297.png]]
293 293  
294 294  
... ... @@ -298,6 +298,7 @@
298 298  
299 299  === 2.2.7  Use MQTT protocol to uplink data ===
300 300  
370 +
301 301  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
302 302  
303 303  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -308,11 +308,14 @@
308 308  * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 309  * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
310 310  
381 +
382 +
311 311  [[image:1657352634421-276.png]]
312 312  
313 313  
314 314  [[image:1657352645687-385.png]]
315 315  
388 +
316 316  (((
317 317  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.
318 318  )))
... ... @@ -326,11 +326,14 @@
326 326  
327 327  === 2.2.8  Use TCP protocol to uplink data ===
328 328  
402 +
329 329  This feature is supported since firmware version v110
330 330  
331 331  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 332  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
333 333  
408 +
409 +
334 334  [[image:1657352898400-901.png]]
335 335  
336 336  
... ... @@ -340,6 +340,7 @@
340 340  
341 341  === 2.2.9  Change Update Interval ===
342 342  
419 +
343 343  User can use below command to change the (% style="color:green" %)**uplink interval**.
344 344  
345 345  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -353,54 +353,88 @@
353 353  == 2.3  Uplink Payload ==
354 354  
355 355  
356 -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 +)))
357 357  
358 358  
438 +(((
359 359  For example:
440 +)))
360 360  
361 - (% 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 +)))
362 362  
363 363  
447 +(((
364 364  The uplink payloads are composed in  ASCII String. For example:
449 +)))
365 365  
451 +(((
366 366  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
453 +)))
367 367  
455 +(((
368 368  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
457 +)))
369 369  
370 370  
460 +(((
371 371  (% style="color:red" %)**NOTE:**
462 +)))
372 372  
373 373  (% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 -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.**
376 376  
377 377  
378 378  
473 +
474 +)))
379 379  
380 380  === 2.3.1  Payload Analyze ===
381 381  
478 +
382 382  N95S31B uplink payload includes in total 21 bytes
383 383  
384 384  
385 -(% 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" %)
386 386  |=(% style="width: 60px;" %)(((
387 387  **Size(bytes)**
388 -)))|=(% 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**
389 -|(% 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 +(((
390 390  Reserve/ Same as NBSN95 CFGMOD=1
489 +)))
391 391  
491 +(((
392 392  No function here.
493 +)))
393 393  )))|(% style="width:77px" %)(((
394 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
495 +(((
496 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
497 +)))
395 395  
499 +(((
396 396  By SHT31
501 +)))
397 397  )))|(% style="width:80px" %)(((
398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
503 +(((
504 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
505 +)))
399 399  
507 +(((
400 400  By SHT31
401 401  )))
510 +)))
402 402  
403 403  (((
513 +
514 +
404 404  (((
405 405  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
406 406  )))
... ... @@ -433,6 +433,7 @@
433 433  
434 434  === 2.3.2  Device ID ===
435 435  
547 +
436 436  (((
437 437  By default, the Device ID equal to the last 6 bytes of IMEI.
438 438  )))
... ... @@ -458,14 +458,25 @@
458 458  === 2.3.3  Version Info ===
459 459  
460 460  
573 +(((
461 461  These bytes include the hardware and software version.
575 +)))
462 462  
577 +(((
463 463  Higher byte: Specify hardware version: always 0x00 for N95S31B
579 +)))
464 464  
581 +(((
465 465  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
583 +)))
466 466  
585 +(((
586 +
587 +)))
467 467  
589 +(((
468 468  For example: 0x00 6E: this device is N95S31B with firmware version 110.
591 +)))
469 469  
470 470  (((
471 471  
... ... @@ -474,6 +474,7 @@
474 474  
475 475  === 2.3.4  Battery Info ===
476 476  
600 +
477 477  (((
478 478  Ex1: 0x0B45 = 2885mV
479 479  )))
... ... @@ -486,6 +486,7 @@
486 486  
487 487  === 2.3.5  Signal Strength ===
488 488  
613 +
489 489  (((
490 490  NB-IoT Network signal Strength.
491 491  )))
... ... @@ -518,6 +518,7 @@
518 518  
519 519  === 2.3.6  Temperature & Humidity ===
520 520  
646 +
521 521  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
522 522  
523 523  [[image:image-20220709161741-3.png]]
... ... @@ -534,10 +534,11 @@
534 534  
535 535  
536 536  
537 -== 2.5  Downlink Payload ==
663 +== 2.4  Downlink Payload ==
538 538  
539 -By default, NDDS75 prints the downlink payload to console port.
540 540  
666 +By default, N95S31B prints the downlink payload to console port.
667 +
541 541  [[image:image-20220709100028-1.png]]
542 542  
543 543  
... ... @@ -574,7 +574,7 @@
574 574  )))
575 575  
576 576  (((
577 -If payload = 0x04FF, it will reset the NDDS75
704 +If payload = 0x04FF, it will reset the N95S31B
578 578  )))
579 579  
580 580  
... ... @@ -586,51 +586,17 @@
586 586  
587 587  
588 588  
589 -== 2.6  ​LED Indicator ==
716 +== 2.5  ​Battery Analysis ==
590 590  
591 591  
592 -The NDDS75 has an internal LED which is to show the status of different state.
719 +=== 2.5.1  ​Battery Type ===
593 593  
594 594  
595 -* 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)
596 -* Then the LED will be on for 1 second means device is boot normally.
597 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
598 -* For each uplink probe, LED will be on for 500ms.
599 -
600 600  (((
601 -
723 +The N95S31B 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.
602 602  )))
603 603  
604 -
605 -
606 -== 2.7  ​Firmware Change Log ==
607 -
608 -
609 609  (((
610 -Download URL & Firmware Change log
611 -)))
612 -
613 -(((
614 -[[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/]]
615 -)))
616 -
617 -
618 -(((
619 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
620 -)))
621 -
622 -
623 -
624 -== 2.8  ​Battery Analysis ==
625 -
626 -=== 2.8.1  ​Battery Type ===
627 -
628 -
629 -(((
630 -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.
631 -)))
632 -
633 -(((
634 634  The battery is designed to last for several years depends on the actually use environment and update interval. 
635 635  )))
636 636  
... ... @@ -648,56 +648,37 @@
648 648  
649 649  
650 650  
651 -=== 2.8.2  Power consumption Analyze ===
744 +=== 2.5.2  Power consumption Analyze ===
652 652  
653 -(((
654 -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.
655 -)))
656 656  
657 -
658 658  (((
659 -Instruction to use as below:
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.
660 660  )))
661 661  
662 662  (((
663 -(% 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/]]
752 +
664 664  )))
665 665  
666 666  
667 -(((
668 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
669 -)))
756 +=== 2.5.3  ​Battery Note ===
670 670  
671 -* (((
672 -Product Model
673 -)))
674 -* (((
675 -Uplink Interval
676 -)))
677 -* (((
678 -Working Mode
679 -)))
680 680  
681 681  (((
682 -And the Life expectation in difference case will be shown on the right.
760 +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.
683 683  )))
684 684  
685 -[[image:image-20220709110451-3.png]]
686 686  
687 687  
765 +=== 2.5.4  Replace the battery ===
688 688  
689 -=== 2.8.3  ​Battery Note ===
690 690  
691 691  (((
692 -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.
769 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
693 693  )))
694 694  
695 695  
696 -
697 -=== 2.8.4  Replace the battery ===
698 -
699 699  (((
700 -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).
774 +The default battery pack of N95S31B 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).
701 701  )))
702 702  
703 703  
... ... @@ -704,6 +704,7 @@
704 704  
705 705  = 3. ​ Access NB-IoT Module =
706 706  
781 +
707 707  (((
708 708  Users can directly access the AT command set of the NB-IoT module.
709 709  )))
... ... @@ -710,6 +710,8 @@
710 710  
711 711  (((
712 712  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 +
713 713  )))
714 714  
715 715  [[image:1657333200519-600.png]]
... ... @@ -718,11 +718,13 @@
718 718  
719 719  = 4.  Using the AT Commands =
720 720  
798 +
721 721  == 4.1  Access AT Commands ==
722 722  
723 -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/]]
724 724  
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]]
725 725  
804 +
726 726  AT+<CMD>?  : Help on <CMD>
727 727  
728 728  AT+<CMD>         : Run <CMD>
... ... @@ -796,6 +796,7 @@
796 796  
797 797  = ​5.  FAQ =
798 798  
878 +
799 799  == 5.1 ​ How to Upgrade Firmware ==
800 800  
801 801  
... ... @@ -808,13 +808,18 @@
808 808  )))
809 809  
810 810  (((
811 -(% 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.**
812 812  )))
896 +)))
813 813  
814 814  
815 815  
816 816  = 6.  Trouble Shooting =
817 817  
902 +
818 818  == 6.1  ​Connection problem when uploading firmware ==
819 819  
820 820  
... ... @@ -830,6 +830,7 @@
830 830  
831 831  == 6.2  AT Command input doesn't work ==
832 832  
918 +
833 833  (((
834 834  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.
835 835  
... ... @@ -840,7 +840,7 @@
840 840  = 7. ​ Order Info =
841 841  
842 842  
843 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
929 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
844 844  
845 845  
846 846  (% class="wikigeneratedid" %)
... ... @@ -855,7 +855,7 @@
855 855  
856 856  (% style="color:#037691" %)**Package Includes**:
857 857  
858 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
944 +* N95S31B NB-IoT Temperature and Humidity Sensor
859 859  * External antenna x 1
860 860  )))
861 861  
... ... @@ -864,11 +864,10 @@
864 864  
865 865  (% style="color:#037691" %)**Dimension and weight**:
866 866  
867 -
868 868  * Device Size: 13.0 x 5 x 4.5 cm
869 869  * Device Weight: 150g
870 -* Package Size / pcs : 15 x 12x 5.5 cm
871 -* Weight / pcs : 220g
955 +* Package Size / pcs : 14.0 x 8x 5 cm
956 +* Weight / pcs : 180g
872 872  )))
873 873  
874 874  (((
... ... @@ -880,5 +880,9 @@
880 880  
881 881  = 9.  Support =
882 882  
968 +
883 883  * 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.
884 884  * 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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0