<
From version < 130.15 >
edited by Xiaoling
on 2023/04/28 15:52
To version < 130.1 >
edited by Bei Jinggeng
on 2023/04/19 14:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -19,6 +19,8 @@
19 19  
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 +(((
23 +
22 22  
23 23  (((
24 24  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*.
... ... @@ -37,13 +37,20 @@
37 37  )))
38 38  
39 39  (((
42 +
43 +)))
44 +
45 +(((
40 40  ~* make sure you have NB-IoT coverage locally.
41 41  )))
42 42  
49 +
50 +)))
43 43  
44 44  [[image:1657348284168-431.png]]
45 45  
46 46  
55 +
47 47  == 1.2 ​ Features ==
48 48  
49 49  
... ... @@ -59,7 +59,6 @@
59 59  * 8500mAh Battery for long term use
60 60  
61 61  
62 -
63 63  == 1.3  Specification ==
64 64  
65 65  
... ... @@ -86,7 +86,6 @@
86 86  * Max boost current: 2A, 1 second
87 87  
88 88  
89 -
90 90  == ​1.4  Applications ==
91 91  
92 92  
... ... @@ -168,6 +168,7 @@
168 168  
169 169  )))
170 170  
178 +
171 171  == 2.2 ​ Configure the N95S31B ==
172 172  
173 173  === 2.2.1  Power On N95S31B ===
... ... @@ -355,6 +355,7 @@
355 355  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.
356 356  )))
357 357  
366 +
358 358  (((
359 359  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.
360 360  )))
... ... @@ -407,7 +407,7 @@
407 407  )))
408 408  
409 409  (((
410 - (% 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.
419 + (% 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.
411 411  )))
412 412  
413 413  
... ... @@ -444,10 +444,11 @@
444 444  ==== 2.3.1.1  Before Firmware v1.2 ====
445 445  
446 446  
447 -N95S31B uplink payload includes in total 21 bytes.
456 +N95S31B uplink payload includes in total 21 bytes
448 448  
449 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
450 -|=(% 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**
458 +
459 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
460 +|=(% 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**
451 451  |(% 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" %)(((
452 452  (((
453 453  Reserve/ Same as NBSN95 CFGMOD=1
... ... @@ -520,8 +520,8 @@
520 520  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.
521 521  
522 522  
523 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
524 -|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**4**
533 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
534 +|=(% 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**
525 525  |=(% 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 .....
526 526  
527 527  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
... ... @@ -565,7 +565,6 @@
565 565  * (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
566 566  
567 567  
568 -
569 569  === 2.3.2  Device ID ===
570 570  
571 571  
... ... @@ -614,11 +614,11 @@
614 614  )))
615 615  
616 616  (((
617 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B
626 +Higher byte: Specify hardware version: always 0x00 for N95S31B
618 618  )))
619 619  
620 620  (((
621 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
630 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
622 622  )))
623 623  
624 624  (((
... ... @@ -700,11 +700,7 @@
700 700  
701 701  By default, N95S31B prints the downlink payload to console port.
702 702  
703 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
704 -|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)**
705 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4
706 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2
707 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4
712 +[[image:image-20220709100028-1.png]]
708 708  
709 709  
710 710  (((
... ... @@ -943,10 +943,12 @@
943 943  )))
944 944  
945 945  (((
946 -Firmware Download:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
951 +firmware:[[Dropbox - Firmware - 简化您的生活>>url:https://www.dropbox.com/sh/ap9k142hfnlh5w6/AACJeN_St0ryUl3AggrNB5x0a/N95S31B/Firmware?dl=0&subfolder_nav_tracking=1]]
947 947  
953 +(((
948 948  (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
949 949  )))
956 +)))
950 950  
951 951  
952 952  = 6.  Trouble Shooting =
... ... @@ -958,6 +958,10 @@
958 958  **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]]
959 959  )))
960 960  
968 +(% class="wikigeneratedid" %)
969 +(((
970 +
971 +)))
961 961  
962 962  == 6.2  AT Command input doesn't work ==
963 963  
... ... @@ -968,12 +968,6 @@
968 968  
969 969  )))
970 970  
971 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
972 -
973 -
974 -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]]//**.
975 -
976 -
977 977  = 7. ​ Order Info =
978 978  
979 979  
... ... @@ -1002,13 +1002,16 @@
1002 1002  * Weight / pcs : 180g
1003 1003  )))
1004 1004  
1010 +(((
1011 +
1005 1005  
1013 +
1014 +)))
1006 1006  
1007 1007  = 9.  Support =
1008 1008  
1009 1009  
1010 1010  * 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.
1011 -
1012 1012  * 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]]
1013 1013  
1014 1014  
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0