Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.26 >
edited by Xiaoling
on 2022/07/11 08:35
To version < 121.1 >
edited by David Huang
on 2022/09/08 16:31
>
Change comment: Uploaded new attachment "image-20220908163102-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -17,6 +17,7 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
59 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -66,6 +66,9 @@
66 66  * Micro SIM card slot for NB-IoT SIM
67 67  * 8500mAh Battery for long term use
68 68  
71 +
72 +
73 +
69 69  == 1.3  Specification ==
70 70  
71 71  
... ... @@ -74,6 +74,8 @@
74 74  * Supply Voltage: 2.1v ~~ 3.6v
75 75  * Operating Temperature: -40 ~~ 85°C
76 76  
82 +
83 +
77 77  (% style="color:#037691" %)**NB-IoT Spec:**
78 78  
79 79  * - B1 @H-FDD: 2100MHz
... ... @@ -83,9 +83,10 @@
83 83  * - B20 @H-FDD: 800MHz
84 84  * - B28 @H-FDD: 700MHz
85 85  
86 -(% style="color:#037691" %)**Battery:**
87 87  
88 88  
95 +(% style="color:#037691" %)**Battery:**
96 +
89 89  * Li/SOCI2 un-chargeable battery
90 90  * Capacity: 8500mAh
91 91  * Self Discharge: <1% / Year @ 25°C
... ... @@ -92,8 +92,12 @@
92 92  * Max continuously current: 130mA
93 93  * Max boost current: 2A, 1 second
94 94  
103 +
104 +
105 +
95 95  == ​1.4  Applications ==
96 96  
108 +
97 97  * Smart Buildings & Home Automation
98 98  * Logistics and Supply Chain Management
99 99  * Smart Metering
... ... @@ -105,15 +105,20 @@
105 105  ​
106 106  
107 107  
108 -== 1.5  Pin Definitions ==
109 109  
121 +== 1.5  Pin Definitions & Switch ==
122 +
123 +
110 110  N95S31B use the mother board from NBSN95 which as below.
111 111  
126 +
112 112  [[image:image-20220709144723-1.png]]
113 113  
114 114  
130 +
115 115  === 1.5.1 Jumper JP2 ===
116 116  
133 +
117 117  Power on Device when put this jumper.
118 118  
119 119  
... ... @@ -120,14 +120,20 @@
120 120  
121 121  === 1.5.2 BOOT MODE / SW1 ===
122 122  
140 +
141 +(((
123 123  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 +)))
124 124  
145 +(((
125 125  2) Flash: work mode, device starts to work and send out console output for further debug
147 +)))
126 126  
127 127  
128 128  
129 129  === 1.5.3 Reset Button ===
130 130  
153 +
131 131  Press to reboot the device.
132 132  
133 133  
... ... @@ -134,13 +134,18 @@
134 134  
135 135  === 1.5.4 LED ===
136 136  
160 +
137 137  It will flash:
138 138  
139 139  1. When boot the device in flash mode
140 140  1. Send an uplink packet
141 141  
166 +
167 +
168 +
142 142  = 2.  Use N95S31B to communicate with IoT Server =
143 143  
171 +
144 144  == 2.1  How it works ==
145 145  
146 146  
... ... @@ -157,7 +157,7 @@
157 157  
158 158  )))
159 159  
160 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
161 161  
162 162  (((
163 163  
... ... @@ -173,26 +173,49 @@
173 173  [[image:image-20220709150546-2.png]]
174 174  
175 175  
204 +
176 176  === 2.2.1 Test Requirement ===
177 177  
178 178  
208 +(((
179 179  To use N95S31B in your city, make sure meet below requirements:
210 +)))
180 180  
181 -* Your local operator has already distributed a NB-IoT Network there.
182 -* The local NB-IoT network used the band that N95S31B supports.
183 -* 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 +)))
184 184  
222 +(((
185 185  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
186 186  
226 +(((
187 187  N95S31B supports different communication protocol such as :
228 +)))
188 188  
189 189  (((
190 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
191 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
192 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
193 -* 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 +)))
194 194  
244 +(((
195 195  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 +)))
196 196  
197 197  
198 198  )))
... ... @@ -203,6 +203,7 @@
203 203  
204 204  === 2.2.3  Insert SIM card ===
205 205  
257 +
206 206  (((
207 207  Insert the NB-IoT Card get from your provider.
208 208  )))
... ... @@ -218,14 +218,18 @@
218 218  
219 219  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
220 220  
273 +
221 221  (((
222 222  (((
223 223  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 +
224 224  )))
225 225  )))
226 226  
227 227  [[image:1657351312545-300.png]]
228 228  
284 +
229 229  **Connection:**
230 230  
231 231   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -249,8 +249,9 @@
249 249  
250 250  [[image:1657329814315-101.png]]
251 251  
308 +
252 252  (((
253 -(% 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]]**
254 254  )))
255 255  
256 256  
... ... @@ -257,9 +257,10 @@
257 257  
258 258  === 2.2.5  Use CoAP protocol to uplink data ===
259 259  
260 -(% 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/]]
261 261  
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/]]**
262 262  
320 +
263 263  (((
264 264  **Use below commands:**
265 265  )))
... ... @@ -298,6 +298,8 @@
298 298  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
299 299  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
300 300  
359 +
360 +
301 301  [[image:1657352391268-297.png]]
302 302  
303 303  
... ... @@ -307,6 +307,7 @@
307 307  
308 308  === 2.2.7  Use MQTT protocol to uplink data ===
309 309  
370 +
310 310  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
311 311  
312 312  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -317,11 +317,14 @@
317 317  * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
318 318  * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
319 319  
381 +
382 +
320 320  [[image:1657352634421-276.png]]
321 321  
322 322  
323 323  [[image:1657352645687-385.png]]
324 324  
388 +
325 325  (((
326 326  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.
327 327  )))
... ... @@ -335,11 +335,14 @@
335 335  
336 336  === 2.2.8  Use TCP protocol to uplink data ===
337 337  
402 +
338 338  This feature is supported since firmware version v110
339 339  
340 340  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
341 341  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
342 342  
408 +
409 +
343 343  [[image:1657352898400-901.png]]
344 344  
345 345  
... ... @@ -349,6 +349,7 @@
349 349  
350 350  === 2.2.9  Change Update Interval ===
351 351  
419 +
352 352  User can use below command to change the (% style="color:green" %)**uplink interval**.
353 353  
354 354  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -362,30 +362,52 @@
362 362  == 2.3  Uplink Payload ==
363 363  
364 364  
365 -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 +)))
366 366  
367 367  
438 +(((
368 368  For example:
440 +)))
369 369  
370 - (% 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 +)))
371 371  
372 372  
447 +(((
373 373  The uplink payloads are composed in  ASCII String. For example:
449 +)))
374 374  
451 +(((
375 375  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
453 +)))
376 376  
455 +(((
377 377  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
457 +)))
378 378  
379 379  
460 +(((
380 380  (% style="color:red" %)**NOTE:**
462 +)))
381 381  
382 382  (% style="color:red" %)
383 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
384 -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.**
385 385  
386 386  
472 +
473 +
474 +)))
475 +
387 387  === 2.3.1  Payload Analyze ===
388 388  
478 +
389 389  N95S31B uplink payload includes in total 21 bytes
390 390  
391 391  
... ... @@ -420,6 +420,8 @@
420 420  )))
421 421  
422 422  (((
513 +
514 +
423 423  (((
424 424  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 425  )))
... ... @@ -452,6 +452,7 @@
452 452  
453 453  === 2.3.2  Device ID ===
454 454  
547 +
455 455  (((
456 456  By default, the Device ID equal to the last 6 bytes of IMEI.
457 457  )))
... ... @@ -477,14 +477,25 @@
477 477  === 2.3.3  Version Info ===
478 478  
479 479  
573 +(((
480 480  These bytes include the hardware and software version.
575 +)))
481 481  
577 +(((
482 482  Higher byte: Specify hardware version: always 0x00 for N95S31B
579 +)))
483 483  
581 +(((
484 484  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
583 +)))
485 485  
585 +(((
586 +
587 +)))
486 486  
589 +(((
487 487  For example: 0x00 6E: this device is N95S31B with firmware version 110.
591 +)))
488 488  
489 489  (((
490 490  
... ... @@ -493,6 +493,7 @@
493 493  
494 494  === 2.3.4  Battery Info ===
495 495  
600 +
496 496  (((
497 497  Ex1: 0x0B45 = 2885mV
498 498  )))
... ... @@ -505,6 +505,7 @@
505 505  
506 506  === 2.3.5  Signal Strength ===
507 507  
613 +
508 508  (((
509 509  NB-IoT Network signal Strength.
510 510  )))
... ... @@ -537,6 +537,7 @@
537 537  
538 538  === 2.3.6  Temperature & Humidity ===
539 539  
646 +
540 540  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
541 541  
542 542  [[image:image-20220709161741-3.png]]
... ... @@ -555,8 +555,9 @@
555 555  
556 556  == 2.4  Downlink Payload ==
557 557  
558 -By default, NDDS75 prints the downlink payload to console port.
559 559  
666 +By default, N95S31B prints the downlink payload to console port.
667 +
560 560  [[image:image-20220709100028-1.png]]
561 561  
562 562  
... ... @@ -593,7 +593,7 @@
593 593  )))
594 594  
595 595  (((
596 -If payload = 0x04FF, it will reset the NDDS75
704 +If payload = 0x04FF, it will reset the N95S31B
597 597  )))
598 598  
599 599  
... ... @@ -607,6 +607,7 @@
607 607  
608 608  == 2.5  ​Battery Analysis ==
609 609  
718 +
610 610  === 2.5.1  ​Battery Type ===
611 611  
612 612  
... ... @@ -634,8 +634,9 @@
634 634  
635 635  === 2.5.2  Power consumption Analyze ===
636 636  
746 +
637 637  (((
638 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
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.
639 639  )))
640 640  
641 641  (((
... ... @@ -645,6 +645,7 @@
645 645  
646 646  === 2.5.3  ​Battery Note ===
647 647  
758 +
648 648  (((
649 649  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.
650 650  )))
... ... @@ -667,6 +667,7 @@
667 667  
668 668  = 3. ​ Access NB-IoT Module =
669 669  
781 +
670 670  (((
671 671  Users can directly access the AT command set of the NB-IoT module.
672 672  )))
... ... @@ -673,6 +673,8 @@
673 673  
674 674  (((
675 675  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 +
676 676  )))
677 677  
678 678  [[image:1657333200519-600.png]]
... ... @@ -681,11 +681,13 @@
681 681  
682 682  = 4.  Using the AT Commands =
683 683  
798 +
684 684  == 4.1  Access AT Commands ==
685 685  
686 -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/]]
687 687  
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]]
688 688  
804 +
689 689  AT+<CMD>?  : Help on <CMD>
690 690  
691 691  AT+<CMD>         : Run <CMD>
... ... @@ -759,6 +759,7 @@
759 759  
760 760  = ​5.  FAQ =
761 761  
878 +
762 762  == 5.1 ​ How to Upgrade Firmware ==
763 763  
764 764  
... ... @@ -773,13 +773,16 @@
773 773  (((
774 774  
775 775  
776 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
893 +(((
894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
777 777  )))
896 +)))
778 778  
779 779  
780 780  
781 781  = 6.  Trouble Shooting =
782 782  
902 +
783 783  == 6.1  ​Connection problem when uploading firmware ==
784 784  
785 785  
... ... @@ -795,6 +795,7 @@
795 795  
796 796  == 6.2  AT Command input doesn't work ==
797 797  
918 +
798 798  (((
799 799  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.
800 800  
... ... @@ -844,5 +844,9 @@
844 844  
845 845  = 9.  Support =
846 846  
968 +
847 847  * 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.
848 848  * 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
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content

Applications

Navigation

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