Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.18 >
edited by Xiaoling
on 2022/07/09 18:08
To version < 115.35 >
edited by Xiaoling
on 2022/07/11 09:30
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,16 +22,29 @@
22 22  (((
23 23  
24 24  
25 +(((
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*.
27 +)))
26 26  
29 +(((
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.
31 +)))
28 28  
33 +(((
29 29  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 +)))
30 30  
37 +(((
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).
39 +)))
32 32  
41 +(((
42 +
43 +)))
33 33  
45 +(((
34 34  ~* make sure you have NB-IoT coverage locally.
47 +)))
35 35  
36 36  
37 37  )))
... ... @@ -55,6 +55,7 @@
55 55  
56 56  
57 57  
71 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -63,6 +63,7 @@
63 63  * Supply Voltage: 2.1v ~~ 3.6v
64 64  * Operating Temperature: -40 ~~ 85°C
65 65  
80 +
66 66  (% style="color:#037691" %)**NB-IoT Spec:**
67 67  
68 68  * - B1 @H-FDD: 2100MHz
... ... @@ -72,9 +72,9 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
90 +
75 75  (% style="color:#037691" %)**Battery:**
76 76  
77 -
78 78  * Li/SOCI2 un-chargeable battery
79 79  * Capacity: 8500mAh
80 80  * Self Discharge: <1% / Year @ 25°C
... ... @@ -83,6 +83,7 @@
83 83  
84 84  
85 85  
101 +
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -111,9 +111,13 @@
111 111  
112 112  === 1.5.2 BOOT MODE / SW1 ===
113 113  
130 +(((
114 114  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.
132 +)))
115 115  
134 +(((
116 116  2) Flash: work mode, device starts to work and send out console output for further debug
136 +)))
117 117  
118 118  
119 119  
... ... @@ -130,6 +130,9 @@
130 130  1. When boot the device in flash mode
131 131  1. Send an uplink packet
132 132  
153 +
154 +
155 +
133 133  = 2.  Use N95S31B to communicate with IoT Server =
134 134  
135 135  == 2.1  How it works ==
... ... @@ -167,23 +167,45 @@
167 167  === 2.2.1 Test Requirement ===
168 168  
169 169  
193 +(((
170 170  To use N95S31B in your city, make sure meet below requirements:
195 +)))
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.
197 +* (((
198 +Your local operator has already distributed a NB-IoT Network there.
199 +)))
200 +* (((
201 +The local NB-IoT network used the band that N95S31B supports.
202 +)))
203 +* (((
204 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
205 +)))
175 175  
207 +(((
176 176  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
209 +)))
177 177  
211 +(((
178 178  N95S31B supports different communication protocol such as :
213 +)))
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(%%))
216 +* (((
217 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
218 +)))
219 +* (((
220 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
221 +)))
222 +* (((
223 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
224 +)))
225 +* (((
226 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
227 +)))
185 185  
229 +(((
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.
231 +)))
187 187  
188 188  
189 189  )))
... ... @@ -353,28 +353,48 @@
353 353  == 2.3  Uplink Payload ==
354 354  
355 355  
401 +(((
356 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.
403 +)))
357 357  
358 358  
406 +(((
359 359  For example:
408 +)))
360 360  
410 +(((
361 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.
412 +)))
362 362  
363 363  
415 +(((
364 364  The uplink payloads are composed in  ASCII String. For example:
417 +)))
365 365  
419 +(((
366 366  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
421 +)))
367 367  
423 +(((
368 368  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
425 +)))
369 369  
370 370  
428 +(((
371 371  (% style="color:red" %)**NOTE:**
430 +)))
372 372  
373 373  (% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
375 -1. By default, the device will send an uplink message every 1 hour.
433 +1. (((
434 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
435 +)))
436 +1. (((
437 +By default, the device will send an uplink message every 1 hour.
438 +)))
376 376  
377 377  
441 +
442 +
378 378  === 2.3.1  Payload Analyze ===
379 379  
380 380  N95S31B uplink payload includes in total 21 bytes
... ... @@ -381,22 +381,34 @@
381 381  
382 382  
383 383  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
384 -|=(% style="width: 50px;" %)(((
449 +|=(% style="width: 60px;" %)(((
385 385  **Size(bytes)**
386 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 60px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**2**
451 +)))|=(% 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**
387 387  |(% 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" %)(((
453 +(((
388 388  Reserve/ Same as NBSN95 CFGMOD=1
455 +)))
389 389  
457 +(((
390 390  No function here.
459 +)))
391 391  )))|(% style="width:77px" %)(((
461 +(((
392 392  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
463 +)))
393 393  
465 +(((
394 394  By SHT31
467 +)))
395 395  )))|(% style="width:80px" %)(((
469 +(((
396 396  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
471 +)))
397 397  
473 +(((
398 398  By SHT31
399 399  )))
476 +)))
400 400  
401 401  (((
402 402  (((
... ... @@ -752,8 +752,10 @@
752 752  (((
753 753  
754 754  
832 +(((
755 755  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
756 756  )))
835 +)))
757 757  
758 758  
759 759  

Applications

Navigation

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