Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.14 >
edited by Xiaoling
on 2022/07/09 17:55
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
... ... @@ -64,6 +64,8 @@
64 64  * Supply Voltage: 2.1v ~~ 3.6v
65 65  * Operating Temperature: -40 ~~ 85°C
66 66  
82 +
83 +
67 67  (% style="color:#037691" %)**NB-IoT Spec:**
68 68  
69 69  * - B1 @H-FDD: 2100MHz
... ... @@ -73,9 +73,10 @@
73 73  * - B20 @H-FDD: 800MHz
74 74  * - B28 @H-FDD: 700MHz
75 75  
76 -(% style="color:#037691" %)**Battery:**
77 77  
78 78  
95 +(% style="color:#037691" %)**Battery:**
96 +
79 79  * Li/SOCI2 un-chargeable battery
80 80  * Capacity: 8500mAh
81 81  * Self Discharge: <1% / Year @ 25°C
... ... @@ -87,6 +87,7 @@
87 87  
88 88  == ​1.4  Applications ==
89 89  
108 +
90 90  * Smart Buildings & Home Automation
91 91  * Logistics and Supply Chain Management
92 92  * Smart Metering
... ... @@ -98,15 +98,20 @@
98 98  ​
99 99  
100 100  
101 -== 1.5  Pin Definitions ==
102 102  
121 +== 1.5  Pin Definitions & Switch ==
122 +
123 +
103 103  N95S31B use the mother board from NBSN95 which as below.
104 104  
126 +
105 105  [[image:image-20220709144723-1.png]]
106 106  
107 107  
130 +
108 108  === 1.5.1 Jumper JP2 ===
109 109  
133 +
110 110  Power on Device when put this jumper.
111 111  
112 112  
... ... @@ -113,14 +113,20 @@
113 113  
114 114  === 1.5.2 BOOT MODE / SW1 ===
115 115  
140 +
141 +(((
116 116  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 +)))
117 117  
145 +(((
118 118  2) Flash: work mode, device starts to work and send out console output for further debug
147 +)))
119 119  
120 120  
121 121  
122 122  === 1.5.3 Reset Button ===
123 123  
153 +
124 124  Press to reboot the device.
125 125  
126 126  
... ... @@ -127,6 +127,7 @@
127 127  
128 128  === 1.5.4 LED ===
129 129  
160 +
130 130  It will flash:
131 131  
132 132  1. When boot the device in flash mode
... ... @@ -133,8 +133,11 @@
133 133  1. Send an uplink packet
134 134  
135 135  
167 +
168 +
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
171 +
138 138  == 2.1  How it works ==
139 139  
140 140  
... ... @@ -151,7 +151,7 @@
151 151  
152 152  )))
153 153  
154 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
155 155  
156 156  (((
157 157  
... ... @@ -167,26 +167,49 @@
167 167  [[image:image-20220709150546-2.png]]
168 168  
169 169  
204 +
170 170  === 2.2.1 Test Requirement ===
171 171  
172 172  
208 +(((
173 173  To use N95S31B in your city, make sure meet below requirements:
210 +)))
174 174  
175 -* Your local operator has already distributed a NB-IoT Network there.
176 -* The local NB-IoT network used the band that N95S31B supports.
177 -* 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 +)))
178 178  
222 +(((
179 179  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
180 180  
226 +(((
181 181  N95S31B supports different communication protocol such as :
228 +)))
182 182  
183 183  (((
184 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
185 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
186 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
187 -* 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 +)))
188 188  
244 +(((
189 189  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 +)))
190 190  
191 191  
192 192  )))
... ... @@ -197,6 +197,7 @@
197 197  
198 198  === 2.2.3  Insert SIM card ===
199 199  
257 +
200 200  (((
201 201  Insert the NB-IoT Card get from your provider.
202 202  )))
... ... @@ -212,14 +212,18 @@
212 212  
213 213  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
214 214  
273 +
215 215  (((
216 216  (((
217 217  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 +
218 218  )))
219 219  )))
220 220  
221 221  [[image:1657351312545-300.png]]
222 222  
284 +
223 223  **Connection:**
224 224  
225 225   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -243,8 +243,9 @@
243 243  
244 244  [[image:1657329814315-101.png]]
245 245  
308 +
246 246  (((
247 -(% 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]]**
248 248  )))
249 249  
250 250  
... ... @@ -251,9 +251,10 @@
251 251  
252 252  === 2.2.5  Use CoAP protocol to uplink data ===
253 253  
254 -(% 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  
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/]]**
256 256  
320 +
257 257  (((
258 258  **Use below commands:**
259 259  )))
... ... @@ -356,51 +356,83 @@
356 356  == 2.3  Uplink Payload ==
357 357  
358 358  
359 -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 +)))
360 360  
361 361  
428 +(((
362 362  For example:
430 +)))
363 363  
364 - (% 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 +)))
365 365  
366 366  
437 +(((
367 367  The uplink payloads are composed in  ASCII String. For example:
439 +)))
368 368  
441 +(((
369 369  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
443 +)))
370 370  
445 +(((
371 371  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
447 +)))
372 372  
373 373  
450 +(((
374 374  (% style="color:red" %)**NOTE:**
452 +)))
375 375  
376 376  (% style="color:red" %)
377 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
378 -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.
379 379  
380 380  
381 381  
463 +
464 +)))
465 +
382 382  === 2.3.1  Payload Analyze ===
383 383  
384 384  N95S31B uplink payload includes in total 21 bytes
385 385  
386 386  
387 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
388 388  |=(% style="width: 60px;" %)(((
389 389  **Size(bytes)**
390 -)))|=(% 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**
391 -|(% 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" %)(((
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**
475 +|(% 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 +(((
392 392  Reserve/ Same as NBSN95 CFGMOD=1
478 +)))
393 393  
480 +(((
394 394  No function here.
482 +)))
395 395  )))|(% style="width:77px" %)(((
396 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
484 +(((
485 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
486 +)))
397 397  
488 +(((
398 398  By SHT31
490 +)))
399 399  )))|(% style="width:80px" %)(((
400 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
492 +(((
493 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
494 +)))
401 401  
496 +(((
402 402  By SHT31
403 403  )))
499 +)))
404 404  
405 405  (((
406 406  (((
... ... @@ -459,15 +459,25 @@
459 459  
460 460  === 2.3.3  Version Info ===
461 461  
462 -
558 +(((
463 463  These bytes include the hardware and software version.
560 +)))
464 464  
562 +(((
465 465  Higher byte: Specify hardware version: always 0x00 for N95S31B
564 +)))
466 466  
566 +(((
467 467  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
568 +)))
468 468  
570 +(((
571 +
572 +)))
469 469  
574 +(((
470 470  For example: 0x00 6E: this device is N95S31B with firmware version 110.
576 +)))
471 471  
472 472  (((
473 473  
... ... @@ -538,7 +538,7 @@
538 538  
539 539  == 2.4  Downlink Payload ==
540 540  
541 -By default, NDDS75 prints the downlink payload to console port.
647 +By default, N95S31B prints the downlink payload to console port.
542 542  
543 543  [[image:image-20220709100028-1.png]]
544 544  
... ... @@ -576,7 +576,7 @@
576 576  )))
577 577  
578 578  (((
579 -If payload = 0x04FF, it will reset the NDDS75
685 +If payload = 0x04FF, it will reset the N95S31B
580 580  )))
581 581  
582 582  
... ... @@ -756,8 +756,10 @@
756 756  (((
757 757  
758 758  
865 +(((
759 759  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
760 760  )))
868 +)))
761 761  
762 762  
763 763  
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