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

Summary

Details

Page properties
Content
... ... @@ -17,21 +17,35 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
23 23  
24 24  
26 +(((
25 25  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 +)))
26 26  
30 +(((
27 27  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 +)))
28 28  
34 +(((
29 29  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 +)))
30 30  
38 +(((
31 31  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 +)))
32 32  
42 +(((
43 +
44 +)))
33 33  
46 +(((
34 34  ~* make sure you have NB-IoT coverage locally.
48 +)))
35 35  
36 36  
37 37  )))
... ... @@ -42,6 +42,7 @@
42 42  
43 43  == 1.2 ​ Features ==
44 44  
59 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 46  * Monitor Temperature & Humidity via SHT31
47 47  * AT Commands to change parameters
... ... @@ -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,13 +123,18 @@
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
129 129  1. Send an uplink packet
130 130  
166 +
167 +
168 +
131 131  = 2.  Use N95S31B to communicate with IoT Server =
132 132  
171 +
133 133  == 2.1  How it works ==
134 134  
135 135  
... ... @@ -146,7 +146,7 @@
146 146  
147 147  )))
148 148  
149 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
150 150  
151 151  (((
152 152  
... ... @@ -162,26 +162,49 @@
162 162  [[image:image-20220709150546-2.png]]
163 163  
164 164  
204 +
165 165  === 2.2.1 Test Requirement ===
166 166  
167 167  
208 +(((
168 168  To use N95S31B in your city, make sure meet below requirements:
210 +)))
169 169  
170 -* Your local operator has already distributed a NB-IoT Network there.
171 -* The local NB-IoT network used the band that N95S31B supports.
172 -* 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 +)))
173 173  
222 +(((
174 174  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
175 175  
226 +(((
176 176  N95S31B supports different communication protocol such as :
228 +)))
177 177  
178 178  (((
179 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
180 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
181 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
182 -* 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 +)))
183 183  
244 +(((
184 184  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 +)))
185 185  
186 186  
187 187  )))
... ... @@ -192,6 +192,7 @@
192 192  
193 193  === 2.2.3  Insert SIM card ===
194 194  
257 +
195 195  (((
196 196  Insert the NB-IoT Card get from your provider.
197 197  )))
... ... @@ -207,14 +207,18 @@
207 207  
208 208  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
209 209  
273 +
210 210  (((
211 211  (((
212 212  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 +
213 213  )))
214 214  )))
215 215  
216 216  [[image:1657351312545-300.png]]
217 217  
284 +
218 218  **Connection:**
219 219  
220 220   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -238,8 +238,9 @@
238 238  
239 239  [[image:1657329814315-101.png]]
240 240  
308 +
241 241  (((
242 -(% 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]]**
243 243  )))
244 244  
245 245  
... ... @@ -246,9 +246,10 @@
246 246  
247 247  === 2.2.5  Use CoAP protocol to uplink data ===
248 248  
249 -(% 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/]]
250 250  
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/]]**
251 251  
320 +
252 252  (((
253 253  **Use below commands:**
254 254  )))
... ... @@ -351,27 +351,49 @@
351 351  == 2.3  Uplink Payload ==
352 352  
353 353  
354 -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.
423 +(((
424 +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.
425 +)))
355 355  
356 356  
428 +(((
357 357  For example:
430 +)))
358 358  
359 - (% 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.
432 +(((
433 + (% 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.
434 +)))
360 360  
361 361  
437 +(((
362 362  The uplink payloads are composed in  ASCII String. For example:
439 +)))
363 363  
441 +(((
364 364  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
443 +)))
365 365  
445 +(((
366 366  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
447 +)))
367 367  
368 368  
450 +(((
369 369  (% style="color:red" %)**NOTE:**
452 +)))
370 370  
371 371  (% style="color:red" %)
372 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
373 -1. By default, the device will send an uplink message every 1 hour.
455 +1. (((
456 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
457 +)))
458 +1. (((
459 +By default, the device will send an uplink message every 1 hour.
374 374  
461 +
462 +
463 +
464 +)))
465 +
375 375  === 2.3.1  Payload Analyze ===
376 376  
377 377  N95S31B uplink payload includes in total 21 bytes
... ... @@ -380,20 +380,32 @@
380 380  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
381 381  |=(% style="width: 60px;" %)(((
382 382  **Size(bytes)**
383 -)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
474 +)))|=(% 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**
384 384  |(% 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" %)(((
476 +(((
385 385  Reserve/ Same as NBSN95 CFGMOD=1
478 +)))
386 386  
480 +(((
387 387  No function here.
482 +)))
388 388  )))|(% style="width:77px" %)(((
484 +(((
389 389  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
486 +)))
390 390  
488 +(((
391 391  By SHT31
490 +)))
392 392  )))|(% style="width:80px" %)(((
492 +(((
393 393  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
494 +)))
394 394  
496 +(((
395 395  By SHT31
396 396  )))
499 +)))
397 397  
398 398  (((
399 399  (((
... ... @@ -452,15 +452,25 @@
452 452  
453 453  === 2.3.3  Version Info ===
454 454  
455 -
558 +(((
456 456  These bytes include the hardware and software version.
560 +)))
457 457  
562 +(((
458 458  Higher byte: Specify hardware version: always 0x00 for N95S31B
564 +)))
459 459  
566 +(((
460 460  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
568 +)))
461 461  
570 +(((
571 +
572 +)))
462 462  
574 +(((
463 463  For example: 0x00 6E: this device is N95S31B with firmware version 110.
576 +)))
464 464  
465 465  (((
466 466  
... ... @@ -531,7 +531,7 @@
531 531  
532 532  == 2.4  Downlink Payload ==
533 533  
534 -By default, NDDS75 prints the downlink payload to console port.
647 +By default, N95S31B prints the downlink payload to console port.
535 535  
536 536  [[image:image-20220709100028-1.png]]
537 537  
... ... @@ -569,7 +569,7 @@
569 569  )))
570 570  
571 571  (((
572 -If payload = 0x04FF, it will reset the NDDS75
685 +If payload = 0x04FF, it will reset the N95S31B
573 573  )))
574 574  
575 575  
... ... @@ -749,8 +749,10 @@
749 749  (((
750 750  
751 751  
865 +(((
752 752  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
753 753  )))
868 +)))
754 754  
755 755  
756 756  
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