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

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

From version < 97.8 >

edited by Xiaoling
on 2022/07/09 11:26

To version < 120.1 >

edited by David Huang
on 2022/09/08 15:49

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

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Attachments (0 modified, 20 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--NDDS75 NB-IoT Distance Detect Sensor User Manual
++N95S31B NB-IoT Temperature & Humidity Sensor User Manual

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.David

Content

@@ -1,10 +1,12 @@
  (% style="text-align:center" %)
--[[image:image-20220709085040-1.png||height="542" width="524"]]
++[[image:1657348034241-728.png||height="470" width="470"]]
++
++
  **Table of Contents:**
  {{toc/}}
@@ -13,48 +13,62 @@
--
  = 1.  Introduction =
--== 1.1  What is NDDS75 Distance Detection Sensor ==
++== 1.1  What is N95S31B NB-IoT Sensor Node ==
++
  (((
  (((
--The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
--\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
--\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
--\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
--\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
--\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
++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).
++)))
++
++(((
  )))
--[[image:1657327959271-447.png]]
++(((
++~* make sure you have NB-IoT coverage locally.
++)))
++
++)))
++[[image:1657348284168-431.png]]
++
++
  == 1.2  Features ==
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
--* Ultra low power consumption
--* Distance Detection by Ultrasonic technology
--* Flat object range 280mm - 7500mm
--* Accuracy: ±(1cm+S*0.3%) (S: Distance)
--* Cable Length: 25cm
++* Monitor Temperature & Humidity via SHT31
  * AT Commands to change parameters
  * Uplink on periodically
  * Downlink to change configure
  * IP66 Waterproof Enclosure
++* Ultra-Low Power consumption
++* AT Commands to change parameters
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long term use
++
  == 1.3  Specification ==
@@ -63,6 +63,8 @@
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
++
++
  (% style="color:#037691" %)**NB-IoT Spec:**
  * - B1 @H-FDD: 2100MHz
@@ -72,6 +72,8 @@
  * - B20 @H-FDD: 800MHz
  * - B28 @H-FDD: 700MHz
++
++
  (% style="color:#037691" %)**Battery:**
  * Li/SOCI2 un-chargeable battery
@@ -80,15 +80,12 @@
  * Max continuously current: 130mA
  * Max boost current: 2A, 1 second
--(% style="color:#037691" %)**Power Consumption**
--* STOP Mode: 10uA @ 3.3v
--* Max transmit power: 350mA@3.3v
--
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -100,24 +100,68 @@
--== 1.5  Pin Definitions ==
++== 1.5  Pin Definitions & Switch ==
--[[image:1657328609906-564.png]]
++N95S31B use the mother board from NBSN95 which as below.
--= 2.  Use NDDS75 to communicate with IoT Server =
++[[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.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
++
++
++
++
++= 2.  Use N95S31B to communicate with IoT Server =
++
++
  == 2.1  How it works ==
++
  (((
--The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
++The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
  )))
  (((
--The diagram below shows the working flow in default firmware of NDDS75:
++The diagram below shows the working flow in default firmware of N95S31B:
  )))
  (((
@@ -124,7 +124,7 @@
  )))
--[[image:1657328659945-416.png]]
++[[image:1657520100595-569.png]]
  (((
@@ -131,30 +131,69 @@
  )))
--== 2.2  Configure the NDDS75 ==
++== 2.2  Configure the N95S31B ==
++=== 2.2.1  Power On N95S31B ===
++
++
++[[image:image-20220709150546-2.png]]
++
++
++
  === 2.2.1  Test Requirement ===
++
  (((
--To use NDDS75 in your city, make sure meet below requirements:
++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 NSE01 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.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test 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 :
++)))
--[[image:1657328756309-230.png]]
++(((
++* (((
++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.
++)))
++
++)))
--=== 2.2.2  Insert SIM card ===
++[[image:1657350625843-586.png]]
++
++
++=== 2.2.3  Insert SIM card ===
++
++
  (((
  Insert the NB-IoT Card get from your provider.
  )))
@@ -164,20 +164,24 @@
  )))
--[[image:1657328884227-504.png]]
++[[image:1657351240556-536.png]]
--=== 2.2.3  Connect USB – TTL to NDDS75 to configure it ===
++=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
++
  (((
  (((
--User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
++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:image-20220709092052-2.png]]
++[[image:1657351312545-300.png]]
++
  **Connection:**
   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
@@ -196,40 +196,56 @@
  * Flow Control: (% style="color:green" %)**None**
  (((
--Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
++Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
  )))
  [[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/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
++(% 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.4  Use CoAP protocol to uplink data ===
++=== 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:**
++)))
--* (% 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+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
++* (((
++(% 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+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
++)))
++(((
++
++
  For parameter description, please refer to AT command set
++)))
--[[image:1657330452568-615.png]]
++[[image:1657352146020-183.png]]
++(((
  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
++)))
--[[image:1657330472797-498.png]]
++[[image:1657352185396-303.png]]
--=== 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
++=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
  * (% style="color:blue" %)**AT+PRO=2   ** (%%)        ~/~/ Set to use UDP protocol to uplink
@@ -236,109 +236,117 @@
  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   **  (%%) ~/~/ to set UDP server address and port
  * (% style="color:blue" %)**AT+CFM=1       **   (%%) ~/~/ If the server does not respond, this command is unnecessary
--[[image:1657330501006-241.png]]
--[[image:1657330533775-472.png]]
++[[image:1657352391268-297.png]]
++[[image:1657352403317-397.png]]
--=== 2.2.6  Use MQTT protocol to uplink data ===
--* (% 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=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
--* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%)       ~/~/Set the subscription topic of MQTT
++=== 2.2.7  Use MQTT protocol to uplink data ===
--[[image:1657249978444-674.png]]
++N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
--[[image:1657330723006-866.png]]
++* (% 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]]
++
++
++[[image:1657352645687-385.png]]
++
++
  (((
--MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
++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.
  )))
++(((
++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.
++)))
--=== 2.2.7  Use TCP protocol to uplink data ===
++=== 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
  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
--[[image:image-20220709093918-1.png]]
--[[image:image-20220709093918-2.png]]
++[[image:1657352898400-901.png]]
++[[image:1657352914475-252.png]]
--=== 2.2.8  Change Update Interval ===
++
++=== 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
  (((
--(% style="color:red" %)**NOTE:**
++
  )))
--(((
--(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
--)))
--
  == 2.3  Uplink Payload ==
--In this mode, uplink payload includes in total 14 bytes
++(((
++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.
++)))
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
--|=(% style="width: 80px;" %)(((
--**Size(bytes)**
--)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
  (((
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
++For example:
  )))
++(((
++ (% 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.
++)))
--[[image:1657331036973-987.png]]
  (((
--The payload is ASCII string, representative same HEX:
++The uplink payloads are composed in  ASCII String. For example:
  )))
  (((
--0x72403155615900640c6c19029200 where:
++0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
  )))
--* (((
--Device ID: 0x724031556159 = 724031556159
++(((
++0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d  Total 12 bytes
  )))
--* (((
--Version: 0x0064=100=1.0.0
++
++
++(((
++(% style="color:red" %)**NOTE:**
  )))
--* (((
--BAT: 0x0c6c = 3180 mV = 3.180V
++(% style="color:red" %)
++1. (((
++**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
  )))
--* (((
--Signal: 0x19 = 25
--)))
--* (((
--Distance: 0x0292= 658 mm
--)))
--* (((
--Interrupt: 0x00 = 0
++1. (((
++**By default, the device will send an uplink message every 1 hour.**
@@ -345,168 +345,198 @@
  )))
--== 2.4  Payload Explanation and Sensor Interface ==
++=== 2.3.1  Payload Analyze ===
--=== 2.4.1  Device ID ===
++N95S31B uplink payload includes in total 21 bytes
++
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
++|=(% style="width: 60px;" %)(((
++**Size(bytes)**
++)))|=(% 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**
++|(% 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" %)(((
  (((
--By default, the Device ID equal to the last 6 bytes of IMEI.
++Reserve/ Same as NBSN95 CFGMOD=1
  )))
  (((
--User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
++No function here.
  )))
++)))|(% style="width:77px" %)(((
++(((
++[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
++)))
  (((
--**Example:**
++By SHT31
  )))
++)))|(% style="width:80px" %)(((
++(((
++[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
++)))
  (((
--AT+DEUI=A84041F15612
++By SHT31
  )))
++)))
  (((
--The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
++
++
++(((
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
  )))
++)))
++[[image:1657354294009-643.png]]
--=== 2.4.2  Version Info ===
++The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
++
++* Device ID: 0x724031607457 = 724031607457
++* Version: 0x006e=110=1.1.0
++
++* BAT: 0x0ccd = 3277 mV = 3.277V
++* Signal: 0x1b = 27
++* Model: 0x01 = 1
++* 0x00dc000ccc= reserve, ignore in N95S31B
++* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
++* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
++
  (((
--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.
++
  )))
++=== 2.3.2  Device ID ===
--=== 2.4.3  Battery Info ===
  (((
--Ex1: 0x0B45 = 2885mV
++By default, the Device ID equal to the last 6 bytes of IMEI.
  )))
  (((
--Ex2: 0x0B49 = 2889mV
++User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
  )))
++(((
++**Example:**
++)))
++(((
++AT+DEUI=A84041F15612
++)))
--=== 2.4.4  Signal Strength ===
--
  (((
--NB-IoT Network signal Strength.
++The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
  )))
++
++
++=== 2.3.3  Version Info ===
++
++
  (((
--**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
--
  (((
--(((
--(% style="color:blue" %)**                                                        0B05(H) = 2821(D) = 2821mm.**
++Ex1: 0x0B45 = 2885mV
  )))
--)))
  (((
--
++Ex2: 0x0B49 = 2889mV
  )))
--(((
--
--)))
--=== 2.4.6  Digital Interrupt ===
++=== 2.3.5  Signal Strength ===
++
++
  (((
--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.4.7  +5V Output ===
++=== 2.3.6  Temperature & Humidity ===
--(((
--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.
--(((
--The 5V output time can be controlled by AT Command.
--)))
++[[image:image-20220709161741-3.png]]
--(((
--(% style="color:blue" %)**AT+5VT=1000**
--)))
--(((
--Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
--)))
++Convert the read byte to decimal and divide it by ten.
++**Example:**
--== 2.5  Downlink Payload ==
++Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
--By default, NDDS75 prints the downlink payload to console port.
++Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
++
++
++== 2.4  Downlink Payload ==
++
++
++By default, N95S31B prints the downlink payload to console port.
++
  [[image:image-20220709100028-1.png]]
@@ -543,7 +543,7 @@
  )))
  (((
--If payload = 0x04FF, it will reset the NDDS75
++If payload = 0x04FF, it will reset the N95S31B
  )))
@@ -555,47 +555,17 @@
--== 2.6  LED Indicator ==
++== 2.5  Battery Analysis ==
--The NDDS75 has an internal LED which is to show the status of different state.
++=== 2.5.1  Battery Type ===
--* 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.
--
  (((
--
++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.
  )))
--
--
--== 2.7  Firmware Change Log ==
--
--
--Download URL & Firmware Change log
--
  (((
--[[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/]]
--)))
--
--
--Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
--
--
--
--== 2.8  Battery Analysis ==
--
--=== 2.8.1  Battery Type ===
--
--
--(((
--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 battery is designed to last for several years depends on the actually use environment and update interval.
  )))
@@ -613,56 +613,37 @@
--=== 2.8.2  Power consumption Analyze ===
++=== 2.5.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/]]
++
  )))
--(((
--(% style="color:blue" %)**Step 2: **(%%) Open it and choose
--)))
++=== 2.5.3  Battery Note ===
--* (((
--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.5.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).
  )))
@@ -669,6 +669,7 @@
  = 3.  Access NB-IoT Module =
++
  (((
  Users can directly access the AT command set of the NB-IoT module.
  )))
@@ -675,6 +675,8 @@
  (((
  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]]
@@ -683,11 +683,13 @@
  = 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>
@@ -761,6 +761,7 @@
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -773,13 +773,18 @@
  )))
  (((
--(% 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 ==
@@ -795,6 +795,7 @@
  == 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.
@@ -805,7 +805,7 @@
  = 7.  Order Info =
--Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
  (% class="wikigeneratedid" %)
@@ -820,7 +820,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
  )))
@@ -829,11 +829,10 @@
  (% 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
  )))
  (((
@@ -845,5 +845,9 @@
  = 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]]
++
++
++

1657348034241-728.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+127.8 KB

Content

1657348284168-431.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+93.5 KB

Content

1657350248151-650.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+126.1 KB

Content

1657350625843-586.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+93.3 KB

Content

1657351240556-536.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+483.6 KB

Content

1657351312545-300.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+675.8 KB

Content

1657352146020-183.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+264.0 KB

Content

1657352185396-303.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+98.3 KB

Content

1657352391268-297.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+238.0 KB

Content

1657352403317-397.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+547.7 KB

Content

1657352634421-276.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+163.6 KB

Content

1657352645687-385.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+214.7 KB

Content

1657352898400-901.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+144.8 KB

Content

1657352914475-252.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+157.0 KB

Content

1657354294009-643.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+214.7 KB

Content

1657520100595-569.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+126.1 KB

Content

image-20220709144723-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+413.1 KB

Content

image-20220709150546-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+333.5 KB

Content

image-20220709161741-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+111.2 KB

Content

image-20220908154949-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+58.5 KB

Content

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

Summary

Details

Applications

Navigation