Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 113.1 >
edited by Xiaoling
on 2022/07/09 15:48
To version < 115.3 >
edited by Xiaoling
on 2022/07/09 16:59
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,7 +41,6 @@
41 41  
42 42  == 1.2 ​ Features ==
43 43  
44 -
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
... ... @@ -55,6 +55,7 @@
55 55  
56 56  
57 57  
57 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -83,6 +83,7 @@
83 83  
84 84  
85 85  
86 +
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -131,8 +131,6 @@
131 131  1. Send an uplink packet
132 132  
133 133  
134 -
135 -
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
138 138  == 2.1  How it works ==
... ... @@ -176,7 +176,6 @@
176 176  * The local NB-IoT network used the band that N95S31B supports.
177 177  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
178 178  
179 -
180 180  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181 181  
182 182  N95S31B supports different communication protocol such as :
... ... @@ -302,7 +302,7 @@
302 302  
303 303  === 2.2.7  Use MQTT protocol to uplink data ===
304 304  
305 -N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption.
303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
306 306  
307 307  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
308 308  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -309,8 +309,8 @@
309 309  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
310 310  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
311 311  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
312 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
313 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
314 314  
315 315  [[image:1657352634421-276.png]]
316 316  
... ... @@ -328,20 +328,21 @@
328 328  
329 329  
330 330  
331 -=== 2.2.7 Use TCP protocol to uplink data ===
329 +=== 2.2.8  Use TCP protocol to uplink data ===
332 332  
331 +This feature is supported since firmware version v110
333 333  
334 334  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
335 335  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
336 336  
337 -[[image:image-20220709093918-1.png]]
336 +[[image:1657352898400-901.png]]
338 338  
339 339  
340 -[[image:image-20220709093918-2.png]]
339 +[[image:1657352914475-252.png]]
341 341  
342 342  
343 343  
344 -=== 2.2.8 Change Update Interval ===
343 +=== 2.2.9  Change Update Interval ===
345 345  
346 346  User can use below command to change the (% style="color:green" %)**uplink interval**.
347 347  
... ... @@ -348,69 +348,92 @@
348 348  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
349 349  
350 350  (((
351 -(% style="color:red" %)**NOTE:**
350 +
352 352  )))
353 353  
354 -(((
355 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
356 -)))
357 357  
358 358  
359 -
360 360  == 2.3  Uplink Payload ==
361 361  
362 -In this mode, uplink payload includes in total 14 bytes
363 363  
358 +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.
364 364  
360 +
361 +For example:
362 +
363 + (% 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.
364 +
365 +
366 +The uplink payloads are composed in  ASCII String. For example:
367 +
368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
369 +
370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
371 +
372 +
373 +(% style="color:red" %)**NOTE:**
374 +
375 +(% style="color:red" %)
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
378 +
379 +
380 +
381 +=== 2.3.1  Payload Analyze ===
382 +
383 +N95S31B uplink payload includes in total 21 bytes
384 +
385 +
365 365  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
366 366  |=(% style="width: 60px;" %)(((
367 367  **Size(bytes)**
368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
389 +)))|=(% 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**
390 +|(% 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" %)(((
391 +Reserve/ Same as NBSN95 CFGMOD=1
370 370  
371 -(((
372 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
373 -)))
393 +No function here.
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
374 374  
397 +By SHT31
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
375 375  
376 -[[image:1657331036973-987.png]]
377 -
378 -(((
379 -The payload is ASCII string, representative same HEX:
401 +By SHT31
380 380  )))
381 381  
382 382  (((
383 -0x72403155615900640c6c19029200 where:
405 +(((
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
384 384  )))
385 -
386 -* (((
387 -Device ID: 0x724031556159 = 724031556159
388 388  )))
389 -* (((
390 -Version: 0x0064=100=1.0.0
391 -)))
392 392  
393 -* (((
394 -BAT: 0x0c6c = 3180 mV = 3.180V
395 -)))
396 -* (((
397 -Signal: 0x19 = 25
398 -)))
399 -* (((
400 -Distance: 0x0292= 658 mm
401 -)))
402 -* (((
403 -Interrupt: 0x00 = 0
404 404  
411 +[[image:1657354294009-643.png]]
405 405  
406 406  
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
415 +
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
418 +
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425 +
426 +(((
407 407  
408 408  )))
409 409  
410 -== 2.4  Payload Explanation and Sensor Interface ==
430 +(((
431 +
432 +)))
411 411  
412 412  
413 -=== 2.4.1  Device ID ===
435 +=== 2.3.2  Device ID ===
414 414  
415 415  (((
416 416  By default, the Device ID equal to the last 6 bytes of IMEI.
... ... @@ -434,20 +434,25 @@
434 434  
435 435  
436 436  
437 -=== 2.4.2  Version Info ===
459 +=== 2.3.3  Version Info ===
438 438  
439 -(((
440 -Specify the software version: 0x64=100, means firmware version 1.00.
441 -)))
442 442  
462 +These bytes include the hardware and software version.
463 +
464 +Higher byte: Specify hardware version: always 0x00 for N95S31B
465 +
466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
467 +
468 +
469 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
470 +
443 443  (((
444 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
472 +
445 445  )))
446 446  
447 447  
476 +=== 2.3.4  Battery Info ===
448 448  
449 -=== 2.4.3  Battery Info ===
450 -
451 451  (((
452 452  Ex1: 0x0B45 = 2885mV
453 453  )))
... ... @@ -458,7 +458,7 @@
458 458  
459 459  
460 460  
461 -=== 2.4.4  Signal Strength ===
488 +=== 2.3.5  Signal Strength ===
462 462  
463 463  (((
464 464  NB-IoT Network signal Strength.
... ... @@ -490,83 +490,24 @@
490 490  
491 491  
492 492  
493 -=== 2.4.5  Distance ===
520 +=== 2.3.6  Temperature & Humidity ===
494 494  
495 -Get the distance. Flat object range 280mm - 7500mm.
522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
496 496  
497 -(((
498 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
499 -)))
524 +[[image:image-20220709161741-3.png]]
500 500  
501 -(((
502 -(((
503 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
504 -)))
505 -)))
506 506  
507 -(((
508 -
509 -)))
527 +Convert the read byte to decimal and divide it by ten.
510 510  
511 -(((
512 -
513 -)))
514 514  
515 -=== 2.4.6  Digital Interrupt ===
530 +**Example:**
516 516  
517 -(((
518 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
519 -)))
532 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
520 520  
521 -(((
522 -The command is:
523 -)))
534 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
524 524  
525 -(((
526 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
527 -)))
528 528  
529 529  
530 -(((
531 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
532 -)))
533 -
534 -
535 -(((
536 -Example:
537 -)))
538 -
539 -(((
540 -0x(00): Normal uplink packet.
541 -)))
542 -
543 -(((
544 -0x(01): Interrupt Uplink Packet.
545 -)))
546 -
547 -
548 -
549 -=== 2.4.7  ​+5V Output ===
550 -
551 -(((
552 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
553 -)))
554 -
555 -
556 -(((
557 -The 5V output time can be controlled by AT Command.
558 -)))
559 -
560 -(((
561 -(% style="color:blue" %)**AT+5VT=1000**
562 -)))
563 -
564 -(((
565 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
566 -)))
567 -
568 -
569 -
570 570  == 2.5  Downlink Payload ==
571 571  
572 572  By default, NDDS75 prints the downlink payload to console port.
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content

Applications

Navigation

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