Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.3 >
edited by Xiaoling
on 2022/07/09 16:59
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  )))
... ... @@ -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:1657350248151-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.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]]**
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.5  Downlink 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 NDDS75
704 +If payload = 0x04FF, it will reset the N95S31B
579 579  )))
580 580  
581 581  
... ... @@ -587,51 +587,17 @@
587 587  
588 588  
589 589  
590 -== 2.6  ​LED Indicator ==
716 +== 2.5  ​Battery Analysis ==
591 591  
592 592  
593 -The NDDS75 has an internal LED which is to show the status of different state.
719 +=== 2.5.1  ​Battery Type ===
594 594  
595 595  
596 -* 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)
597 -* Then the LED will be on for 1 second means device is boot normally.
598 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
599 -* For each uplink probe, LED will be on for 500ms.
600 -
601 601  (((
602 -
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.
603 603  )))
604 604  
605 -
606 -
607 -== 2.7  ​Firmware Change Log ==
608 -
609 -
610 610  (((
611 -Download URL & Firmware Change log
612 -)))
613 -
614 -(((
615 -[[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/]]
616 -)))
617 -
618 -
619 -(((
620 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
621 -)))
622 -
623 -
624 -
625 -== 2.8  ​Battery Analysis ==
626 -
627 -=== 2.8.1  ​Battery Type ===
628 -
629 -
630 -(((
631 -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.
632 -)))
633 -
634 -(((
635 635  The battery is designed to last for several years depends on the actually use environment and update interval. 
636 636  )))
637 637  
... ... @@ -649,56 +649,37 @@
649 649  
650 650  
651 651  
652 -=== 2.8.2  Power consumption Analyze ===
744 +=== 2.5.2  Power consumption Analyze ===
653 653  
654 -(((
655 -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.
656 -)))
657 657  
658 -
659 659  (((
660 -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.
661 661  )))
662 662  
663 663  (((
664 -(% 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 +
665 665  )))
666 666  
667 667  
668 -(((
669 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
670 -)))
756 +=== 2.5.3  ​Battery Note ===
671 671  
672 -* (((
673 -Product Model
674 -)))
675 -* (((
676 -Uplink Interval
677 -)))
678 -* (((
679 -Working Mode
680 -)))
681 681  
682 682  (((
683 -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.
684 684  )))
685 685  
686 -[[image:image-20220709110451-3.png]]
687 687  
688 688  
765 +=== 2.5.4  Replace the battery ===
689 689  
690 -=== 2.8.3  ​Battery Note ===
691 691  
692 692  (((
693 -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.
694 694  )))
695 695  
696 696  
697 -
698 -=== 2.8.4  Replace the battery ===
699 -
700 700  (((
701 -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).
702 702  )))
703 703  
704 704  
... ... @@ -705,6 +705,7 @@
705 705  
706 706  = 3. ​ Access NB-IoT Module =
707 707  
781 +
708 708  (((
709 709  Users can directly access the AT command set of the NB-IoT module.
710 710  )))
... ... @@ -711,6 +711,8 @@
711 711  
712 712  (((
713 713  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 +
714 714  )))
715 715  
716 716  [[image:1657333200519-600.png]]
... ... @@ -719,11 +719,13 @@
719 719  
720 720  = 4.  Using the AT Commands =
721 721  
798 +
722 722  == 4.1  Access AT Commands ==
723 723  
724 -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/]]
725 725  
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]]
726 726  
804 +
727 727  AT+<CMD>?  : Help on <CMD>
728 728  
729 729  AT+<CMD>         : Run <CMD>
... ... @@ -797,6 +797,7 @@
797 797  
798 798  = ​5.  FAQ =
799 799  
878 +
800 800  == 5.1 ​ How to Upgrade Firmware ==
801 801  
802 802  
... ... @@ -809,13 +809,18 @@
809 809  )))
810 810  
811 811  (((
812 -(% 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.**
813 813  )))
896 +)))
814 814  
815 815  
816 816  
817 817  = 6.  Trouble Shooting =
818 818  
902 +
819 819  == 6.1  ​Connection problem when uploading firmware ==
820 820  
821 821  
... ... @@ -831,6 +831,7 @@
831 831  
832 832  == 6.2  AT Command input doesn't work ==
833 833  
918 +
834 834  (((
835 835  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.
836 836  
... ... @@ -841,7 +841,7 @@
841 841  = 7. ​ Order Info =
842 842  
843 843  
844 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
929 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
845 845  
846 846  
847 847  (% class="wikigeneratedid" %)
... ... @@ -856,7 +856,7 @@
856 856  
857 857  (% style="color:#037691" %)**Package Includes**:
858 858  
859 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
944 +* N95S31B NB-IoT Temperature and Humidity Sensor
860 860  * External antenna x 1
861 861  )))
862 862  
... ... @@ -865,11 +865,10 @@
865 865  
866 866  (% style="color:#037691" %)**Dimension and weight**:
867 867  
868 -
869 869  * Device Size: 13.0 x 5 x 4.5 cm
870 870  * Device Weight: 150g
871 -* Package Size / pcs : 15 x 12x 5.5 cm
872 -* Weight / pcs : 220g
955 +* Package Size / pcs : 14.0 x 8x 5 cm
956 +* Weight / pcs : 180g
873 873  )))
874 874  
875 875  (((
... ... @@ -881,5 +881,9 @@
881 881  
882 882  = 9.  Support =
883 883  
968 +
884 884  * 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.
885 885  * 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