<
From version < 129.36 >
edited by Xiaoling
on 2023/04/03 17:01
To version < 130.15 >
edited by Xiaoling
on 2023/04/28 15:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,8 +19,6 @@
19 19  
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 -(((
23 -
24 24  
25 25  (((
26 26  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*.
... ... @@ -39,20 +39,13 @@
39 39  )))
40 40  
41 41  (((
42 -
43 -)))
44 -
45 -(((
46 46  ~* make sure you have NB-IoT coverage locally.
47 47  )))
48 48  
49 -
50 -)))
51 51  
52 52  [[image:1657348284168-431.png]]
53 53  
54 54  
55 -
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -177,7 +177,6 @@
177 177  
178 178  )))
179 179  
180 -
181 181  == 2.2 ​ Configure the N95S31B ==
182 182  
183 183  === 2.2.1  Power On N95S31B ===
... ... @@ -365,7 +365,6 @@
365 365  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.
366 366  )))
367 367  
368 -
369 369  (((
370 370  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.
371 371  )))
... ... @@ -418,7 +418,7 @@
418 418  )))
419 419  
420 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.
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.
422 422  )))
423 423  
424 424  
... ... @@ -455,11 +455,10 @@
455 455  ==== 2.3.1.1  Before Firmware v1.2 ====
456 456  
457 457  
458 -N95S31B uplink payload includes in total 21 bytes
447 +N95S31B uplink payload includes in total 21 bytes.
459 459  
460 -
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**
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**
463 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" %)(((
464 464  (((
465 465  Reserve/ Same as NBSN95 CFGMOD=1
... ... @@ -532,8 +532,8 @@
532 532  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.
533 533  
534 534  
535 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
536 -|=(% 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**
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**
537 537  |=(% 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 .....
538 538  
539 539  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
... ... @@ -626,11 +626,11 @@
626 626  )))
627 627  
628 628  (((
629 -Higher byte: Specify hardware version: always 0x00 for N95S31B
617 +**Higher byte:** Specify hardware version: always 0x00 for N95S31B
630 630  )))
631 631  
632 632  (((
633 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
621 +**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
634 634  )))
635 635  
636 636  (((
... ... @@ -712,7 +712,11 @@
712 712  
713 713  By default, N95S31B prints the downlink payload to console port.
714 714  
715 -[[image:image-20220709100028-1.png]]
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
716 716  
717 717  
718 718  (((
... ... @@ -951,12 +951,10 @@
951 951  )))
952 952  
953 953  (((
954 -
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]]
955 955  
956 -(((
957 957  (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
958 958  )))
959 -)))
960 960  
961 961  
962 962  = 6.  Trouble Shooting =
... ... @@ -968,10 +968,6 @@
968 968  **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]]
969 969  )))
970 970  
971 -(% class="wikigeneratedid" %)
972 -(((
973 -
974 -)))
975 975  
976 976  == 6.2  AT Command input doesn't work ==
977 977  
... ... @@ -982,6 +982,12 @@
982 982  
983 983  )))
984 984  
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 +
985 985  = 7. ​ Order Info =
986 986  
987 987  
... ... @@ -1010,17 +1010,13 @@
1010 1010  * Weight / pcs : 180g
1011 1011  )))
1012 1012  
1013 -(((
1014 -
1015 1015  
1016 -
1017 -)))
1018 1018  
1019 1019  = 9.  Support =
1020 1020  
1021 1021  
1022 1022  * 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 +
1023 1023  * 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]]
1024 1024  
1025 -
1026 1026  
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0