Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.24 >
edited by Xiaoling
on 2022/07/09 18:19
To version < 118.7 >
edited by Xiaoling
on 2022/07/12 17:35
>
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  )))
... ... @@ -53,6 +53,8 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
69 +
70 +
56 56  == 1.3  Specification ==
57 57  
58 58  
... ... @@ -72,7 +72,6 @@
72 72  
73 73  (% style="color:#037691" %)**Battery:**
74 74  
75 -
76 76  * Li/SOCI2 un-chargeable battery
77 77  * Capacity: 8500mAh
78 78  * Self Discharge: <1% / Year @ 25°C
... ... @@ -79,6 +79,8 @@
79 79  * Max continuously current: 130mA
80 80  * Max boost current: 2A, 1 second
81 81  
96 +
97 +
82 82  == ​1.4  Applications ==
83 83  
84 84  * Smart Buildings & Home Automation
... ... @@ -92,7 +92,7 @@
92 92  ​
93 93  
94 94  
95 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
96 96  
97 97  N95S31B use the mother board from NBSN95 which as below.
98 98  
... ... @@ -107,9 +107,13 @@
107 107  
108 108  === 1.5.2 BOOT MODE / SW1 ===
109 109  
126 +(((
110 110  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.
128 +)))
111 111  
130 +(((
112 112  2) Flash: work mode, device starts to work and send out console output for further debug
132 +)))
113 113  
114 114  
115 115  
... ... @@ -126,6 +126,7 @@
126 126  1. When boot the device in flash mode
127 127  1. Send an uplink packet
128 128  
149 +
129 129  = 2.  Use N95S31B to communicate with IoT Server =
130 130  
131 131  == 2.1  How it works ==
... ... @@ -144,7 +144,7 @@
144 144  
145 145  )))
146 146  
147 -[[image:1657350248151-650.png]]
168 +[[image:1657520100595-569.png]]
148 148  
149 149  (((
150 150  
... ... @@ -163,23 +163,45 @@
163 163  === 2.2.1 Test Requirement ===
164 164  
165 165  
187 +(((
166 166  To use N95S31B in your city, make sure meet below requirements:
189 +)))
167 167  
168 -* Your local operator has already distributed a NB-IoT Network there.
169 -* The local NB-IoT network used the band that N95S31B supports.
170 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
191 +* (((
192 +Your local operator has already distributed a NB-IoT Network there.
193 +)))
194 +* (((
195 +The local NB-IoT network used the band that N95S31B supports.
196 +)))
197 +* (((
198 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +)))
171 171  
201 +(((
172 172  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
203 +)))
173 173  
205 +(((
174 174  N95S31B supports different communication protocol such as :
207 +)))
175 175  
176 176  (((
177 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
178 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
179 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
180 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
210 +* (((
211 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
212 +)))
213 +* (((
214 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
215 +)))
216 +* (((
217 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
218 +)))
219 +* (((
220 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
221 +)))
181 181  
223 +(((
182 182  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.
225 +)))
183 183  
184 184  
185 185  )))
... ... @@ -349,29 +349,49 @@
349 349  == 2.3  Uplink Payload ==
350 350  
351 351  
352 -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.
395 +(((
396 +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.
397 +)))
353 353  
354 354  
400 +(((
355 355  For example:
402 +)))
356 356  
357 - (% 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.
404 +(((
405 + (% 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.
406 +)))
358 358  
359 359  
409 +(((
360 360  The uplink payloads are composed in  ASCII String. For example:
411 +)))
361 361  
413 +(((
362 362  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
415 +)))
363 363  
417 +(((
364 364  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
419 +)))
365 365  
366 366  
422 +(((
367 367  (% style="color:red" %)**NOTE:**
424 +)))
368 368  
369 369  (% style="color:red" %)
370 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
371 -1. By default, the device will send an uplink message every 1 hour.
427 +1. (((
428 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
429 +)))
430 +1. (((
431 +By default, the device will send an uplink message every 1 hour.
372 372  
373 373  
374 374  
435 +
436 +)))
437 +
375 375  === 2.3.1  Payload Analyze ===
376 376  
377 377  N95S31B uplink payload includes in total 21 bytes
... ... @@ -464,15 +464,25 @@
464 464  
465 465  === 2.3.3  Version Info ===
466 466  
467 -
530 +(((
468 468  These bytes include the hardware and software version.
532 +)))
469 469  
534 +(((
470 470  Higher byte: Specify hardware version: always 0x00 for N95S31B
536 +)))
471 471  
538 +(((
472 472  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
540 +)))
473 473  
542 +(((
543 +
544 +)))
474 474  
546 +(((
475 475  For example: 0x00 6E: this device is N95S31B with firmware version 110.
548 +)))
476 476  
477 477  (((
478 478  
... ... @@ -543,7 +543,7 @@
543 543  
544 544  == 2.4  Downlink Payload ==
545 545  
546 -By default, NDDS75 prints the downlink payload to console port.
619 +By default, N95S31B prints the downlink payload to console port.
547 547  
548 548  [[image:image-20220709100028-1.png]]
549 549  
... ... @@ -581,7 +581,7 @@
581 581  )))
582 582  
583 583  (((
584 -If payload = 0x04FF, it will reset the NDDS75
657 +If payload = 0x04FF, it will reset the N95S31B
585 585  )))
586 586  
587 587  
... ... @@ -761,8 +761,10 @@
761 761  (((
762 762  
763 763  
837 +(((
764 764  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
765 765  )))
840 +)))
766 766  
767 767  
768 768  
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