Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.30 >
edited by Xiaoling
on 2022/07/11 08:39
To version < 129.33 >
edited by Xiaoling
on 2022/12/30 11:21
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
58 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -68,7 +68,6 @@
68 68  
69 69  
70 70  
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -77,7 +77,6 @@
77 77  * Supply Voltage: 2.1v ~~ 3.6v
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
80 -
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 83  * - B1 @H-FDD: 2100MHz
... ... @@ -87,7 +87,6 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 -
91 91  (% style="color:#037691" %)**Battery:**
92 92  
93 93  * Li/SOCI2 un-chargeable battery
... ... @@ -98,9 +98,9 @@
98 98  
99 99  
100 100  
101 -
102 102  == ​1.4  Applications ==
103 103  
101 +
104 104  * Smart Buildings & Home Automation
105 105  * Logistics and Supply Chain Management
106 106  * Smart Metering
... ... @@ -112,47 +112,49 @@
112 112  ​
113 113  
114 114  
115 -== 1.5  Pin Definitions ==
113 +== 1.5  Pin Definitions & Switch ==
116 116  
115 +
117 117  N95S31B use the mother board from NBSN95 which as below.
118 118  
118 +
119 119  [[image:image-20220709144723-1.png]]
120 120  
121 121  
122 122  === 1.5.1 Jumper JP2 ===
123 123  
124 +
124 124  Power on Device when put this jumper.
125 125  
126 126  
127 -
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 +
130 130  (((
131 -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 +**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 132  )))
133 133  
134 134  (((
135 -2) Flash: work mode, device starts to work and send out console output for further debug
136 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
136 136  )))
137 137  
138 138  
139 -
140 140  === 1.5.3 Reset Button ===
141 141  
142 +
142 142  Press to reboot the device.
143 143  
144 144  
145 -
146 146  === 1.5.4 LED ===
147 147  
148 +
148 148  It will flash:
149 149  
150 -1. When boot the device in flash mode
151 -1. Send an uplink packet
151 +1.  When boot the device in flash mode
152 152  
153 +2.  Send an uplink packet
153 153  
154 154  
155 -
156 156  = 2.  Use N95S31B to communicate with IoT Server =
157 157  
158 158  == 2.1  How it works ==
... ... @@ -171,7 +171,7 @@
171 171  
172 172  )))
173 173  
174 -[[image:1657350248151-650.png]]
174 +[[image:1657520100595-569.png]]
175 175  
176 176  (((
177 177  
... ... @@ -180,7 +180,6 @@
180 180  
181 181  == 2.2 ​ Configure the N95S31B ==
182 182  
183 -
184 184  === 2.2.1  Power On N95S31B ===
185 185  
186 186  
... ... @@ -187,26 +187,48 @@
187 187  [[image:image-20220709150546-2.png]]
188 188  
189 189  
190 -=== 2.2.1 Test Requirement ===
189 +=== 2.2.2 Test Requirement ===
191 191  
192 192  
192 +(((
193 193  To use N95S31B in your city, make sure meet below requirements:
194 +)))
194 194  
195 -* Your local operator has already distributed a NB-IoT Network there.
196 -* The local NB-IoT network used the band that N95S31B supports.
197 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
196 +* (((
197 +Your local operator has already distributed a NB-IoT Network there.
198 +)))
199 +* (((
200 +The local NB-IoT network used the band that N95S31B supports.
201 +)))
202 +* (((
203 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
204 +)))
198 198  
206 +(((
199 199  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
208 +)))
200 200  
210 +(((
201 201  N95S31B supports different communication protocol such as :
212 +)))
202 202  
203 203  (((
204 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
205 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
206 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
207 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
215 +* (((
216 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
217 +)))
218 +* (((
219 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
220 +)))
221 +* (((
222 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
223 +)))
224 +* (((
225 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
226 +)))
208 208  
228 +(((
209 209  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.
230 +)))
210 210  
211 211  
212 212  )))
... ... @@ -214,9 +214,9 @@
214 214  [[image:1657350625843-586.png]]
215 215  
216 216  
217 -
218 218  === 2.2.3  Insert SIM card ===
219 219  
240 +
220 220  (((
221 221  Insert the NB-IoT Card get from your provider.
222 222  )))
... ... @@ -229,26 +229,29 @@
229 229  [[image:1657351240556-536.png]]
230 230  
231 231  
232 -
233 233  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
234 234  
255 +
235 235  (((
236 236  (((
237 237  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.
259 +
260 +
238 238  )))
239 239  )))
240 240  
241 241  [[image:1657351312545-300.png]]
242 242  
243 -**Connection:**
244 244  
245 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
267 +(% style="color:blue" %)**Connection:**
246 246  
247 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
269 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
248 248  
249 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
271 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
250 250  
273 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
251 251  
275 +
252 252  In the PC, use below serial tool settings:
253 253  
254 254  * Baud:  (% style="color:green" %)**9600**
... ... @@ -263,17 +263,18 @@
263 263  
264 264  [[image:1657329814315-101.png]]
265 265  
290 +
266 266  (((
267 -(% 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/]]
292 +(% 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]]**
268 268  )))
269 269  
270 270  
271 -
272 272  === 2.2.5  Use CoAP protocol to uplink data ===
273 273  
274 -(% 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/]]
275 275  
299 +(% 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/]]**
276 276  
301 +
277 277  (((
278 278  **Use below commands:**
279 279  )))
... ... @@ -282,10 +282,10 @@
282 282  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
283 283  )))
284 284  * (((
285 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
310 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
286 286  )))
287 287  * (((
288 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
313 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
289 289  )))
290 290  
291 291  (((
... ... @@ -304,7 +304,6 @@
304 304  [[image:1657352185396-303.png]]
305 305  
306 306  
307 -
308 308  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
309 309  
310 310  
... ... @@ -318,18 +318,18 @@
318 318  [[image:1657352403317-397.png]]
319 319  
320 320  
321 -
322 322  === 2.2.7  Use MQTT protocol to uplink data ===
323 323  
347 +
324 324  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
325 325  
326 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
327 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
328 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
329 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
330 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
331 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
332 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
350 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
351 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
352 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
353 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
354 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
355 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
356 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
333 333  
334 334  [[image:1657352634421-276.png]]
335 335  
... ... @@ -336,6 +336,7 @@
336 336  
337 337  [[image:1657352645687-385.png]]
338 338  
363 +
339 339  (((
340 340  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.
341 341  )))
... ... @@ -346,9 +346,9 @@
346 346  )))
347 347  
348 348  
349 -
350 350  === 2.2.8  Use TCP protocol to uplink data ===
351 351  
376 +
352 352  This feature is supported since firmware version v110
353 353  
354 354  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -360,9 +360,9 @@
360 360  [[image:1657352914475-252.png]]
361 361  
362 362  
363 -
364 364  === 2.2.9  Change Update Interval ===
365 365  
390 +
366 366  User can use below command to change the (% style="color:green" %)**uplink interval**.
367 367  
368 368  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -371,43 +371,71 @@
371 371  
372 372  )))
373 373  
399 +(((
400 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
401 +)))
374 374  
403 +(((
404 +(% 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).**
405 +)))
375 375  
407 +
376 376  == 2.3  Uplink Payload ==
377 377  
378 378  
379 -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.
411 +(((
412 +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.
413 +)))
380 380  
381 381  
416 +(((
382 382  For example:
418 +)))
383 383  
384 - (% 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.
420 +(((
421 + (% 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.
422 +)))
385 385  
386 386  
425 +(((
387 387  The uplink payloads are composed in  ASCII String. For example:
427 +)))
388 388  
429 +(((
389 389  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
431 +)))
390 390  
433 +(((
391 391  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
435 +)))
392 392  
393 393  
438 +(((
394 394  (% style="color:red" %)**NOTE:**
440 +)))
395 395  
396 396  (% style="color:red" %)
397 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
398 -1. By default, the device will send an uplink message every 1 hour.
443 +1. (((
444 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
445 +)))
446 +1. (((
447 +**By default, the device will send an uplink message every 1 hour.**
399 399  
400 400  
450 +
451 +)))
452 +
401 401  === 2.3.1  Payload Analyze ===
402 402  
455 +==== 2.3.1.1  Before Firmware v1.2 ====
456 +
457 +
403 403  N95S31B uplink payload includes in total 21 bytes
404 404  
405 405  
406 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
407 -|=(% style="width: 60px;" %)(((
408 -**Size(bytes)**
409 -)))|=(% 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**
410 -|(% 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" %)(((
461 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
462 +|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2**
463 +|(% 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" %)(((
411 411  (((
412 412  Reserve/ Same as NBSN95 CFGMOD=1
413 413  )))
... ... @@ -415,7 +415,7 @@
415 415  (((
416 416  No function here.
417 417  )))
418 -)))|(% style="width:77px" %)(((
471 +)))|(% style="width:102px" %)(((
419 419  (((
420 420  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
421 421  )))
... ... @@ -423,7 +423,7 @@
423 423  (((
424 424  By SHT31
425 425  )))
426 -)))|(% style="width:80px" %)(((
479 +)))|(% style="width:81px" %)(((
427 427  (((
428 428  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
429 429  )))
... ... @@ -434,6 +434,8 @@
434 434  )))
435 435  
436 436  (((
490 +
491 +
437 437  (((
438 438  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
439 439  )))
... ... @@ -443,29 +443,90 @@
443 443  [[image:1657354294009-643.png]]
444 444  
445 445  
446 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
501 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
447 447  
448 -* Device ID: 0x724031607457 = 724031607457
449 -* Version: 0x006e=110=1.1.0
503 +**where:**
450 450  
451 -* BAT: 0x0ccd = 3277 mV = 3.277V
452 -* Signal: 0x1b = 27
453 -* Model: 0x01 = 1
454 -* 0x00dc000ccc= reserve, ignore in N95S31B
455 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
456 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
505 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
457 457  
507 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
508 +
509 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
510 +
511 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
512 +
513 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
514 +
515 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
516 +
517 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
518 +
519 +* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
520 +
458 458  (((
459 459  
460 -)))
461 461  
462 -(((
524 +
463 463  
464 464  )))
465 465  
528 +==== 2.3.1.2 Since Firmware v1.2 ====
466 466  
530 +
531 +In this mode, uplink payload includes 91 bytes in total by default.
532 +
533 +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.
534 +
535 +
536 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
537 +|=(% 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**
538 +|=(% 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 .....
539 +
540 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
541 +
542 +
543 +[[image:image-20220908154949-1.png]]
544 +
545 +
546 +The payload is ASCII string, representative same HEX:
547 +
548 +**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__ **
549 +
550 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
551 +
552 +**where:**
553 +
554 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
555 +
556 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
557 +
558 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
559 +
560 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
561 +
562 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
563 +
564 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
565 +
566 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
567 +
568 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
569 +
570 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
571 +
572 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
573 +
574 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
575 +
576 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
577 +
578 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
579 +
580 +
581 +
467 467  === 2.3.2  Device ID ===
468 468  
584 +
469 469  (((
470 470  By default, the Device ID equal to the last 6 bytes of IMEI.
471 471  )))
... ... @@ -472,10 +472,12 @@
472 472  
473 473  (((
474 474  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
591 +
592 +
475 475  )))
476 476  
477 477  (((
478 -**Example:**
596 +(% style="color:blue" %)**Example:**
479 479  )))
480 480  
481 481  (((
... ... @@ -483,30 +483,54 @@
483 483  )))
484 484  
485 485  (((
486 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
604 +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.
605 +
606 +
487 487  )))
488 488  
609 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
489 489  
490 490  
612 +By default, the Device ID equal to the last 15 bits of IMEI.
613 +
614 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
615 +
616 +
617 +(% style="color:blue" %)**Example:**
618 +
619 +AT+DEUI=868411056754138
620 +
621 +
491 491  === 2.3.3  Version Info ===
492 492  
493 493  
625 +(((
494 494  These bytes include the hardware and software version.
627 +)))
495 495  
629 +(((
496 496  Higher byte: Specify hardware version: always 0x00 for N95S31B
631 +)))
497 497  
633 +(((
498 498  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
635 +)))
499 499  
637 +(((
638 +
639 +)))
500 500  
641 +(((
501 501  For example: 0x00 6E: this device is N95S31B with firmware version 110.
643 +)))
502 502  
503 503  (((
504 504  
505 505  )))
506 506  
507 -
508 508  === 2.3.4  Battery Info ===
509 509  
651 +
510 510  (((
511 511  Ex1: 0x0B45 = 2885mV
512 512  )))
... ... @@ -516,9 +516,9 @@
516 516  )))
517 517  
518 518  
519 -
520 520  === 2.3.5  Signal Strength ===
521 521  
663 +
522 522  (((
523 523  NB-IoT Network signal Strength.
524 524  )))
... ... @@ -548,9 +548,9 @@
548 548  )))
549 549  
550 550  
551 -
552 552  === 2.3.6  Temperature & Humidity ===
553 553  
695 +
554 554  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
555 555  
556 556  [[image:image-20220709161741-3.png]]
... ... @@ -566,11 +566,11 @@
566 566  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
567 567  
568 568  
569 -
570 570  == 2.4  Downlink Payload ==
571 571  
572 -By default, NDDS75 prints the downlink payload to console port.
573 573  
714 +By default, N95S31B prints the downlink payload to console port.
715 +
574 574  [[image:image-20220709100028-1.png]]
575 575  
576 576  
... ... @@ -607,7 +607,7 @@
607 607  )))
608 608  
609 609  (((
610 -If payload = 0x04FF, it will reset the NDDS75
752 +If payload = 0x04FF, it will reset the N95S31B
611 611  )))
612 612  
613 613  
... ... @@ -618,12 +618,70 @@
618 618  )))
619 619  
620 620  
763 +== 2.5  Humidity and Temperature alarm function ==
621 621  
622 -== 2.5  ​Battery Analysis ==
623 623  
624 -=== 2.5.1  ​Battery Type ===
766 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
625 625  
626 626  
769 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
770 +
771 +
772 +² When min=0, and max≠0, Alarm higher than max
773 +
774 +² When min≠0, and max=0, Alarm lower than min
775 +
776 +² When min≠0 and max≠0, Alarm higher than max or lower than min
777 +
778 +
779 + (% style="color:blue" %)**Example:**
780 +
781 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
782 +
783 +
784 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
785 +
786 +² When min=0, and max≠0, Alarm higher than max
787 +
788 +² When min≠0, and max=0, Alarm lower than min
789 +
790 +² When min≠0 and max≠0, Alarm higher than max or lower than min
791 +
792 +
793 +**~ (% style="color:blue" %)Example:(%%)**
794 +
795 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
796 +
797 +
798 +== 2.6 Set the number of data to be uploaded and the recording time ==
799 +
800 +
801 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
802 +
803 +* (% 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)
804 +* (% 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.
805 +
806 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
807 +
808 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
809 +
810 +
811 +== 2.7 Read or Clear cached data ==
812 +
813 +
814 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
815 +
816 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
817 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
818 +
819 +[[image:image-20220908163102-2.png]]
820 +
821 +
822 +== 2.8  ​Battery Analysis ==
823 +
824 +=== 2.8.1  ​Battery Type ===
825 +
826 +
627 627  (((
628 628  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.
629 629  )))
... ... @@ -645,11 +645,11 @@
645 645  )))
646 646  
647 647  
848 +=== 2.8.2  Power consumption Analyze ===
648 648  
649 -=== 2.5.2  Power consumption Analyze ===
650 650  
651 651  (((
652 -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.
852 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
653 653  )))
654 654  
655 655  (((
... ... @@ -656,8 +656,8 @@
656 656  
657 657  )))
658 658  
859 +=== 2.8.3  ​Battery Note ===
659 659  
660 -=== 2.5.3  ​Battery Note ===
661 661  
662 662  (((
663 663  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.
... ... @@ -664,10 +664,9 @@
664 664  )))
665 665  
666 666  
867 +=== 2.8.4  Replace the battery ===
667 667  
668 -=== 2.5.4  Replace the battery ===
669 669  
670 -
671 671  (((
672 672  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.
673 673  )))
... ... @@ -678,9 +678,9 @@
678 678  )))
679 679  
680 680  
681 -
682 682  = 3. ​ Access NB-IoT Module =
683 683  
882 +
684 684  (((
685 685  Users can directly access the AT command set of the NB-IoT module.
686 686  )))
... ... @@ -687,19 +687,21 @@
687 687  
688 688  (((
689 689  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/]] 
889 +
890 +
690 690  )))
691 691  
692 692  [[image:1657333200519-600.png]]
693 693  
694 694  
695 -
696 696  = 4.  Using the AT Commands =
697 697  
698 698  == 4.1  Access AT Commands ==
699 699  
700 -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/]]
701 701  
901 +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]]
702 702  
903 +
703 703  AT+<CMD>?  : Help on <CMD>
704 704  
705 705  AT+<CMD>         : Run <CMD>
... ... @@ -739,7 +739,24 @@
739 739  
740 740  AT+SERVADDR  : Server Address
741 741  
943 +AT+TR      : Get or Set record time
742 742  
945 +AT+APN     : Get or set the APN
946 +
947 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
948 +
949 +AT+DNSCFG  : Get or Set DNS Server
950 +
951 +AT+GETSENSORVALUE   : Returns the current sensor measurement
952 +
953 +AT+NOUD      : Get or Set the number of data to be uploaded
954 +
955 +AT+CDP     : Read or Clear cached data
956 +
957 +AT+SHTEMP: Get or Set alarm of temp
958 +
959 +AT+SHHUM: Get or Set alarm of moisture
960 +
743 743  (% style="color:#037691" %)**COAP Management**      
744 744  
745 745  AT+URI            : Resource parameters
... ... @@ -770,7 +770,6 @@
770 770  AT+PWORD  : Serial Access Password
771 771  
772 772  
773 -
774 774  = ​5.  FAQ =
775 775  
776 776  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -787,11 +787,12 @@
787 787  (((
788 788  
789 789  
790 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1007 +(((
1008 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
791 791  )))
1010 +)))
792 792  
793 793  
794 -
795 795  = 6.  Trouble Shooting =
796 796  
797 797  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -806,9 +806,9 @@
806 806  
807 807  )))
808 808  
809 -
810 810  == 6.2  AT Command input doesn't work ==
811 811  
1029 +
812 812  (((
813 813  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.
814 814  
... ... @@ -815,7 +815,6 @@
815 815  
816 816  )))
817 817  
818 -
819 819  = 7. ​ Order Info =
820 820  
821 821  
... ... @@ -822,11 +822,6 @@
822 822  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
823 823  
824 824  
825 -(% class="wikigeneratedid" %)
826 -(((
827 -
828 -)))
829 -
830 830  = 8.  Packing Info =
831 831  
832 832  (((
... ... @@ -852,11 +852,16 @@
852 852  (((
853 853  
854 854  
855 -
856 856  
857 857  )))
858 858  
859 859  = 9.  Support =
860 860  
1072 +
861 861  * 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.
862 862  * 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]]
1075 +
1076 +
1077 +
1078 +
1079 +
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