Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 124.1 >
edited by David Huang
on 2022/09/08 16:38
To version < 125.3 >
edited by Xiaoling
on 2022/09/09 15:56
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -68,6 +68,7 @@
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
71 +
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -93,6 +93,7 @@
93 93  * Max continuously current: 130mA
94 94  * Max boost current: 2A, 1 second
95 95  
97 +
96 96  == ​1.4  Applications ==
97 97  
98 98  
... ... @@ -108,6 +108,7 @@
108 108  
109 109  
110 110  
113 +
111 111  == 1.5  Pin Definitions & Switch ==
112 112  
113 113  
... ... @@ -153,6 +153,7 @@
153 153  1. When boot the device in flash mode
154 154  1. Send an uplink packet
155 155  
159 +
156 156  = 2.  Use N95S31B to communicate with IoT Server =
157 157  
158 158  
... ... @@ -406,16 +406,21 @@
406 406  
407 407  )))
408 408  
409 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
413 +(((
414 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
415 +)))
410 410  
411 -**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).**
417 +(((
418 +(% 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).**
419 +)))
412 412  
413 413  
422 +
414 414  == 2.3  Uplink Payload ==
415 415  
416 416  
417 417  (((
418 -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.
427 +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.
419 419  )))
420 420  
421 421  
... ... @@ -460,14 +460,17 @@
460 460  === 2.3.1  Payload Analyze ===
461 461  
462 462  
472 +==== 2.3.1.1  Before Firmware v1.2 ====
473 +
474 +
463 463  N95S31B uplink payload includes in total 21 bytes
464 464  
465 465  
466 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
478 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
467 467  |=(% style="width: 60px;" %)(((
468 468  **Size(bytes)**
469 -)))|=(% 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**
470 -|(% 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" %)(((
481 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
482 +|(% 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:174px" %)(((
471 471  (((
472 472  Reserve/ Same as NBSN95 CFGMOD=1
473 473  )))
... ... @@ -475,7 +475,7 @@
475 475  (((
476 476  No function here.
477 477  )))
478 -)))|(% style="width:77px" %)(((
490 +)))|(% style="width:106px" %)(((
479 479  (((
480 480  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
481 481  )))
... ... @@ -483,7 +483,7 @@
483 483  (((
484 484  By SHT31
485 485  )))
486 -)))|(% style="width:80px" %)(((
498 +)))|(% style="width:85px" %)(((
487 487  (((
488 488  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
489 489  )))
... ... @@ -507,53 +507,80 @@
507 507  
508 508  The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
509 509  
510 -* Device ID: 0x724031607457 = 724031607457
511 -* Version: 0x006e=110=1.1.0
522 +* Device ID:  0x724031607457 = 724031607457
512 512  
513 -* BAT: 0x0ccd = 3277 mV = 3.277V
514 -* Signal: 0x1b = 27
515 -* Model: 0x01 = 1
524 +* Version:  0x006e=110=1.1.0
525 +
526 +* BAT:  0x0ccd = 3277 mV = 3.277V
527 +
528 +* Signal:  0x1b = 27
529 +
530 +* Model:  0x01 = 1
531 +
516 516  * 0x00dc000ccc= reserve, ignore in N95S31B
517 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
518 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
519 519  
534 +* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
535 +
536 +* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
537 +
520 520  (((
521 521  
522 -)))
523 523  
524 -(((
525 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
541 +
542 +
526 526  )))
527 527  
545 +==== 2.3.1.2 Since Firmware v1.2 ====
546 +
547 +
528 528  In this mode, uplink payload includes 91 bytes in total by default.
529 529  
530 530  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.
531 531  
532 -|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
534 534  
553 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
554 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
555 +|(% 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 .....
556 +
535 535  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
536 536  
559 +
537 537  [[image:image-20220908154949-1.png]]
538 538  
562 +
539 539  The payload is ASCII string, representative same HEX:
540 540  
541 541  0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
542 542  
543 -* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 -* (% style="color:blue" %) Version: 0x000c=120=1.2
545 -* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 -* (% style="color:red" %) Singal: 0x0c = 12
547 -* (% style="color:blue" %) Mod: 0x01 = 1
567 +* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
568 +
569 +* (% style="color:blue" %)Version: 0x000c=120=1.2
570 +
571 +* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
572 +
573 +* (% style="color:red" %)Singal: 0x0c = 12
574 +
575 +* (% style="color:blue" %)Mod: 0x01 = 1
576 +
548 548  * TemDS18B20: 0x0000= 0 = 0
578 +
549 549  * (% style="color:green" %)Interrupt: 0x00= 0
580 +
550 550  * (% style="color:green" %)adc: 0x0030= 48
582 +
551 551  * SHTTEM: 0x0114= 276 = 27.6
584 +
552 552  * SHTHUM:0x0231 =561=56.1%
553 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
586 +
587 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
588 +
554 554  * (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
590 +
555 555  * 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
556 556  
593 +
594 +
595 +
557 557  === 2.3.2  Device ID ===
558 558  
559 559  
... ... @@ -1055,4 +1055,3 @@
1055 1055  
1056 1056  * 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.
1057 1057  * 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]]
1058 -

Applications

Navigation

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