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 < 46.1 >
edited by Edwin Chen
on 2022/09/08 00:00
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png||height="442" width="410"]]
2 +[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png]]
3 3  
4 4  **Table of Contents:**
5 5  
... ... @@ -7,32 +7,27 @@
7 7  
8 8  
9 9  
10 -= 1.  Introduction =
10 += 1. Introduction =
11 11  
12 +== 1.1 ​What is NSPH01 Soil pH Sensor ==
12 12  
13 -== 1.1 ​ What is NSPH01 Soil pH Sensor ==
14 +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.
14 14  
16 +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.
15 15  
16 -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.
17 -
18 -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.
19 -
20 20  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.
21 -\\NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
22 -\\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)
23 -\\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.
19 +\\NSPH01 supports different uplink methods include **TCP,MQTT,UDP and CoAP  **for different application requirement.
20 +\\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)
21 +\\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 **NB-IoT SIM card** from local operator and install NSPH01 to get NB-IoT network connection.
24 24  
25 -
23 +(% style="text-align:center" %)
26 26  [[image:image-20220907153151-1.png]]
27 27  
28 -
26 +(% style="text-align:center" %)
29 29  [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]]
30 30  
29 +== 1.2 Features ==
31 31  
32 -
33 -== 1.2  Features ==
34 -
35 -
36 36  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
37 37  * Monitor soil pH with temperature compensation.
38 38  * Monitor soil temperature
... ... @@ -50,13 +50,12 @@
50 50  
51 51  == 1.3  Specification ==
52 52  
48 +**Common DC Characteristics:**
53 53  
54 -(% style="color:#037691" %)**Common DC Characteristics:**
55 -
56 56  * Supply Voltage: 2.1v ~~ 3.6v
57 57  * Operating Temperature: -40 ~~ 85°C
58 58  
59 -(% style="color:#037691" %)**NB-IoT Spec:**
53 +**NB-IoT Spec:**
60 60  
61 61  * - B1 @H-FDD: 2100MHz
62 62  * - B3 @H-FDD: 1800MHz
... ... @@ -65,11 +65,10 @@
65 65  * - B20 @H-FDD: 800MHz
66 66  * - B28 @H-FDD: 700MHz
67 67  
68 -== 1.4  Probe Specification ==
62 +== 1.4 Probe Specification ==
69 69  
64 +**Soil pH:**
70 70  
71 -(% style="color:#037691" %)**Soil pH:**
72 -
73 73  * Range: 3 ~~ 10 pH
74 74  * Resolution: 0.01 pH
75 75  * Accuracy: ±2% under (0~~50 ℃, Accuracy will poor under 0 due to frozen)
... ... @@ -77,7 +77,7 @@
77 77  * IP68 Protection
78 78  * Length: 3.5 meters
79 79  
80 -(% style="color:#037691" %)**Soil Temperature:**
73 +**Soil Temperature:**
81 81  
82 82  * Range -40℃～85℃
83 83  * Resolution: 0.1℃
... ... @@ -91,32 +91,25 @@
91 91  
92 92  == 1.6 Pin mapping and power on ==
93 93  
94 -
87 +(% style="text-align:center" %)
95 95  [[image:image-20220907153300-2.png]]
96 96  
97 97  
98 -
99 99  = 2.  Use NSPH01 to communicate with IoT Server =
100 100  
101 -
102 102  == 2.1  How it works ==
103 103  
104 -
105 105  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.
106 106  
107 107  The diagram below shows the working flow in default firmware of NSPH01:
108 108  
109 -
99 +(% style="text-align:center" %)
110 110  [[image:image-20220907153416-3.png]]
111 111  
112 -
113 -
114 114  == 2.2 ​ Configure the NSPH01 ==
115 115  
116 -
117 117  === 2.2.1 Test Requirement ===
118 118  
119 -
120 120  To use NSPH01 in the field, make sure meet below requirements:
121 121  
122 122  * Your local operator has already distributed a NB-IoT Network there.
... ... @@ -125,91 +125,77 @@
125 125  
126 126  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.
127 127  
128 -
114 +(% style="text-align:center" %)
129 129  [[image:image-20220907153445-4.png]]
130 130  
131 131  
132 -
133 133  === 2.2.2 Insert SIM card ===
134 134  
120 +User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
135 135  
136 -User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
137 -
122 +(% style="text-align:center" %)
138 138  [[image:image-20220907153505-5.png]]
139 139  
140 -
141 -
142 142  === 2.2.3 Connect USB – TTL to NSPH01 to configure it ===
143 143  
127 +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.
144 144  
145 -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.
129 +**Connection:**
146 146  
131 + USB TTL GND <~-~-~-~-> GND
147 147  
148 -(% style="color:blue" %)**Connection:**
133 + USB TTL TXD <~-~-~-~-> UART_RXD
149 149  
150 -**~ (% style="background-color:yellow" %) USB TTL GND <~-~-~-~->  GND(%%)**
135 + USB TTL RXD <~-~-~-~-> UART_TXD
151 151  
152 -**~ (% style="background-color:yellow" %) USB TTL TXD  <~-~-~-~->  UART_RXD(%%)**
153 -
154 -**~ (% style="background-color:yellow" %) USB TTL RXD  <~-~-~-~->  UART_TXD(%%)**
155 -
156 -
157 157  In the PC, use below serial tool settings:
158 158  
159 -* Baud:  (% style="color:green" %)**9600**
160 -* Data bits:**  (% style="color:green" %)8(%%)**
161 -* Stop bits:  (% style="color:green" %)**1**
162 -* Parity:  (% style="color:green" %)**None**
163 -* Flow Control: (% style="color:green" %)**None**
164 -*
139 +* Baud:  **9600**
140 +* Data bits:** 8**
141 +* Stop bits: **1**
142 +* Parity:  **None**
143 +* Flow Control: **None**
165 165  
166 -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.
145 +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.
167 167  
147 +(% style="text-align:center" %)
148 +[[image:image-20220907153529-6.png]]
168 168  
169 -[[image:image-20220912144017-1.png]]
150 +**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]]
170 170  
171 -
172 -(% 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]]
173 -
174 -
175 -
176 176  === 2.2.4 Use CoAP protocol to uplink data ===
177 177  
154 +**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/]]
178 178  
179 -(% 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/]]
156 +**Use below commands:**
180 180  
158 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
159 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
160 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
181 181  
182 -(% style="color:blue" %)**Use below commands:**
183 -
184 -* (% style="color:#037691" %)**AT+PRO=1**                         (%%) ~/~/  Set to use CoAP protocol to uplink
185 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
186 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
187 -
188 188  For parameter description, please refer to AT command set
189 189  
190 -
164 +(% style="text-align:center" %)
191 191  [[image:image-20220907153551-7.png||height="502" width="740"]]
192 192  
167 +After configure the server address and **reset the device** (via AT+ATZ ), NSPH01 will start to uplink sensor values to CoAP server.
193 193  
194 -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.
195 -
196 -
169 +(% style="text-align:center" %)
197 197  [[image:image-20220907153612-8.png||height="529" width="729"]]
198 198  
199 199  
200 -
201 201  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
202 202  
203 -
204 204  This feature is supported since firmware version v1.0.1
205 -(%%)
206 -* **(% style="color:blue" %)AT+PRO=2   ** ~/~/  Set to use UDP protocol to uplink
207 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
208 -* **(% style="color:blue" %)AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
209 209  
177 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
178 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
179 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessar
180 +
181 +(% style="text-align:center" %)
210 210  [[image:image-20220907153643-9.png||height="401" width="734"]]
211 211  
212 -
184 +(% style="text-align:center" %)
213 213  [[image:image-20220907153703-10.png||height="309" width="738"]]
214 214  
215 215  
... ... @@ -217,49 +217,44 @@
217 217  
218 218  This feature is supported since firmware version v110
219 219  
220 -* **(% style="color:blue" %)AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
221 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
222 -* **(% style="color:blue" %)AT+CLIENT=CLIENT       ** (%%) ~/~/Set up the CLIENT of MQTT
223 -* **(% style="color:blue" %)AT+UNAME=UNAME                               ** (%%)~/~/Set the username of MQTT
224 -* **(% style="color:blue" %)AT+PWD=PWD                                        ** (%%)~/~/Set the password of MQTT
225 -* **(% style="color:blue" %)AT+PUBTOPIC=NSE01_PUB                    **(%%) ~/~/Set the sending topic of MQTT
226 -* **(% style="color:blue" %)AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/Set the subscription topic of MQTT
192 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
193 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
194 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
195 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
196 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
197 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
198 +* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
227 227  
228 -
200 +(% style="text-align:center" %)
229 229  [[image:image-20220907153739-11.png||height="491" width="764"]]
230 230  
231 -
203 +(% style="text-align:center" %)
232 232  [[image:image-20220907153751-12.png||height="555" width="769"]]
233 233  
234 234  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.
235 235  
236 -
237 -
238 -
239 239  === 2.2.7 Use TCP protocol to uplink data ===
240 240  
241 241  This feature is supported since firmware version v110
242 242  
243 -* **(% style="color:blue" %)AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
244 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ to set TCP server address and port
212 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
213 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
245 245  
246 -
215 +(% style="text-align:center" %)
247 247  [[image:image-20220907153818-13.png||height="486" width="668"]]
248 248  
249 -
218 +(% style="text-align:center" %)
250 250  [[image:image-20220907153827-14.png||height="236" width="684"]]
251 251  
252 -
253 -
254 -
255 255  === 2.2.8 Change Update Interval ===
256 256  
257 -Users can use the below command to change the **uplink interval**.
223 +User can use below command to change the **uplink interval**.
258 258  
259 -* **(% style="color:blue" %)AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
225 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
260 260  
261 -**(% 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).**
227 +**NOTE:**
262 262  
229 +**~1. By default, the device will send an uplink message every 2 hour.**
263 263  
264 264  == 2.3  Uplink Payload ==
265 265  
... ... @@ -278,19 +278,20 @@
278 278  
279 279  The payload is ASCII string, representative same HEX:
280 280  
281 -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:
248 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where:
282 282  
283 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
284 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0
285 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
286 -* (% style="color:red" %)Singal: 0x17 = 23
287 -* (% style="color:blue" %)Mod: 0x01 = 1
288 -* (% style="color:green" %)Interrupt: 0x00= 0
250 +* Device ID: 0xf868411056754138 = f868411056754138
251 +* Version: 0x0064=100=1.0.0
252 +
253 +* BAT: 0x0c78 = 3192 mV = 3.192V
254 +* Singal: 0x17 = 23
255 +* Mod: 0x01 = 1
256 +* Interrupt: 0x00= 0
289 289  * Soil PH: 0x0225= 549 = 5.49
290 290  * Soil Temperature:0x010B =267=26.7 °C
291 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
259 +* Time stamp : 0x6315537b =1662342011
292 292  * Soil Temperature,Soil PH,Time stamp : 010b0226631550fb
293 -* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
261 +* 8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
294 294  
295 295  == 2.4  Payload Explanation and Sensor Interface ==
296 296  
... ... @@ -298,7 +298,7 @@
298 298  
299 299  By default, the Device ID equal to the last 15 bits of IMEI.
300 300  
301 -User can use **(% style="color:blue" %)AT+DEUI** (%%)to set Device ID
269 +User can use **AT+DEUI** to set Device ID
302 302  
303 303  **Example:**
304 304  
... ... @@ -497,9 +497,9 @@
497 497  
498 498  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)
499 499  
468 +
500 500  AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
501 501  
502 -
503 503  == 2.10 Read or Clear cached data ==
504 504  
505 505  ➢ AT Command:
... ... @@ -534,7 +534,7 @@
534 534  
535 535  The battery is designed to last for several years depends on the actually use environment and update interval. 
536 536  
537 -The battery-related documents as below:
505 +The battery related documents as below:
538 538  
539 539  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
540 540  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -622,18 +622,13 @@
622 622  
623 623  AT+TR      : Get or Set record time"
624 624  
625 -AT+APN     : Get or set the APN
626 626  
627 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
628 -
629 -AT+DNSCFG  : Get or Set DNS Server
630 -
631 -AT+GETSENSORVALUE   : Returns the current sensor measurement
632 -
633 633  AT+NOUD      : Get or Set the number of data to be uploaded
634 634  
596 +
635 635  AT+CDP     : Read or Clear cached data
636 636  
599 +
637 637  AT+TEMPALARM      : Get or Set alarm of temp
638 638  
639 639  AT+PHALARM     : Get or Set alarm of PH
... ... @@ -699,7 +699,7 @@
699 699  
700 700  **Package Includes**:
701 701  
702 -* NSPH01 NB-IoT pH Sensor x 1
665 +* NSPH01 NB-IoT Soil Moisture & EC Sensor x 1
703 703  * External antenna x 1
704 704  
705 705  **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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0