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

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

From version < 118.7 >

edited by Xiaoling
on 2022/07/12 17:35

To version < 115.11 >

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- 1657520100595-569.png

Details

Page properties

Content

@@ -9,7 +9,6 @@
  **Table of Contents:**
--{{toc/}}
@@ -22,29 +22,16 @@
  (((
--(((
  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.
--)))
  )))
@@ -68,6 +68,7 @@
++
  == 1.3  Specification ==
@@ -87,6 +87,7 @@
  (% style="color:#037691" %)**Battery:**
++
  * Li/SOCI2 un-chargeable battery
  * Capacity: 8500mAh
  * Self Discharge: <1% / Year @ 25°C
@@ -95,6 +95,7 @@
++
  == 1.4  Applications ==
  * Smart Buildings & Home Automation
@@ -108,7 +108,7 @@
--== 1.5  Pin Definitions & Switch ==
++== 1.5  Pin Definitions ==
  N95S31B use the mother board from NBSN95 which as below.
@@ -123,13 +123,9 @@
  === 1.5.2  BOOT MODE / SW1 ===
--(((
 ) 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.
--)))
--(((
 ) Flash: work mode, device starts to work and send out console output for further debug
--)))
@@ -165,7 +165,7 @@
  )))
--[[image:1657520100595-569.png]]
++[[image:1657350248151-650.png]]
  (((
@@ -184,45 +184,23 @@
  === 2.2.1  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.
--)))
  )))
@@ -392,83 +392,51 @@
  == 2.3  Uplink Payload ==
--(((
--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.
--)))
++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.
--(((
  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.
--)))
++ (% 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.
--(((
  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>>||anchor="H2.3A0UplinkPayload"]].
--)))
--1. (((
--By default, the device will send an uplink message every 1 hour.
++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.
--
--)))
--
  === 2.3.1  Payload Analyze ===
  N95S31B uplink payload includes in total 21 bytes
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
  |=(% 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" %)(((
--(((
++)))|=(% 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" %)(((
  Reserve/ Same as NBSN95 CFGMOD=1
--)))
--(((
  No function here.
--)))
  )))|(% style="width:77px" %)(((
--(((
--[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
--)))
++[[Temperature >>||anchor="H2.4.5A0Distance"]]
--(((
  By SHT31
--)))
  )))|(% style="width:80px" %)(((
--(((
--[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
--)))
++[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
--(((
  By SHT31
  )))
--)))
  (((
  (((
@@ -527,25 +527,15 @@
  === 2.3.3  Version Info ===
--(((
++
  These bytes include the hardware and software version.
--)))
--(((
  Higher byte: Specify hardware version: always 0x00 for N95S31B
--)))
--(((
  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
--)))
--(((
--
--)))
--(((
  For example: 0x00 6E: this device is N95S31B with firmware version 110.
--)))
  (((
@@ -614,9 +614,9 @@
--== 2.4  Downlink Payload ==
++== 2.5  Downlink Payload ==
--By default, N95S31B prints the downlink payload to console port.
++By default, NDDS75 prints the downlink payload to console port.
  [[image:image-20220709100028-1.png]]
@@ -654,7 +654,7 @@
  )))
  (((
--If payload = 0x04FF, it will reset the N95S31B
++If payload = 0x04FF, it will reset the NDDS75
  )))
@@ -834,10 +834,8 @@
  (((
--(((
  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
  )))
--)))
@@ -868,7 +868,7 @@
  = 7.  Order Info =
--Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
++Part Number**:** (% style="color:#4f81bd" %)**N95S31B**
  (% class="wikigeneratedid" %)
@@ -883,7 +883,7 @@
  (% style="color:#037691" %)**Package Includes**:
--* N95S31B NB-IoT Temperature and Humidity Sensor
++* NSE01 NB-IoT Distance Detect Sensor Node x 1
  * External antenna x 1
  )))
@@ -892,10 +892,11 @@
  (% style="color:#037691" %)**Dimension and weight**:
++
  * Device Size: 13.0 x 5 x 4.5 cm
  * Device Weight: 150g
--* Package Size / pcs : 14.0 x 8x 5 cm
--* Weight / pcs : 180g
++* Package Size / pcs : 15 x 12x 5.5 cm
++* Weight / pcs : 220g
  )))
  (((

1657520100595-569.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation