Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.21 >
edited by Xiaoling
on 2022/07/09 18:17
To version < 130.4 >
edited by Xiaoling
on 2023/04/28 13:48
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,29 +19,34 @@
19 19  
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 -(((
23 -
24 24  
23 +(((
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*.
25 +)))
26 26  
27 +(((
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.
29 +)))
28 28  
31 +(((
29 29  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
33 +)))
30 30  
35 +(((
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).
37 +)))
32 32  
33 -
39 +(((
34 34  ~* make sure you have NB-IoT coverage locally.
35 -
36 -
37 37  )))
38 38  
43 +
39 39  [[image:1657348284168-431.png]]
40 40  
41 41  
42 -
43 43  == 1.2 ​ Features ==
44 44  
49 +
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
... ... @@ -53,6 +53,7 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
61 +
56 56  == 1.3  Specification ==
57 57  
58 58  
... ... @@ -63,16 +63,15 @@
63 63  
64 64  (% style="color:#037691" %)**NB-IoT Spec:**
65 65  
66 -* - B1 @H-FDD: 2100MHz
67 -* - B3 @H-FDD: 1800MHz
68 -* - B8 @H-FDD: 900MHz
69 -* - B5 @H-FDD: 850MHz
70 -* - B20 @H-FDD: 800MHz
71 -* - B28 @H-FDD: 700MHz
72 +* B1 @H-FDD: 2100MHz
73 +* B3 @H-FDD: 1800MHz
74 +* B8 @H-FDD: 900MHz
75 +* B5 @H-FDD: 850MHz
76 +* B20 @H-FDD: 800MHz
77 +* B28 @H-FDD: 700MHz
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,8 +79,10 @@
79 79  * Max continuously current: 130mA
80 80  * Max boost current: 2A, 1 second
81 81  
87 +
82 82  == ​1.4  Applications ==
83 83  
90 +
84 84  * Smart Buildings & Home Automation
85 85  * Logistics and Supply Chain Management
86 86  * Smart Metering
... ... @@ -92,40 +92,49 @@
92 92  ​
93 93  
94 94  
95 -== 1.5  Pin Definitions ==
102 +== 1.5  Pin Definitions & Switch ==
96 96  
104 +
97 97  N95S31B use the mother board from NBSN95 which as below.
98 98  
107 +
99 99  [[image:image-20220709144723-1.png]]
100 100  
101 101  
102 102  === 1.5.1 Jumper JP2 ===
103 103  
113 +
104 104  Power on Device when put this jumper.
105 105  
106 106  
107 -
108 108  === 1.5.2 BOOT MODE / SW1 ===
109 109  
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.
111 111  
112 -2) Flash: work mode, device starts to work and send out console output for further debug
120 +(((
121 +**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.
122 +)))
113 113  
124 +(((
125 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
126 +)))
114 114  
115 115  
116 116  === 1.5.3 Reset Button ===
117 117  
131 +
118 118  Press to reboot the device.
119 119  
120 120  
121 -
122 122  === 1.5.4 LED ===
123 123  
137 +
124 124  It will flash:
125 125  
126 -1. When boot the device in flash mode
127 -1. Send an uplink packet
140 +1.  When boot the device in flash mode
128 128  
142 +2.  Send an uplink packet
143 +
144 +
129 129  = 2.  Use N95S31B to communicate with IoT Server =
130 130  
131 131  == 2.1  How it works ==
... ... @@ -144,16 +144,14 @@
144 144  
145 145  )))
146 146  
147 -[[image:1657350248151-650.png]]
163 +[[image:1657520100595-569.png]]
148 148  
149 149  (((
150 150  
151 151  )))
152 152  
153 -
154 154  == 2.2 ​ Configure the N95S31B ==
155 155  
156 -
157 157  === 2.2.1  Power On N95S31B ===
158 158  
159 159  
... ... @@ -160,26 +160,48 @@
160 160  [[image:image-20220709150546-2.png]]
161 161  
162 162  
163 -=== 2.2.1 Test Requirement ===
177 +=== 2.2.2 Test Requirement ===
164 164  
165 165  
180 +(((
166 166  To use N95S31B in your city, make sure meet below requirements:
182 +)))
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.
184 +* (((
185 +Your local operator has already distributed a NB-IoT Network there.
186 +)))
187 +* (((
188 +The local NB-IoT network used the band that N95S31B supports.
189 +)))
190 +* (((
191 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
192 +)))
171 171  
194 +(((
172 172  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
196 +)))
173 173  
198 +(((
174 174  N95S31B supports different communication protocol such as :
200 +)))
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(%%))
203 +* (((
204 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
205 +)))
206 +* (((
207 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
208 +)))
209 +* (((
210 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
211 +)))
212 +* (((
213 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
214 +)))
181 181  
216 +(((
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.
218 +)))
183 183  
184 184  
185 185  )))
... ... @@ -187,9 +187,9 @@
187 187  [[image:1657350625843-586.png]]
188 188  
189 189  
190 -
191 191  === 2.2.3  Insert SIM card ===
192 192  
228 +
193 193  (((
194 194  Insert the NB-IoT Card get from your provider.
195 195  )))
... ... @@ -202,26 +202,29 @@
202 202  [[image:1657351240556-536.png]]
203 203  
204 204  
205 -
206 206  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
207 207  
243 +
208 208  (((
209 209  (((
210 210  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.
247 +
248 +
211 211  )))
212 212  )))
213 213  
214 214  [[image:1657351312545-300.png]]
215 215  
216 -**Connection:**
217 217  
218 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
255 +(% style="color:blue" %)**Connection:**
219 219  
220 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
257 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
221 221  
222 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
259 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
223 223  
261 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
224 224  
263 +
225 225  In the PC, use below serial tool settings:
226 226  
227 227  * Baud:  (% style="color:green" %)**9600**
... ... @@ -236,17 +236,18 @@
236 236  
237 237  [[image:1657329814315-101.png]]
238 238  
278 +
239 239  (((
240 -(% 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/]]
280 +(% 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]]**
241 241  )))
242 242  
243 243  
244 -
245 245  === 2.2.5  Use CoAP protocol to uplink data ===
246 246  
247 -(% 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/]]
248 248  
287 +(% 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/]]**
249 249  
289 +
250 250  (((
251 251  **Use below commands:**
252 252  )))
... ... @@ -255,10 +255,10 @@
255 255  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
256 256  )))
257 257  * (((
258 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
298 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
259 259  )))
260 260  * (((
261 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
301 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
262 262  )))
263 263  
264 264  (((
... ... @@ -277,7 +277,6 @@
277 277  [[image:1657352185396-303.png]]
278 278  
279 279  
280 -
281 281  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
282 282  
283 283  
... ... @@ -291,18 +291,18 @@
291 291  [[image:1657352403317-397.png]]
292 292  
293 293  
294 -
295 295  === 2.2.7  Use MQTT protocol to uplink data ===
296 296  
335 +
297 297  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
298 298  
299 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
300 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
301 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
302 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
303 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
304 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
305 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
338 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
339 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
340 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
341 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
342 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
343 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
344 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
306 306  
307 307  [[image:1657352634421-276.png]]
308 308  
... ... @@ -309,19 +309,19 @@
309 309  
310 310  [[image:1657352645687-385.png]]
311 311  
351 +
312 312  (((
313 313  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.
314 314  )))
315 315  
316 -
317 317  (((
318 318  MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
319 319  )))
320 320  
321 321  
322 -
323 323  === 2.2.8  Use TCP protocol to uplink data ===
324 324  
363 +
325 325  This feature is supported since firmware version v110
326 326  
327 327  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -333,9 +333,9 @@
333 333  [[image:1657352914475-252.png]]
334 334  
335 335  
336 -
337 337  === 2.2.9  Change Update Interval ===
338 338  
377 +
339 339  User can use below command to change the (% style="color:green" %)**uplink interval**.
340 340  
341 341  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -344,45 +344,71 @@
344 344  
345 345  )))
346 346  
386 +(((
387 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
388 +)))
347 347  
390 +(((
391 +(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
392 +)))
348 348  
394 +
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.
398 +(((
399 +N95S31B has different working modes for the connections of different types 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.
400 +)))
353 353  
354 354  
403 +(((
355 355  For example:
405 +)))
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.
407 +(((
408 + (% 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.
409 +)))
358 358  
359 359  
412 +(((
360 360  The uplink payloads are composed in  ASCII String. For example:
414 +)))
361 361  
416 +(((
362 362  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
418 +)))
363 363  
420 +(((
364 364  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
422 +)))
365 365  
366 366  
425 +(((
367 367  (% style="color:red" %)**NOTE:**
427 +)))
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.
430 +1. (((
431 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
432 +)))
433 +1. (((
434 +**By default, the device will send an uplink message every 1 hour.**
372 372  
373 373  
437 +
438 +)))
374 374  
375 -
376 376  === 2.3.1  Payload Analyze ===
377 377  
442 +==== 2.3.1.1  Before Firmware v1.2 ====
443 +
444 +
378 378  N95S31B uplink payload includes in total 21 bytes
379 379  
380 380  
381 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
382 -|=(% style="width: 60px;" %)(((
383 -**Size(bytes)**
384 -)))|=(% 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**
385 -|(% 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" %)(((
448 +(% border="1" style="background-color:#f2f2f2; width:520px" %)
449 +|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2**
450 +|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
386 386  (((
387 387  Reserve/ Same as NBSN95 CFGMOD=1
388 388  )))
... ... @@ -390,7 +390,7 @@
390 390  (((
391 391  No function here.
392 392  )))
393 -)))|(% style="width:77px" %)(((
458 +)))|(% style="width:102px" %)(((
394 394  (((
395 395  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
396 396  )))
... ... @@ -398,7 +398,7 @@
398 398  (((
399 399  By SHT31
400 400  )))
401 -)))|(% style="width:80px" %)(((
466 +)))|(% style="width:81px" %)(((
402 402  (((
403 403  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
404 404  )))
... ... @@ -409,6 +409,8 @@
409 409  )))
410 410  
411 411  (((
477 +
478 +
412 412  (((
413 413  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
414 414  )))
... ... @@ -418,29 +418,88 @@
418 418  [[image:1657354294009-643.png]]
419 419  
420 420  
421 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
488 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
422 422  
423 -* Device ID: 0x724031607457 = 724031607457
424 -* Version: 0x006e=110=1.1.0
490 +**where:**
425 425  
426 -* BAT: 0x0ccd = 3277 mV = 3.277V
427 -* Signal: 0x1b = 27
428 -* Model: 0x01 = 1
429 -* 0x00dc000ccc= reserve, ignore in N95S31B
430 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
431 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
492 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
432 432  
494 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
495 +
496 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
497 +
498 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
499 +
500 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
501 +
502 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
503 +
504 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
505 +
506 +* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
507 +
433 433  (((
434 434  
435 -)))
436 436  
437 -(((
438 438  
439 439  )))
440 440  
514 +==== 2.3.1.2 Since Firmware v1.2 ====
441 441  
516 +
517 +In this mode, uplink payload includes 91 bytes in total by default.
518 +
519 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
520 +
521 +
522 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
523 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4**
524 +|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
525 +
526 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
527 +
528 +
529 +[[image:image-20220908154949-1.png]]
530 +
531 +
532 +The payload is ASCII string, representative same HEX:
533 +
534 +**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
535 +
536 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
537 +
538 +**where:**
539 +
540 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
541 +
542 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
543 +
544 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
545 +
546 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
547 +
548 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
549 +
550 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
551 +
552 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
553 +
554 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
555 +
556 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
557 +
558 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
559 +
560 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
561 +
562 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
563 +
564 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
565 +
566 +
442 442  === 2.3.2  Device ID ===
443 443  
569 +
444 444  (((
445 445  By default, the Device ID equal to the last 6 bytes of IMEI.
446 446  )))
... ... @@ -447,10 +447,12 @@
447 447  
448 448  (((
449 449  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
576 +
577 +
450 450  )))
451 451  
452 452  (((
453 -**Example:**
581 +(% style="color:blue" %)**Example:**
454 454  )))
455 455  
456 456  (((
... ... @@ -458,30 +458,54 @@
458 458  )))
459 459  
460 460  (((
461 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
589 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
590 +
591 +
462 462  )))
463 463  
594 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
464 464  
465 465  
597 +By default, the Device ID equal to the last 15 bits of IMEI.
598 +
599 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
600 +
601 +
602 +(% style="color:blue" %)**Example:**
603 +
604 +AT+DEUI=868411056754138
605 +
606 +
466 466  === 2.3.3  Version Info ===
467 467  
468 468  
610 +(((
469 469  These bytes include the hardware and software version.
612 +)))
470 470  
471 -Higher byte: Specify hardware version: always 0x00 for N95S31B
614 +(((
615 +**Higher byte:** Specify hardware version: always 0x00 for N95S31B
616 +)))
472 472  
473 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
618 +(((
619 +**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
620 +)))
474 474  
622 +(((
623 +
624 +)))
475 475  
626 +(((
476 476  For example: 0x00 6E: this device is N95S31B with firmware version 110.
628 +)))
477 477  
478 478  (((
479 479  
480 480  )))
481 481  
482 -
483 483  === 2.3.4  Battery Info ===
484 484  
636 +
485 485  (((
486 486  Ex1: 0x0B45 = 2885mV
487 487  )))
... ... @@ -491,9 +491,9 @@
491 491  )))
492 492  
493 493  
494 -
495 495  === 2.3.5  Signal Strength ===
496 496  
648 +
497 497  (((
498 498  NB-IoT Network signal Strength.
499 499  )))
... ... @@ -523,9 +523,9 @@
523 523  )))
524 524  
525 525  
526 -
527 527  === 2.3.6  Temperature & Humidity ===
528 528  
680 +
529 529  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
530 530  
531 531  [[image:image-20220709161741-3.png]]
... ... @@ -541,11 +541,11 @@
541 541  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
542 542  
543 543  
544 -
545 545  == 2.4  Downlink Payload ==
546 546  
547 -By default, NDDS75 prints the downlink payload to console port.
548 548  
699 +By default, N95S31B prints the downlink payload to console port.
700 +
549 549  [[image:image-20220709100028-1.png]]
550 550  
551 551  
... ... @@ -582,7 +582,7 @@
582 582  )))
583 583  
584 584  (((
585 -If payload = 0x04FF, it will reset the NDDS75
737 +If payload = 0x04FF, it will reset the N95S31B
586 586  )))
587 587  
588 588  
... ... @@ -593,69 +593,76 @@
593 593  )))
594 594  
595 595  
748 +== 2.5  Humidity and Temperature alarm function ==
596 596  
597 -== 2.5  ​Battery Analysis ==
598 598  
599 -=== 2.5.1  ​Battery Type ===
751 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
600 600  
601 601  
602 -(((
603 -The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
604 -)))
754 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
605 605  
606 -(((
607 -The battery is designed to last for several years depends on the actually use environment and update interval. 
608 -)))
609 609  
610 -(((
611 -The battery related documents as below:
612 -)))
757 +² When min=0, and max≠0, Alarm higher than max
613 613  
614 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
615 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
616 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
759 +² When min≠0, and max=0, Alarm lower than min
617 617  
618 -(((
619 -[[image:image-20220709101450-2.png]]
620 -)))
761 +² When min≠0 and max≠0, Alarm higher than max or lower than min
621 621  
622 622  
764 + (% style="color:blue" %)**Example:**
623 623  
624 -=== 2.5.2  Power consumption Analyze ===
766 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
625 625  
626 -(((
627 -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.
628 -)))
629 629  
630 -(((
631 -
632 -)))
769 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
633 633  
771 +² When min=0, and max≠0, Alarm higher than max
634 634  
635 -=== 2.5.3  ​Battery Note ===
773 +² When min≠0, and max=0, Alarm lower than min
636 636  
637 -(((
638 -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.
639 -)))
775 +² When min≠0 and max≠0, Alarm higher than max or lower than min
640 640  
641 641  
778 +**~ (% style="color:blue" %)Example:(%%)**
642 642  
643 -=== 2.5.4  Replace the battery ===
780 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
644 644  
645 645  
646 -(((
647 -You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
648 -)))
783 +== 2.6 Set the number of data to be uploaded and the recording time ==
649 649  
650 650  
651 -(((
652 -The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
653 -)))
786 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
654 654  
788 +* (% style="color:#037691" %)**AT+TR=900**     (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
789 +* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
655 655  
791 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
656 656  
793 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
794 +
795 +
796 +== 2.7 Read or Clear cached data ==
797 +
798 +
799 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
800 +
801 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
802 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
803 +
804 +[[image:image-20220908163102-2.png]]
805 +
806 +
807 +== 2.8 Battery & Power Consumption ==
808 +
809 +
810 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
811 +
812 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
813 +
814 +
657 657  = 3. ​ Access NB-IoT Module =
658 658  
817 +
659 659  (((
660 660  Users can directly access the AT command set of the NB-IoT module.
661 661  )))
... ... @@ -662,19 +662,21 @@
662 662  
663 663  (((
664 664  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/]] 
824 +
825 +
665 665  )))
666 666  
667 667  [[image:1657333200519-600.png]]
668 668  
669 669  
670 -
671 671  = 4.  Using the AT Commands =
672 672  
673 673  == 4.1  Access AT Commands ==
674 674  
675 -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/]]
676 676  
836 +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]]
677 677  
838 +
678 678  AT+<CMD>?  : Help on <CMD>
679 679  
680 680  AT+<CMD>         : Run <CMD>
... ... @@ -714,7 +714,24 @@
714 714  
715 715  AT+SERVADDR  : Server Address
716 716  
878 +AT+TR      : Get or Set record time
717 717  
880 +AT+APN     : Get or set the APN
881 +
882 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
883 +
884 +AT+DNSCFG  : Get or Set DNS Server
885 +
886 +AT+GETSENSORVALUE   : Returns the current sensor measurement
887 +
888 +AT+NOUD      : Get or Set the number of data to be uploaded
889 +
890 +AT+CDP     : Read or Clear cached data
891 +
892 +AT+SHTEMP: Get or Set alarm of temp
893 +
894 +AT+SHHUM: Get or Set alarm of moisture
895 +
718 718  (% style="color:#037691" %)**COAP Management**      
719 719  
720 720  AT+URI            : Resource parameters
... ... @@ -745,7 +745,6 @@
745 745  AT+PWORD  : Serial Access Password
746 746  
747 747  
748 -
749 749  = ​5.  FAQ =
750 750  
751 751  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -760,13 +760,12 @@
760 760  )))
761 761  
762 762  (((
763 -
940 +Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
764 764  
765 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
942 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
766 766  )))
767 767  
768 768  
769 -
770 770  = 6.  Trouble Shooting =
771 771  
772 772  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -776,14 +776,10 @@
776 776  **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
777 777  )))
778 778  
779 -(% class="wikigeneratedid" %)
780 -(((
781 -
782 -)))
783 783  
784 -
785 785  == 6.2  AT Command input doesn't work ==
786 786  
958 +
787 787  (((
788 788  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.
789 789  
... ... @@ -790,7 +790,12 @@
790 790  
791 791  )))
792 792  
965 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
793 793  
967 +
968 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
969 +
970 +
794 794  = 7. ​ Order Info =
795 795  
796 796  
... ... @@ -797,11 +797,6 @@
797 797  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
798 798  
799 799  
800 -(% class="wikigeneratedid" %)
801 -(((
802 -
803 -)))
804 -
805 805  = 8.  Packing Info =
806 806  
807 807  (((
... ... @@ -824,14 +824,13 @@
824 824  * Weight / pcs : 180g
825 825  )))
826 826  
827 -(((
828 -
829 829  
830 830  
831 -
832 -)))
833 -
834 834  = 9.  Support =
835 835  
1003 +
836 836  * 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.
1005 +
837 837  * 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]]
1007 +
1008 +
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
image-20221009001045-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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