Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

Last modified by Mengting Qiu on 2024/04/02 16:44

From 114.2 to 115.1 From 129.33 to 129.34

From version 115.1

edited by Xiaoling
on 2022/07/09 16:17

Change comment: Uploaded new attachment "image-20220709161741-3.png", version {1}

To version 129.33

edited by Xiaoling
on 2022/12/30 11:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Content

@@ -9,6 +9,7 @@
  **Table of Contents:**
++{{toc/}}
@@ -21,16 +21,29 @@
  (((
++(((
  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*.
++)))
++(((
  The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
++)))
++(((
  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
++)))
++(((
  N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
++)))
++(((
++
++)))
++(((
  ~* make sure you have NB-IoT coverage locally.
++)))
  )))
@@ -54,6 +54,7 @@
  * 8500mAh Battery for long term use
++
  == 1.3  Specification ==
@@ -73,7 +73,6 @@
  (% style="color:#037691" %)**Battery:**
--
  * Li/SOCI2 un-chargeable battery
  * Capacity: 8500mAh
  * Self Discharge: <1% / Year @ 25°C
@@ -81,8 +81,10 @@
  * Max boost current: 2A, 1 second
++
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -94,40 +94,47 @@
--== 1.5  Pin Definitions ==
++== 1.5  Pin Definitions & Switch ==
++
  N95S31B use the mother board from NBSN95 which as below.
++
  [[image:image-20220709144723-1.png]]
  === 1.5.1  Jumper JP2 ===
++
  Power on Device when put this jumper.
--
  === 1.5.2  BOOT MODE / SW1 ===
--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.
--2) Flash: work mode, device starts to work and send out console output for further debug
++(((
++**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.
++)))
++(((
++**2) Flash:**  work mode, device starts to work and send out console output for further debug
++)))
  === 1.5.3  Reset Button ===
++
  Press to reboot the device.
--
  === 1.5.4  LED ===
++
  It will flash:
--1. When boot the device in flash mode
--1. Send an uplink packet
++1.  When boot the device in flash mode
++2.  Send an uplink packet
  = 2.  Use N95S31B to communicate with IoT Server =
@@ -148,7 +148,7 @@
  )))
--[[image:1657350248151-650.png]]
++[[image:1657520100595-569.png]]
  (((
@@ -157,7 +157,6 @@
  == 2.2  Configure the N95S31B ==
--
  === 2.2.1  Power On N95S31B ===
@@ -164,26 +164,48 @@
  [[image:image-20220709150546-2.png]]
--=== 2.2.1  Test Requirement ===
++=== 2.2.2  Test Requirement ===
++(((
  To use N95S31B in your city, make sure meet below requirements:
++)))
--* Your local operator has already distributed a NB-IoT Network there.
--* The local NB-IoT network used the band that N95S31B supports.
--* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
++* (((
++Your local operator has already distributed a NB-IoT Network there.
++)))
++* (((
++The local NB-IoT network used the band that N95S31B supports.
++)))
++* (((
++Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
++)))
++(((
  Below figure shows our testing structure.   Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
++)))
++(((
  N95S31B supports different communication protocol such as :
++)))
  (((
--* CoAP       ((% style="color:red" %)120.24.4.116:5683(%%))
--* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
--* MQTT      ((% style="color:red" %)120.24.4.116:1883(%%))
--* TCP          ((% style="color:red" %)120.24.4.116:5600(%%))
++* (((
++CoAP       ((% style="color:red" %)120.24.4.116:5683(%%))
++)))
++* (((
++raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
++)))
++* (((
++MQTT      ((% style="color:red" %)120.24.4.116:1883(%%))
++)))
++* (((
++TCP          ((% style="color:red" %)120.24.4.116:5600(%%))
++)))
++(((
  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.
++)))
  )))
@@ -191,9 +191,9 @@
  [[image:1657350625843-586.png]]
--
  === 2.2.3  Insert SIM card ===
++
  (((
  Insert the NB-IoT Card get from your provider.
  )))
@@ -206,26 +206,29 @@
  [[image:1657351240556-536.png]]
--
  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
++
  (((
  (((
  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.
++
++
  )))
  )))
  [[image:1657351312545-300.png]]
--**Connection:**
-- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
++(% style="color:blue" %)**Connection:**
-- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
++ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
-- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
++**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
++**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
++
  In the PC, use below serial tool settings:
  * Baud:       (% style="color:green" %)**9600**
@@ -240,17 +240,18 @@
  [[image:1657329814315-101.png]]
++
  (((
--(% 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/]]
++(% 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]]**
  )))
--
  === 2.2.5  Use CoAP protocol to uplink data ===
--(% 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/]]
++(% 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/]]**
++
  (((
  **Use below commands:**
  )))
@@ -259,10 +259,10 @@
  (% style="color:blue" %)**AT+PRO=1**  (%%)                                             ~/~/ Set to use CoAP protocol to uplink
  )))
  * (((
--(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **  (%%)~/~/ to set CoAP server address and port
++(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **    (%%)~/~/ to set CoAP server address and port
  )))
  * (((
--(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
++(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/  Set COAP resource path
  )))
  (((
@@ -281,7 +281,6 @@
  [[image:1657352185396-303.png]]
--
  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
@@ -295,18 +295,18 @@
  [[image:1657352403317-397.png]]
--
  === 2.2.7  Use MQTT protocol to uplink data ===
++
  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
--* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                        ~/~/Set to use MQTT protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)    ~/~/Set MQTT server address and port
--* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                            (%%)~/~/Set up the CLIENT of MQTT
--* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
--* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
--* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
--* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%)                  ~/~/Set the subscription topic of MQTT
++* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                        ~/~/  Set to use MQTT protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)    ~/~/  Set MQTT server address and port
++* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                            (%%)~/~/  Set up the CLIENT of MQTT
++* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
++* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/   Set the password of MQTT
++* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/   Set the sending topic of MQTT
++* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%)                  ~/~/   Set the subscription topic of MQTT
  [[image:1657352634421-276.png]]
@@ -313,6 +313,7 @@
  [[image:1657352645687-385.png]]
++
  (((
  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.
  )))
@@ -323,9 +323,9 @@
  )))
--
  === 2.2.8  Use TCP protocol to uplink data ===
++
  This feature is supported since firmware version v110
  * (% style="color:blue" %)**AT+PRO=4   ** (%%)                                          ~/~/ Set to use TCP protocol to uplink
@@ -337,9 +337,9 @@
  [[image:1657352914475-252.png]]
--
  === 2.2.9  Change Update Interval ===
++
  User can use below command to change the (% style="color:green" %)**uplink interval**.
  * (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/ Set Update Interval to 600s
@@ -348,59 +348,99 @@
  )))
++(((
++(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
++)))
++(((
++(% 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).**
++)))
++
  == 2.3  Uplink Payload ==
--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.
++(((
++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.
++)))
++(((
  For example:
++)))
-- (% 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.
++(((
++ (% 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.
++)))
++(((
  The uplink payloads are composed in  ASCII String. For example:
++)))
++(((
 a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
++)))
++(((
 x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d  Total 12 bytes
++)))
++(((
  (% style="color:red" %)**NOTE:**
++)))
  (% style="color:red" %)
--1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
--1. By default, the device will send an uplink message every 1 hour.
++1. (((
++**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
++)))
++1. (((
++**By default, the device will send an uplink message every 1 hour.**
++
++)))
--
  === 2.3.1  Payload Analyze ===
++==== 2.3.1.1  Before Firmware v1.2 ====
++
++
  N95S31B uplink payload includes in total 21 bytes
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
--|=(% style="width: 60px;" %)(((
--**Size(bytes)**
--)))|=(% 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**
--|(% 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" %)(((
++(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
++|=(% 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**
++|(% 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" %)(((
++(((
  Reserve/ Same as NBSN95 CFGMOD=1
++)))
++(((
  No function here.
--)))|(% style="width:77px" %)(((
--[[Temperature >>||anchor="H2.4.5A0Distance"]]
++)))
++)))|(% style="width:102px" %)(((
++(((
++[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
++)))
++(((
  By SHT31
--)))|(% style="width:80px" %)(((
--[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
++)))
++)))|(% style="width:81px" %)(((
++(((
++[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
++)))
++(((
  By SHT31
  )))
++)))
  (((
++
++
  (((
  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
  )))
@@ -409,43 +409,91 @@
  [[image:1657354294009-643.png]]
--(((
--The payload is ASCII string, representative same HEX:
--)))
--(((
--0x72403155615900640c6c19029200 where:
--)))
++The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
--* (((
--Device ID: 0x724031556159 = 724031556159
--)))
--* (((
--Version: 0x0064=100=1.0.0
--)))
++**where:**
--* (((
--BAT: 0x0c6c = 3180 mV = 3.180V
--)))
--* (((
--Signal: 0x19 = 25
--)))
--* (((
--Distance: 0x0292= 658 mm
--)))
--* (((
--Interrupt: 0x00 = 0
++* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
++* (% style="color:#037691" %)**Version: **(%%)    0x006e=110=1.1.0
++* (% style="color:#037691" %)**BAT:**   (%%)   0x0ccd = 3277 mV = 3.277V
++* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
++
++* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
++
++* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
++
++* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
++
++* (% style="color:#037691" %)**Humidity by SHT31:**  (%%)     0x0186 = 390 = 39.0 %rh
++
++(((
++
++
++
  )))
--== 2.4  Payload Explanation and Sensor Interface ==
++==== 2.3.1.2 Since Firmware v1.2 ====
--=== 2.4.1  Device ID ===
++In this mode, uplink payload includes 91 bytes in total by default.
++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.
++
++
++(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
++|=(% 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**
++|=(% 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 .....
++
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
++
++
++[[image:image-20220908154949-1.png]]
++
++
++The payload is ASCII string, representative same HEX:
++
++**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__ **
++
++**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
++
++**where:**
++
++* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
++
++* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
++
++* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
++
++* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
++
++* (% style="color:#037691" %)**Mod:**(%%)    0x01 = 1
++
++* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
++
++* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
++
++* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
++
++* (% style="color:#037691" %)**SHTTEM:**(%%)    0x0114= 276 = 27.6
++
++* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
++
++* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
++
++* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
++
++* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
++
++
++
++=== 2.3.2  Device ID ===
++
++
  (((
  By default, the Device ID equal to the last 6 bytes of IMEI.
  )))
@@ -452,10 +452,12 @@
  (((
  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
++
++
  )))
  (((
--**Example:**
++(% style="color:blue" %)**Example:**
  )))
  (((
@@ -463,148 +463,118 @@
  )))
  (((
--The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
--)))
++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.
--
--
--=== 2.4.2  Version Info ===
--
--(((
--Specify the software version: 0x64=100, means firmware version 1.00.
++
  )))
--(((
--For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
--)))
++(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
++By default, the Device ID equal to the last 15 bits of IMEI.
--=== 2.4.3  Battery Info ===
++User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
--(((
--Ex1: 0x0B45 = 2885mV
--)))
--(((
--Ex2: 0x0B49 = 2889mV
--)))
++(% style="color:blue" %)**Example:**
++AT+DEUI=868411056754138
--=== 2.4.4  Signal Strength ===
++=== 2.3.3  Version Info ===
--(((
--NB-IoT Network signal Strength.
--)))
  (((
--**Ex1: 0x1d = 29**
++These bytes include the hardware and software version.
  )))
  (((
--(% style="color:blue" %)**0**(%%)        -113dBm or less
++Higher byte: Specify hardware version: always 0x00 for N95S31B
  )))
  (((
--(% style="color:blue" %)**1**(%%)        -111dBm
++Lower byte: Specify the software version: 0x6E=110, means firmware version 110
  )))
  (((
--(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
++
  )))
  (((
--(% style="color:blue" %)**31**  (%%)    -51dBm or greater
++For example: 0x00 6E: this device is N95S31B with firmware version 110.
  )))
  (((
--(% style="color:blue" %)**99**   (%%)   Not known or not detectable
++
  )))
++=== 2.3.4  Battery Info ===
--=== 2.4.5  Distance ===
--
--Get the distance. Flat object range 280mm - 7500mm.
--
  (((
--For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
++Ex1: 0x0B45 = 2885mV
  )))
  (((
--(((
--(% style="color:blue" %)**                                                        0B05(H) = 2821(D) = 2821mm.**
++Ex2: 0x0B49 = 2889mV
  )))
--)))
--(((
--
--)))
--(((
--
--)))
++=== 2.3.5  Signal Strength ===
--=== 2.4.6  Digital Interrupt ===
  (((
--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.
++NB-IoT Network signal Strength.
  )))
  (((
--The command is:
++**Ex1: 0x1d = 29**
  )))
  (((
--(% 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]])**.**
++(% style="color:blue" %)**0**(%%)        -113dBm or less
  )))
--
  (((
--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.
++(% style="color:blue" %)**1**(%%)        -111dBm
  )))
--
  (((
--Example:
++(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
  )))
  (((
--0x(00): Normal uplink packet.
++(% style="color:blue" %)**31**  (%%)    -51dBm or greater
  )))
  (((
--0x(01): Interrupt Uplink Packet.
++(% style="color:blue" %)**99**   (%%)   Not known or not detectable
  )))
++=== 2.3.6  Temperature & Humidity ===
--=== 2.4.7  +5V Output ===
--(((
--NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
--)))
++The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
++[[image:image-20220709161741-3.png]]
--(((
--The 5V output time can be controlled by AT Command.
--)))
--(((
--(% style="color:blue" %)**AT+5VT=1000**
--)))
++Convert the read byte to decimal and divide it by ten.
--(((
--Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
--)))
++**Example:**
++Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
--== 2.5  Downlink Payload ==
++Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
--By default, NDDS75 prints the downlink payload to console port.
++== 2.4  Downlink Payload ==
++
++
++By default, N95S31B prints the downlink payload to console port.
++
  [[image:image-20220709100028-1.png]]
@@ -641,7 +641,7 @@
  )))
  (((
--If payload = 0x04FF, it will reset the NDDS75
++If payload = 0x04FF, it will reset the N95S31B
  )))
@@ -652,42 +652,65 @@
  )))
++== 2.5  Humidity and Temperature alarm function ==
--== 2.6  LED Indicator ==
++**~ (% style="color:blue" %)➢ AT Command:(%%)**
--The NDDS75 has an internal LED which is to show the status of different state.
++(% style="color:#037691" %)**AT+ SHHUM=min,max**
--* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
--* Then the LED will be on for 1 second means device is boot normally.
--* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
--* For each uplink probe, LED will be on for 500ms.
--(((
--
--)))
++² When min=0, and max≠0, Alarm higher than max
++² When min≠0, and max=0, Alarm lower than min
++² When min≠0 and max≠0, Alarm higher than max or lower than min
--== 2.7  Firmware Change Log ==
++ (% style="color:blue" %)**Example:**
--(((
--Download URL & Firmware Change log
--)))
++AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
--(((
--[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
--)))
++(% style="color:#037691" %)**AT+ SHTEMP=min,max**
--(((
--Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
--)))
++² When min=0, and max≠0, Alarm higher than max
++² When min≠0, and max=0, Alarm lower than min
++² When min≠0 and max≠0, Alarm higher than max or lower than min
++
++**~ (% style="color:blue" %)Example:(%%)**
++
++AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
++
++
++== 2.6 Set the number of data to be uploaded and the recording time ==
++
++
++**~ (% style="color:blue" %)➢ AT Command:(%%)**
++
++* (% 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)
++* (% 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.
++
++ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
++
++[[image:image-20221009001045-1.png||height="726" width="1009"]]
++
++
++== 2.7 Read or Clear cached data ==
++
++
++**~ (% style="color:blue" %)➢ AT Command:(%%)**
++
++* (% style="color:#037691" %)**AT+CDP**  (%%)        ~/~/ Read cached data
++* (% style="color:#037691" %)**AT+CDP=0** (%%)   ~/~/  Clear cached data
++
++[[image:image-20220908163102-2.png]]
++
++
  == 2.8  Battery Analysis ==
  === 2.8.1  Battery Type ===
@@ -694,7 +694,7 @@
  (((
--The NDDS75 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.
++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.
  )))
  (((
@@ -714,63 +714,41 @@
  )))
--
  === 2.8.2  Power consumption Analyze ===
--(((
--Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
--)))
--
  (((
--Instruction to use as below:
++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.
  )))
  (((
--(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
++
  )))
++=== 2.8.3  Battery Note ===
--(((
--(% style="color:blue" %)**Step 2: **(%%) Open it and choose
--)))
--* (((
--Product Model
--)))
--* (((
--Uplink Interval
--)))
--* (((
--Working Mode
--)))
--
  (((
--And the Life expectation in difference case will be shown on the right.
++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.
  )))
--[[image:image-20220709110451-3.png]]
++=== 2.8.4  Replace the battery ===
--=== 2.8.3  Battery Note ===
--
  (((
--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 transmit LoRa, then the battery life may be decreased.
++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.
  )))
--
--=== 2.8.4  Replace the battery ===
--
  (((
--The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
++The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
  )))
--
  = 3.  Access NB-IoT Module =
++
  (((
  Users can directly access the AT command set of the NB-IoT module.
  )))
@@ -777,19 +777,21 @@
  (((
  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/]]
++
++
  )))
  [[image:1657333200519-600.png]]
--
  = 4.  Using the AT Commands =
  == 4.1  Access AT Commands ==
--See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
++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]]
++
  AT+<CMD>?                    : Help on <CMD>
  AT+<CMD>                      : Run <CMD>
@@ -829,7 +829,24 @@
  AT+SERVADDR          : Server Address
++AT+TR      : Get or Set record time
++AT+APN            : Get or set the APN
++
++AT+FBAND          : Get or Set whether to automatically modify the frequency band
++
++AT+DNSCFG         :  Get or Set DNS Server
++
++AT+GETSENSORVALUE   : Returns the current sensor measurement
++
++AT+NOUD      : Get or Set the number of data to be uploaded
++
++AT+CDP     : Read or Clear cached data
++
++AT+SHTEMP: Get or Set alarm of temp
++
++AT+SHHUM: Get or Set alarm of moisture
++
  (% style="color:#037691" %)**COAP Management**
  AT+URI            : Resource parameters
@@ -860,7 +860,6 @@
  AT+PWORD       : Serial Access Password
--
  = 5.  FAQ =
  == 5.1  How to Upgrade Firmware ==
@@ -875,11 +875,14 @@
  )))
  (((
--(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
++
++
++(((
++(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
  )))
++)))
--
  = 6.  Trouble Shooting =
  == 6.1  Connection problem when uploading firmware ==
@@ -894,9 +894,9 @@
  )))
--
  == 6.2  AT Command input doesn't work ==
++
  (((
  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.
@@ -903,18 +903,12 @@
  )))
--
  = 7.  Order Info =
--Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
--(% class="wikigeneratedid" %)
--(((
--
--)))
--
  = 8.  Packing Info =
  (((
@@ -922,7 +922,7 @@
  (% style="color:#037691" %)**Package Includes**:
--* NSE01 NB-IoT Distance Detect Sensor Node x 1
++* N95S31B NB-IoT Temperature and Humidity Sensor
  * External antenna x 1
  )))
@@ -931,21 +931,25 @@
  (% style="color:#037691" %)**Dimension and weight**:
--
  * Device Size: 13.0 x 5 x 4.5 cm
  * Device Weight: 150g
--* Package Size / pcs : 15 x 12x 5.5 cm
--* Weight / pcs : 220g
++* Package Size / pcs : 14.0 x 8x 5 cm
++* Weight / pcs : 180g
  )))
  (((
--
  )))
  = 9.  Support =
++
  * 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.
  * 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]]
++
++
++
++
++

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