Changes for page NSPH01-NB-IoT Soil pH Sensor User Manual

Last modified by Bei Jinggeng on 2024/03/30 17:53

From version < 51.3 >

edited by Xiaoling
on 2022/09/12 15:01

To version < 44.3 >

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

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)
- image-20220912144017-1.png

Details

Page properties

Content

@@ -1,5 +1,5 @@
  (% style="text-align:center" %)
--[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png||height="442" width="410"]]
++[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png]]
  **Table of Contents:**
@@ -7,36 +7,31 @@
--= 1.  Introduction =
++= 1. Introduction =
++== 1.1 What is NSPH01 Soil pH Sensor ==
--== 1.1  What is NSPH01 Soil pH Sensor ==
++The Dragino NSPH01 is a **NB-IOT soil ph sensor** for IoT of Agriculture. It is designed to measure the soil PH and soil temperature, so to send to the platform to analyze the soil acid or alkali level. The probe is IP68 waterproof.
++NSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** pH **with high accuracy and stable value. The NSPH01 probe can be buried into soil for long time use.
--The Dragino NSPH01 is a (% style="color:blue" %)**NB-IoT soil pH sensor**(%%) for IoT of Agriculture. It is designed to measure the soil pH and soil temperature, so to send to the platform to analyze the soil acid or alkali level. The probe is IP68 waterproof.
--
--NSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** (% style="color:blue" %)pH (%%)**with high accuracy and stable value. The NSPH01 probe can be buried into soil for long time use.
--
  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.
--\\NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
--\\NSPH01 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 NSPH01, user needs to check if there is NB-IoT coverage in the installation area and with the bands NSPH01 supports. If the local operator supports it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card** (%%)from local operator and install NSPH01 to get NB-IoT network connection.
++\\NSPH01 supports different uplink methods include **TCP,MQTT,UDP and CoAP  **for different application requirement.
++\\NSPH01 is powered by  **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 NSPH01, user needs to check if there is NB-IoT coverage in local area and with the bands NSPH01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install NSPH01 to get NB-IoT network connection.
--
++(% style="text-align:center" %)
  [[image:image-20220907153151-1.png]]
--
++(% style="text-align:center" %)
  [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]]
++== 1.2 Features ==
--
--== 1.2  Features ==
--
--
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
  * Monitor soil pH with temperature compensation.
  * Monitor soil temperature
--* pH and Temperature alarm function
++* PH and Temperature alarm function
  * Monitor Battery Level
  * Support pH calibration by end user
  * Uplink on periodically
@@ -45,18 +45,17 @@
  * IP68 rate for the Sensor Probe
  * Ultra-Low Power consumption
  * AT Commands to change parameters
--* Micro SIM card slot
++* Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long term use
  == 1.3  Specification ==
++**Common DC Characteristics:**
--(% style="color:#037691" %)**Common DC Characteristics:**
--
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
--(% style="color:#037691" %)**NB-IoT Spec:**
++**NB-IoT Spec:**
  * - B1 @H-FDD: 2100MHz
  * - B3 @H-FDD: 1800MHz
@@ -65,11 +65,10 @@
  * - B20 @H-FDD: 800MHz
  * - B28 @H-FDD: 700MHz
--== 1.4  Probe Specification ==
++== 1.4 Probe Specification ==
++**Soil pH:**
--(% style="color:#037691" %)**Soil pH:**
--
  * Range: 3 ~~ 10 pH
  * Resolution: 0.01 pH
  * Accuracy: ±2% under (0~~50 ℃, Accuracy will poor under 0 due to frozen)
@@ -77,7 +77,7 @@
  * IP68 Protection
  * Length: 3.5 meters
--(% style="color:#037691" %)**Soil Temperature:**
++**Soil Temperature:**
  * Range -40℃～85℃
  * Resolution: 0.1℃
@@ -91,125 +91,106 @@
  == 1.6 Pin mapping and power on ==
--
++(% style="text-align:center" %)
  [[image:image-20220907153300-2.png]]
--
  = 2.  Use NSPH01 to communicate with IoT Server =
--
  == 2.1  How it works ==
--
  The NSPH01 is equipped with a NB-IoT module, the pre-loaded firmware in NSPH01 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 NSPH01.
  The diagram below shows the working flow in default firmware of NSPH01:
--
++(% style="text-align:center" %)
  [[image:image-20220907153416-3.png]]
--
--
  == 2.2  Configure the NSPH01 ==
--
  === 2.2.1  Test Requirement ===
++To use NSPH01 in your city, make sure meet below requirements:
--To use NSPH01 in the field, 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 NSPH01 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 NSPH01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(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.  The NSPH01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server
--
++(% style="text-align:center" %)
  [[image:image-20220907153445-4.png]]
--
  === 2.2.2  Insert SIM card ===
++Insert the NB-IoT Card get from your provider.
--User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
++User need to take out the NB-IoT module and insert the SIM card like below:
++(% style="text-align:center" %)
  [[image:image-20220907153505-5.png]]
--
--
  === 2.2.3  Connect USB – TTL to NSPH01 to configure it ===
++User need to configure NSPH01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NSPH01 support AT Commands, user can use a USB to TTL adapter to connect to NSPH01 and use AT Commands to configure it, as below.
--User need to configure NSPH01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NSPH01 support AT Commands, user can use a USB to TTL adapter to connect to NSPH01 and use AT Commands to configure it, as below.
++**Connection:**
++ USB TTL GND <~-~-~-~-> GND
--(% style="color:blue" %)**Connection:**
++ USB TTL TXD <~-~-~-~-> UART_RXD
--**~ (% style="background-color:yellow" %) USB TTL GND <~-~-~-~->  GND(%%)**
++ 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**
--* Data bits:**        (% style="color:green" %)8(%%)**
--* Stop bits:        (% style="color:green" %)**1**
--* Parity:             (% style="color:green" %)**None**
--* Flow Control: (% style="color:green" %)**None**
--*
++* Baud:       **9600**
++* Data bits:** 8**
++* Stop bits: **1**
++* Parity:      **None**
++* Flow Control: **None**
--Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSPH01. NSPH01 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 NSPH01. NSPH01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.
++(% style="text-align:center" %)
++[[image:image-20220907153529-6.png]]
--[[image:image-20220912144017-1.png]]
++**Note: the valid AT Commands can be found at:  **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
--
--(% style="color:red" %)**Note: the valid AT Commands can be found at:**(%%)**  **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
--
--
--
  === 2.2.4  Use CoAP protocol to uplink data ===
++**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/**>>url: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/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
++**Use below commands:**
++* **AT+PRO=1**                                               ~/~/ Set to use CoAP protocol to uplink
++* **AT+SERVADDR=120.24.4.116,5683   **  ~/~/ to set CoAP server address and port
++* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" **       ~/~/Set COAP resource path
--(% style="color:blue" %)**Use below commands:**
--
--* (% style="color:#037691" %)**AT+PRO=1**                         (%%)                      ~/~/  Set to use CoAP protocol to uplink
--* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)  ~/~/   to set CoAP server address and port
--* (% style="color:#037691" %)**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
--
++(% style="text-align:center" %)
  [[image:image-20220907153551-7.png||height="502" width="740"]]
++After configure the server address and **reset the device** (via AT+ATZ ), NSPH01 will start to uplink sensor values to CoAP server.
--After configure the server address and (% style="color:green" %)**reset the device (via AT+ATZ )**(%%), NSPH01 will start to uplink sensor values to CoAP server.
--
--
++(% style="text-align:center" %)
  [[image:image-20220907153612-8.png||height="529" width="729"]]
--
  === 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
--
  This feature is supported since firmware version v1.0.1
--(%%)
--* **(% style="color:blue" %)AT+PRO=2   **                                            ~/~/  Set to use UDP protocol to uplink
--* **(% 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 unnecessar
++* **AT+PRO=2   **  ~/~/ Set to use UDP protocol to uplink
++* **AT+SERVADDR=120.24.4.116,5601   **   ~/~/ to set UDP server address and port
++* **AT+CFM=1       **    ~/~/If the server does not respond, this command is unnecessar
++
++(% style="text-align:center" %)
  [[image:image-20220907153643-9.png||height="401" width="734"]]
--
++(% style="text-align:center" %)
  [[image:image-20220907153703-10.png||height="309" width="738"]]
@@ -217,49 +217,44 @@
  This feature is supported since firmware version v110
--* **(% 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=NSE01_PUB                    **(%%)  ~/~/Set the sending topic of MQTT
--* **(% style="color:blue" %)AT+SUBTOPIC=NSE01_SUB          **   (%%)       ~/~/Set the subscription topic of MQTT
++* **AT+PRO=3   **                                              ~/~/Set to use MQTT protocol to uplink
++* **AT+SERVADDR=120.24.4.116,1883   **      ~/~/Set MQTT server address and port
++* **AT+CLIENT=CLIENT       **                           ~/~/Set up the CLIENT of MQTT
++* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
++* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
++* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
++* **AT+SUBTOPIC=NSE01_SUB          **          ~/~/Set the subscription topic of MQTT
--
++(% style="text-align:center" %)
  [[image:image-20220907153739-11.png||height="491" width="764"]]
--
++(% style="text-align:center" %)
  [[image:image-20220907153751-12.png||height="555" width="769"]]
  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.
--
--
--
  === 2.2.7  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
++* **AT+PRO=4   **                                           ~/~/ Set to use TCP protocol to uplink
++* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
--
++(% style="text-align:center" %)
  [[image:image-20220907153818-13.png||height="486" width="668"]]
--
++(% style="text-align:center" %)
  [[image:image-20220907153827-14.png||height="236" width="684"]]
--
--
--
  === 2.2.8  Change Update Interval ===
--Users can use the below command to change the **uplink interval**.
++User can use below command to change the **uplink interval**.
--* **(% style="color:blue" %)AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
++* **AT+TDC=600      **  ~/~/ Set Update Interval to 600s
--**(% style="color:red" %)NOTE: 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).**
++**NOTE:**
++**~1. By default, the device will send an uplink message every 2 hour.**
  == 2.3  Uplink Payload ==
@@ -267,6 +267,10 @@
  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.
++(% style="width:934px" %)
++|(% style="width:93px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:41px" %)**2**|(% style="width:126px" %)**1**|(% style="width:54px" %)**1**|(% style="width:84px" %)1|(% style="width:75px" %)2|(% style="width:133px" %)2|(% style="width:70px" %)2|(% style="width:127px" %)4
++|(% style="width:93px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:41px" %)BAT|(% style="width:126px" %)Signal Strength|(% style="width:54px" %)MOD|(% style="width:84px" %)Interrupt|(% style="width:75px" %)Soil PH|(% style="width:133px" %)Soil Temperature|(% style="width:70px" %)Soil PH|(% style="width:127px" %)Time stamp  .....
++
  |**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
  |**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Soil PH|Soil Temperature|Time stamp|Soil Temperature|Soil PH|Time stamp  .....
@@ -278,19 +278,20 @@
  The payload is ASCII string, representative same HEX:
--0x(% style="color:red" %)f868411056754138(% style="color:blue" %)0064(% style="color:green" %)0c78(% style="color:red" %)17(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//0225010b6315537b//**010b0226631550fb//**010e022663154d77**//01110225631549f1//**011502246315466b**//01190223631542e5//**011d022163153f62**//011e022163153bde//**011e022163153859**//(%%) where:
++0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where:
--* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
--* (% style="color:blue" %)Version: 0x0064=100=1.0.0
--* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
--* (% style="color:red" %)Singal: 0x17 = 23
--* (% style="color:blue" %)Mod: 0x01 = 1
--* (% style="color:green" %)Interrupt: 0x00= 0
++* Device ID: 0xf868411056754138 = f868411056754138
++* Version: 0x0064=100=1.0.0
++
++* BAT: 0x0c78 = 3192 mV = 3.192V
++* Singal: 0x17 = 23
++* Mod: 0x01 = 1
++* Interrupt: 0x00= 0
  * Soil PH: 0x0225= 549 = 5.49
  * Soil Temperature:0x010B =267=26.7 °C
--* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
++* Time stamp : 0x6315537b =1662342011
  * Soil Temperature,Soil PH,Time stamp : 010b0226631550fb
--* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
++* 8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
  == 2.4  Payload Explanation and Sensor Interface ==
@@ -298,7 +298,7 @@
  By default, the Device ID equal to the last 15 bits of IMEI.
--User can use **(% style="color:blue" %)AT+DEUI** (%%)to set Device ID
++User can use **AT+DEUI** to set Device ID
  **Example:**
@@ -497,9 +497,9 @@
  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.10 Read or Clear cached data ==
  ➢ AT Command:
@@ -534,7 +534,7 @@
  The battery is designed to last for several years depends on the actually use environment and update interval.
--The battery-related documents as below:
++The battery related documents as below:
  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
@@ -622,18 +622,13 @@
  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+TEMPALARM      : Get or Set alarm of temp
  AT+PHALARM     : Get or Set alarm of PH
@@ -699,7 +699,7 @@
  **Package Includes**:
--* NSPH01 NB-IoT pH Sensor x 1
++* NSPH01 NB-IoT Soil Moisture & EC Sensor x 1
  * External antenna x 1
  **Dimension and weight**:

image-20220912144017-1.png

Author

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

Size

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

Content

Changes for page NSPH01-NB-IoT Soil pH Sensor User Manual

Summary

Details

Applications

Navigation