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

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

From version < 115.27 >

edited by Xiaoling
on 2022/07/11 08:36

To version < 122.1 >

edited by David Huang
on 2022/09/08 16:31

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -17,6 +17,7 @@
  = 1.  Introduction =
++
  == 1.1  What is N95S31B NB-IoT Sensor Node ==
  (((
@@ -55,6 +55,7 @@
  == 1.2  Features ==
++
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
  * Monitor Temperature & Humidity via SHT31
  * AT Commands to change parameters
@@ -66,9 +66,6 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long term use
--
--
--
  == 1.3  Specification ==
@@ -88,7 +88,6 @@
  (% style="color:#037691" %)**Battery:**
--
  * Li/SOCI2 un-chargeable battery
  * Capacity: 8500mAh
  * Self Discharge: <1% / Year @ 25°C
@@ -97,6 +97,7 @@
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -108,15 +108,20 @@
--== 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.
@@ -123,14 +123,20 @@
  === 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
++)))
  === 1.5.3  Reset Button ===
++
  Press to reboot the device.
@@ -137,6 +137,7 @@
  === 1.5.4  LED ===
++
  It will flash:
 . When boot the device in flash mode
@@ -144,6 +144,7 @@
  = 2.  Use N95S31B to communicate with IoT Server =
++
  == 2.1  How it works ==
@@ -160,7 +160,7 @@
  )))
--[[image:1657350248151-650.png]]
++[[image:1657520100595-569.png]]
  (((
@@ -176,26 +176,49 @@
  [[image:image-20220709150546-2.png]]
++
  === 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.
++)))
  )))
@@ -206,6 +206,7 @@
  === 2.2.3  Insert SIM card ===
++
  (((
  Insert the NB-IoT Card get from your provider.
  )))
@@ -221,14 +221,18 @@
  === 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
@@ -252,8 +252,9 @@
  [[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]]**
  )))
@@ -260,9 +260,10 @@
  === 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:**
  )))
@@ -310,6 +310,7 @@
  === 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
@@ -325,6 +325,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.
  )))
@@ -338,6 +338,7 @@
  === 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
@@ -352,6 +352,7 @@
  === 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
@@ -360,35 +360,60 @@
  )))
++(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
++**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 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 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>>||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>>||anchor="H2.3A0UplinkPayload"]].**
++)))
++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
@@ -423,6 +423,8 @@
  )))
  (((
++
++
  (((
  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
  )))
@@ -449,12 +449,41 @@
  )))
  (((
--
++(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
  )))
++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.
++
++|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
++|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
++
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 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:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
++
++* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
++* (% style="color:blue" %) Version: 0x000c=120=1.2
++* (% style="color:green" %)  BAT: 0x0d0f = 3343 mV = 3.343V
++* (% style="color:red" %)  Singal: 0x0c = 12
++* (% style="color:blue" %) Mod: 0x01 = 1
++* TemDS18B20: 0x0000= 0 = 0
++* (% style="color:green" %)Interrupt: 0x00= 0
++* (% style="color:green" %)adc: 0x0030= 48
++* SHTTEM: 0x0114= 276 = 27.6
++* SHTHUM:0x0231 =561=56.1%
++* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
++* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
++* 8 sets of recorded data: SHTTEM(% style="color:red" %),SHTHUM,Time stamp : //**0113023163199c5e**//,.......
++
  === 2.3.2  Device ID ===
++
  (((
  By default, the Device ID equal to the last 6 bytes of IMEI.
  )))
@@ -473,21 +473,44 @@
  (((
  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
++
++
  )))
++(% 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.
++
++User can use **AT+DEUI** to set Device ID
++
++**Example:**
++
++AT+DEUI=868411056754138
++
++
  === 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.
++)))
  (((
@@ -496,6 +496,7 @@
  === 2.3.4  Battery Info ===
++
  (((
  Ex1: 0x0B45 = 2885mV
  )))
@@ -508,6 +508,7 @@
  === 2.3.5  Signal Strength ===
++
  (((
  NB-IoT Network signal Strength.
  )))
@@ -540,6 +540,7 @@
  === 2.3.6  Temperature & Humidity ===
++
  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
  [[image:image-20220709161741-3.png]]
@@ -558,8 +558,9 @@
  == 2.4  Downlink Payload ==
--By default, NDDS75 prints the downlink payload to console port.
++By default, N95S31B prints the downlink payload to console port.
++
  [[image:image-20220709100028-1.png]]
@@ -596,7 +596,7 @@
  )))
  (((
--If payload = 0x04FF, it will reset the NDDS75
++If payload = 0x04FF, it will reset the N95S31B
  )))
@@ -607,12 +607,59 @@
  )))
++== 2.5 Humidity and Temperature alarm function ==
--== 2.5  Battery Analysis ==
++➢ AT Command:
--=== 2.5.1  Battery Type ===
++AT+ SHHUM=min,max
++² 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
++
++Example:
++
++AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
++
++
++AT+ SHTEMP=min,max
++
++² 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
++
++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 ==
++
++➢ AT Command:
++
++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)
++
++AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
++
++== 2.7 Read or Clear cached data ==
++
++➢ AT Command:
++
++AT+CDP    ~/~/ Read cached data
++
++[[image:image-20220908163102-2.png]]
++
++AT+CDP=0    ~/~/ Clear cached data
++
++== 2.8  Battery Analysis ==
++
++
++=== 2.8.1  Battery Type ===
++
++
  (((
  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.
  )))
@@ -635,10 +635,11 @@
--=== 2.5.2  Power consumption Analyze ===
++=== 2.8.2  Power consumption Analyze ===
++
  (((
--The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
++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.
  )))
  (((
@@ -646,8 +646,9 @@
  )))
--=== 2.5.3  Battery Note ===
++=== 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 uplink data, then the battery life may be decreased.
  )))
@@ -654,7 +654,7 @@
--=== 2.5.4  Replace the battery ===
++=== 2.8.4  Replace the battery ===
  (((
@@ -670,6 +670,7 @@
  = 3.  Access NB-IoT Module =
++
  (((
  Users can directly access the AT command set of the NB-IoT module.
  )))
@@ -676,6 +676,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]]
@@ -684,11 +684,13 @@
  = 4.  Using the AT Commands =
++
  == 4.1  Access AT Commands ==
--See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
++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>
@@ -728,7 +728,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
@@ -762,6 +762,7 @@
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -776,13 +776,16 @@
  (((
--(% style="color:red" %)Notice, N95S31B and LSN50v2 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 ==
@@ -798,6 +798,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.
@@ -847,5 +847,8 @@
  = 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

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

Summary

Details

Applications

Navigation