<
From version < 56.25 >
edited by Xiaoling
on 2024/01/18 14:17
To version < 51.3 >
edited by Xiaoling
on 2022/09/12 15:01
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,16 +3,6 @@
1 -
2 -
3 3  (% style="text-align:center" %)
4 4  [[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png||height="442" width="410"]]
5 5  
6 -
7 -
8 -
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents:**
15 15  
16 16  {{toc/}}
... ... @@ -19,34 +19,20 @@
19 19  
20 20  = 1.  Introduction =
21 21  
12 +
22 22  == 1.1 ​ What is NSPH01 Soil pH Sensor ==
23 23  
24 24  
25 -(((
26 26  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.
27 -)))
28 28  
29 -(((
30 30  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.
31 -)))
32 32  
33 -(((
34 34  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.
35 -)))
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.
36 36  
37 -(((
38 -NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
39 -)))
40 40  
41 -(((
42 -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)
43 -)))
44 -
45 -(((
46 -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.
47 -)))
48 -
49 -
50 50  [[image:image-20220907153151-1.png]]
51 51  
52 52  
... ... @@ -53,6 +53,7 @@
53 53  [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]]
54 54  
55 55  
32 +
56 56  == 1.2  Features ==
57 57  
58 58  
... ... @@ -81,12 +81,12 @@
81 81  
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
84 -* B1 @H-FDD: 2100MHz
85 -* B3 @H-FDD: 1800MHz
86 -* B8 @H-FDD: 900MHz
87 -* B5 @H-FDD: 850MHz
88 -* B20 @H-FDD: 800MHz
89 -* B28 @H-FDD: 700MHz
61 +* - B1 @H-FDD: 2100MHz
62 +* - B3 @H-FDD: 1800MHz
63 +* - B8 @H-FDD: 900MHz
64 +* - B5 @H-FDD: 850MHz
65 +* - B20 @H-FDD: 800MHz
66 +* - B28 @H-FDD: 700MHz
90 90  
91 91  == 1.4  Probe Specification ==
92 92  
... ... @@ -108,19 +108,20 @@
108 108  * IP68 Protection
109 109  * Length: 3.5 meters
110 110  
111 -== 1.5  ​Applications ==
88 +== 1.5 ​Applications ==
112 112  
113 -
114 114  * Smart Agriculture
115 115  
116 -== 1.6  Pin mapping and power on ==
92 +== 1.6 Pin mapping and power on ==
117 117  
118 118  
119 119  [[image:image-20220907153300-2.png]]
120 120  
121 121  
98 +
122 122  = 2.  Use NSPH01 to communicate with IoT Server =
123 123  
101 +
124 124  == 2.1  How it works ==
125 125  
126 126  
... ... @@ -132,8 +132,10 @@
132 132  [[image:image-20220907153416-3.png]]
133 133  
134 134  
113 +
135 135  == 2.2 ​ Configure the NSPH01 ==
136 136  
116 +
137 137  === 2.2.1 Test Requirement ===
138 138  
139 139  
... ... @@ -143,21 +143,22 @@
143 143  * The local NB-IoT network used the band that NSPH01 supports.
144 144  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
145 145  
146 -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.
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.
147 147  
148 148  
149 149  [[image:image-20220907153445-4.png]]
150 150  
151 151  
132 +
152 152  === 2.2.2 Insert SIM card ===
153 153  
154 154  
155 155  User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
156 156  
157 -
158 158  [[image:image-20220907153505-5.png]]
159 159  
160 160  
141 +
161 161  === 2.2.3 Connect USB – TTL to NSPH01 to configure it ===
162 162  
163 163  
... ... @@ -180,14 +180,18 @@
180 180  * Stop bits:  (% style="color:green" %)**1**
181 181  * Parity:  (% style="color:green" %)**None**
182 182  * Flow Control: (% style="color:green" %)**None**
164 +*
183 183  
184 184  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.
185 185  
168 +
186 186  [[image:image-20220912144017-1.png]]
187 187  
171 +
188 188  (% 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]]
189 189  
190 190  
175 +
191 191  === 2.2.4 Use CoAP protocol to uplink data ===
192 192  
193 193  
... ... @@ -212,15 +212,16 @@
212 212  [[image:image-20220907153612-8.png||height="529" width="729"]]
213 213  
214 214  
200 +
215 215  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
216 216  
217 217  
218 218  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
219 219  
220 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
221 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
222 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
223 -
224 224  [[image:image-20220907153643-9.png||height="401" width="734"]]
225 225  
226 226  
... ... @@ -229,34 +229,35 @@
229 229  
230 230  === 2.2.6 Use MQTT protocol to uplink data ===
231 231  
232 -
233 233  This feature is supported since firmware version v110
234 234  
235 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/ Set to use MQTT protocol to uplink
236 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/ Set MQTT server address and port
237 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/ Set up the CLIENT of MQTT
238 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/ Set the username of MQTT
239 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/ Set the password of MQTT
240 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/ Set the sending topic of MQTT
241 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/ Set the subscription topic of MQTT
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
242 242  
228 +
243 243  [[image:image-20220907153739-11.png||height="491" width="764"]]
244 244  
245 245  
246 246  [[image:image-20220907153751-12.png||height="555" width="769"]]
247 247  
248 -
249 249  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.
250 250  
251 251  
252 -=== 2.2.7 Use TCP protocol to uplink data ===
253 253  
254 254  
239 +=== 2.2.7 Use TCP protocol to uplink data ===
240 +
255 255  This feature is supported since firmware version v110
256 256  
257 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
258 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ to set TCP server address and port
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
259 259  
246 +
260 260  [[image:image-20220907153818-13.png||height="486" width="668"]]
261 261  
262 262  
... ... @@ -263,82 +263,56 @@
263 263  [[image:image-20220907153827-14.png||height="236" width="684"]]
264 264  
265 265  
266 -=== 2.2.8 Change Update Interval ===
267 267  
268 268  
255 +=== 2.2.8 Change Update Interval ===
256 +
269 269  Users can use the below command to change the **uplink interval**.
270 270  
271 -* (% style="color:blue" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
259 +* **(% style="color:blue" %)AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
272 272  
273 -(% 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).**
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).**
274 274  
275 275  
276 276  == 2.3  Uplink Payload ==
277 277  
278 -
279 279  In this mode, uplink payload includes 87 bytes in total by default.
280 280  
281 281  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.
282 282  
283 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
284 -|(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:20px" %)**2**|(% style="background-color:#4f81bd; color:white; width:23px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:20px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:51px" %)**2**|(% style="background-color:#4f81bd; color:white; width:49px" %)**4**|(% style="background-color:#4f81bd; color:white; width:49px" %)**2**|(% style="background-color:#4f81bd; color:white; width:34px" %)**2**|(% style="background-color:#4f81bd; color:white; width:39px" %)**4**
285 -|(% style="width:96px" %)Value|(% style="width:83px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:42px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:57px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:69px" %)Soil PH|(% style="width:134px" %)Soil Temperature|(% style="width:98px" %)Time stamp|(% style="width:134px" %)Soil Temperature|(% style="width:68px" %)Soil PH|(% style="width:125px" %)Time stamp  .....
270 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
271 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Soil PH|Soil Temperature|Time stamp|Soil Temperature|Soil PH|Time stamp  .....
286 286  
287 287  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
288 288  
275 +(% style="text-align:center" %)
289 289  [[image:image-20220907153902-15.png||height="581" width="804"]]
290 290  
291 291  
292 -(((
293 293  The payload is ASCII string, representative same HEX:
294 -)))
295 295  
296 -(((
297 -
298 -)))
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:
299 299  
300 -(((
301 -**0x (% style="color:red" %)__f868411056754138__  (% style="color:blue" %)__0064 __ (% style="color:green" %)__0c78__  (% style="color:#00b0f0" %)__17__  (% style="color:#7030a0" %)__01__  (% style="color:#d60093" %)__00__  (% style="color:#a14d07" %)__0225 __ (% style="color:#0020b0" %) __010b__  (% style="color:#420042" %)__6315537b__  (% style="color:#663300" %)//__010b0226631550fb__  __010e022663154d77  01110225631549f1  011502246315466b  01190223631542e5  011d022163153f62  011e022163153bde 011e022163153859__//(%%)**
302 -)))
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
289 +* Soil PH: 0x0225= 549 = 5.49
290 +* Soil Temperature:0x010B =267=26.7 °C
291 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
292 +* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb
293 +* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
303 303  
304 -(((
305 -
306 -
307 -**where:**
308 -)))
309 -
310 -* (% style="color:#037691" %)**Device ID:**(%%)** **0xf868411056754138 = f868411056754138
311 -
312 -* (% style="color:#037691" %)**Version:**  (%%) 0x0064=100=1.0.0
313 -
314 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0c78 = 3192 mV = 3.192V
315 -
316 -* (% style="color:#037691" %)**Singal:** (%%)0x17 = 23
317 -
318 -* (% style="color:#037691" %)**Mod:** (%%) 0x01 = 1
319 -
320 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
321 -
322 -* (% style="color:#037691" %)**Soil PH:** (%%) 0x0225= 549 = 5.49
323 -
324 -* (% style="color:#037691" %)**Soil Temperature:**(%%) 0x010b =267=26.7 °C
325 -
326 -* (% style="color:#037691" %)**Time stamp :**   (%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
327 -
328 -* (% style="color:#037691" %)**Soil Temperature,Soil PH,Time stamp : **(%%) 010b0226631550fb
329 -
330 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%) Temperature,Soil PH,Time stamp :  010e022663154d77,.......
331 -
332 332  == 2.4  Payload Explanation and Sensor Interface ==
333 333  
334 334  === 2.4.1  Device ID ===
335 335  
336 -
337 337  By default, the Device ID equal to the last 15 bits of IMEI.
338 338  
339 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
301 +User can use **(% style="color:blue" %)AT+DEUI** (%%)to set Device ID
340 340  
341 -
342 342  **Example:**
343 343  
344 344  AT+DEUI=868411056754138
... ... @@ -345,18 +345,14 @@
345 345  
346 346  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
347 347  
348 -
349 349  === 2.4.2  Version Info ===
350 350  
351 -
352 352  Specify the software version: 0x64=100, means firmware version 1.00.
353 353  
354 354  For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0.
355 355  
356 -
357 357  === 2.4.3  Battery Info ===
358 358  
359 -
360 360  Check the battery voltage for NSPH01.
361 361  
362 362  Ex1: 0x0B45 = 2885mV
... ... @@ -363,10 +363,8 @@
363 363  
364 364  Ex2: 0x0B49 = 2889mV
365 365  
366 -
367 367  === 2.4.4  Signal Strength ===
368 368  
369 -
370 370  NB-IoT Network signal Strength.
371 371  
372 372  **Ex1: 0x1d = 29**
... ... @@ -381,23 +381,18 @@
381 381  
382 382  **99**    Not known or not detectable
383 383  
384 -
385 385  === 2.4.5  Soil PH ===
386 386  
387 -
388 388  Get the PH content of the soil. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of PH in the soil.
389 389  
390 -For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is
343 +For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is
391 391  
392 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**
345 +**0229(H) = 549(D) /100 = 5.49.**
393 393  
394 -
395 395  === 2.4.6  Soil Temperature ===
396 396  
349 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the soil is
397 397  
398 -Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is (% style="color:blue" %)**__0x09 0xEC__**(%%), the temperature content in the soil is
399 -
400 -
401 401  **Example**:
402 402  
403 403  If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
... ... @@ -404,42 +404,35 @@
404 404  
405 405  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
406 406  
407 -
408 408  === 2.4.7  Timestamp ===
409 409  
410 -
411 411  Time stamp : 0x6315537b =1662342011
412 412  
413 413  Convert Unix timestamp to time 2022-9-5 9:40:11.
414 414  
415 -
416 416  === 2.4.8  Digital Interrupt ===
417 417  
365 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NSPH01 will send a packet to the server.
418 418  
419 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSPH01 will send a packet to the server.
420 -
421 421  The command is:
422 422  
423 -(% 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]])**.**
369 +**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]])**.**
424 424  
425 425  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.
426 426  
373 +Example:
427 427  
428 -**Example:**
429 -
430 430  0x(00): Normal uplink packet.
431 431  
432 432  0x(01): Interrupt Uplink Packet.
433 433  
434 -
435 435  === 2.4.9  ​+5V Output ===
436 436  
437 -
438 438  NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 
439 439  
440 440  The 5V output time can be controlled by AT Command.
441 441  
442 -(% style="color:blue" %)**AT+5VT=1000**
385 +**AT+5VT=1000**
443 443  
444 444  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
445 445  
... ... @@ -446,19 +446,21 @@
446 446  
447 447  == 2.5  Downlink Payload ==
448 448  
449 -
450 450  By default, NSPH01 prints the downlink payload to console port.
451 451  
452 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
453 -|=(% style="width: 183px; background-color:#4F81BD;color:white" %)**Downlink Control Type**|=(% style="width: 55px; background-color:#4F81BD;color:white" %)FPort|=(% style="width: 93px; background-color:#4F81BD;color:white" %)**Type Code**|=(% style="width: 179px; background-color:#4F81BD;color:white" %)**Downlink payload size(bytes)**
454 -|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4
455 -|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2
456 -|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4
394 +(% style="text-align:center" %)
395 +[[image:image-20220907154636-17.png]]
457 457  
458 -(% style="color:blue" %)**Examples:**
459 459  
460 -* (% style="color:#037691" %)** Set TDC**
461 461  
399 +
400 +
401 +
402 +
403 +**Examples:**
404 +
405 +* **Set TDC**
406 +
462 462  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
463 463  
464 464  Payload:    01 00 00 1E    TDC=30S
... ... @@ -465,18 +465,16 @@
465 465  
466 466  Payload:    01 00 00 3C    TDC=60S
467 467  
468 -* (% style="color:#037691" %)** Reset**
413 +* **Reset**
469 469  
470 470  If payload = 0x04FF, it will reset the NSPH01
471 471  
472 -* (% style="color:#037691" %)** INTMOD**
417 +* **INTMOD**
473 473  
474 474  Downlink Payload: 06000003, Set AT+INTMOD=3
475 475  
476 -
477 477  == 2.6  ​LED Indicator ==
478 478  
479 -
480 480  The NSPH01 has an internal LED which is to show the status of different state.
481 481  
482 482  * When power on, NSPH01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
... ... @@ -484,20 +484,16 @@
484 484  * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds.
485 485  * For each uplink probe, LED will be on for 500ms.
486 486  
487 -== 2.7  Installation and Maintain ==
430 +== 2.7 Installation and Maintain ==
488 488  
489 -=== 2.7.1  Before measurement ===
432 +=== 2.7.1 Before measurement ===
490 490  
491 -
492 492  If the NSPH01 has more than 7 days not use or just clean the pH probe. User should put the probe inside pure water for more than 24 hours for activation. If no put in water, user need to put inside soil for more than 24 hours to ensure the measurement accuracy. 
493 493  
436 +=== 2.7.2 Measurement ===
494 494  
495 -=== 2.7.2  Measurement ===
438 +**Measurement the soil surface:**
496 496  
497 -
498 -(% style="color:#037691" %)**Measurement the soil surface:**
499 -
500 -
501 501  [[image:image-20220907154700-18.png]] ​
502 502  
503 503  Choose the proper measuring position. Split the surface soil according to the measured deep.
... ... @@ -508,17 +508,14 @@
508 508  
509 509  Put soil over the probe after insert. And start to measure.
510 510  
450 +**Measurement inside soil:**
511 511  
512 -(% style="color:#037691" %)**Measurement inside soil:**
513 -
514 514  Dig a hole with diameter > 20CM.
515 515  
516 516  Insert the probe inside, method like measure the surface.
517 517  
456 +=== 2.7.3 Maintain Probe ===
518 518  
519 -=== 2.7.3  Maintain Probe ===
520 -
521 -
522 522  1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
523 523  1. After long time use (3~~ 6  months). The probe electrode needs to be clean; user can use high grade sandpaper to polish it or put in 5% hydrochloric acid for several minutes. After the metal probe looks like new, user can use pure water to wash it.
524 524  1. Probe reference electrode is also no strong, need to avoid strong force or hitting.
... ... @@ -526,13 +526,12 @@
526 526  1. Avoid the probes to touch oily matter. Which will cause issue in accuracy.
527 527  1. The probe is IP68 can be put in water.
528 528  
529 -== 2.8  PH and Temperature alarm function ==
465 +== 2.8 PH and Temperature alarm function ==
530 530  
467 +➢ AT Command:
531 531  
532 -(% style="color:#037691" %)**➢ AT Command:**
469 +AT+ PHALARM=min,max
533 533  
534 -(% style="color:blue" %)**AT+ PHALARM=min,max**
535 -
536 536  ² When min=3, and max≠0, Alarm higher than max
537 537  
538 538  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -539,11 +539,10 @@
539 539  
540 540  ² When min≠0 and max≠0, Alarm higher than max or lower than min
541 541  
477 +Example:
542 542  
543 -(% style="color:blue" %)**Example:**
479 +AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5.
544 544  
545 -AT+ PHALARM =5,8  ~/~/ Alarm when PH lower than 5.
546 -
547 547  AT+ TEMPALARM=min,max
548 548  
549 549  ² When min=0, and max≠0, Alarm higher than max
... ... @@ -552,95 +552,98 @@
552 552  
553 553  ² When min≠0 and max≠0, Alarm higher than max or lower than min
554 554  
489 +Example:
555 555  
556 -(% style="color:blue" %)**Example:**
491 +AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
557 557  
558 -AT+ TEMPALARM=20,30  ~/~/ Alarm when temperature lower than 20.
559 559  
494 +== 2.9 Set the number of data to be uploaded and the recording time ==
560 560  
561 -== 2.9  Set the number of data to be uploaded and the recording time ==
496 + AT Command:
562 562  
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)
563 563  
564 -(% style="color:#037691" %)**➢ AT Command:**
500 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
565 565  
566 -* (% style="color:blue" %)**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)
567 -* (% style="color:blue" %)**AT+NOUD=8**     (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
568 568  
569 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
503 +== 2.10 Read or Clear cached data ==
570 570  
571 -[[image:image-20221009000933-1.png||height="750" width="1043"]]
505 +➢ AT Command:
572 572  
507 +AT+CDP ~/~/ Read cached data
573 573  
574 -== 2.10  Read or Clear cached data ==
509 +[[image:image-20220907154700-19.png]]
575 575  
576 576  
577 -(% style="color:#037691" %)**➢ AT Command:**
512 +AT+CDP=0 ~/~/ Clear cached data
578 578  
579 -* (% style="color:blue" %)**AT+CDP**        (%%) ~/~/  Read cached data
580 -* (% style="color:blue" %)**AT+CDP=0**    (%%) ~/~/  Clear cached data
581 581  
582 -[[image:image-20220907154700-19.png]]
515 +== 2.11 Calibration ==
583 583  
517 +User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable).
584 584  
585 -== 2.11  Calibration ==
519 +After stable, user can use below command to calibrate.
586 586  
521 +[[image:image-20220907154700-20.png]] ​
587 587  
588 -User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable).
523 +== 2.12  ​Firmware Change Log ==
589 589  
590 -After stable, user can use below command to calibrate.
525 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
591 591  
592 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
593 -|(% style="background-color:#4f81bd; color:white; width:118px" %)**pH buffer solution**|(% style="background-color:#4f81bd; color:white; width:149px" %)**AT Command to calibrate**|(% style="background-color:#4f81bd; color:white; width:149px" %)**Downlink Command**|(% style="background-color:#4f81bd; color:white; width:99px" %)**Read Cal Value**
594 -|(% style="width:149px" %)4.00|(% style="width:197px" %)AT+PHCAL=4|(% style="width:206px" %)(((
595 -0x13 04
596 -Reply with Calibrate payload
597 -)))|(% style="width:136px" %)(((
598 -AT+PHCAL=?
599 -Example 41,61,91
600 -)))
601 -|(% style="width:149px" %)6.86|(% style="width:197px" %)AT+PHCAL=6|(% style="width:206px" %)(((
602 -0x13 06
603 -Reply with Calibrate payload
604 -)))|(% style="width:136px" %)AT+PHCAL=?
605 -|(% style="width:149px" %)9.18|(% style="width:197px" %)AT+PHCAL=9|(% style="width:206px" %)(((
606 -0x13 09
607 -Reply with Calibrate payload
608 -)))|(% style="width:136px" %)AT+PHCAL=?
609 -|(% style="width:149px" %)Factory Default|(% style="width:197px" %)AT+PHCAL=15|(% style="width:206px" %)(((
610 -0x13 15
611 -Reply with Calibrate payload
612 -)))|(% style="width:136px" %)(((
613 -AT+PHCAL=?
614 -Example 151
615 -)))
527 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
616 616  
617 - ​
529 +== 2.13  Battery Analysis ==
618 618  
531 +=== 2.13.1  ​Battery Type ===
619 619  
620 -== 2.1 ​Firmware Change Log ==
533 +The NSPH01 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.
621 621  
535 +The battery is designed to last for several years depends on the actually use environment and update interval. 
622 622  
623 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0>>https://www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0]]
537 +The battery-related documents as below:
624 624  
625 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
539 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
540 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
541 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
626 626  
543 +[[image:image-20220907154700-21.png]] ​
627 627  
628 -== 2.13 Battery & Power Consumption ==
545 +=== 2.13.2  Power consumption Analyze ===
629 629  
547 +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.
630 630  
631 -NSPH01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
549 +Instruction to use as below:
632 632  
633 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
551 +**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/]]
634 634  
553 +**Step 2: ** Open it and choose
635 635  
636 -= 3. ​ Access NB-IoT Module =
555 +* Product Model
556 +* Uplink Interval
557 +* Working Mode
637 637  
559 +And the Life expectation in difference case will be shown on the right.
638 638  
561 +(% style="text-align:center" %)
562 +[[image:image-20220907154700-22.jpeg]]
563 +
564 +​
565 +
566 +=== 2.13.3  ​Battery Note ===
567 +
568 +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.
569 +
570 +=== 2.13.4  Replace the battery ===
571 +
572 +The default battery pack of NSPH01 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).
573 +
574 += 3. ​ Access NB-IoT Module =
575 +
639 639  Users can directly access the AT command set of the NB-IoT module.
640 640  
641 641  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/]] 
642 642  
643 -
580 +(% style="text-align:center" %)
644 644  [[image:image-20220907154700-23.png]]
645 645  
646 646  ​
... ... @@ -649,7 +649,6 @@
649 649  
650 650  == 4.1  Access AT Commands ==
651 651  
652 -
653 653  See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
654 654  
655 655  AT+<CMD>?  : Help on <CMD>
... ... @@ -660,9 +660,8 @@
660 660  
661 661  AT+<CMD>=?  : Get the value
662 662  
599 +**General Commands**      
663 663  
664 -(% style="color:#037691" %)**General Commands**      
665 -
666 666  AT  : Attention       
667 667  
668 668  AT?  : Short Help     
... ... @@ -706,18 +706,16 @@
706 706  AT+ PHCAL  : calibrate PH value
707 707  
708 708  
709 -(% style="color:#037691" %)**COAP Management**      
644 +**COAP Management**      
710 710  
711 711  AT+URI            : Resource parameters
712 712  
648 +**UDP Management**
713 713  
714 -(% style="color:#037691" %)**UDP Management**
715 -
716 716  AT+CFM          : Upload confirmation mode (only valid for UDP)
717 717  
652 +**MQTT Management**
718 718  
719 -(% style="color:#037691" %)**MQTT Management**
720 -
721 721  AT+CLIENT               : Get or Set MQTT client
722 722  
723 723  AT+UNAME  : Get or Set MQTT Username
... ... @@ -728,61 +728,42 @@
728 728  
729 729  AT+SUBTOPIC  : Get or Set MQTT subscription topic
730 730  
664 +**Information**          
731 731  
732 -(% style="color:#037691" %)**Information**          
733 -
734 734  AT+FDR  : Factory Data Reset
735 735  
736 736  AT+PWORD  : Serial Access Password
737 737  
738 -
739 739  = ​5.  FAQ =
740 740  
741 741  == 5.1 ​ How to Upgrade Firmware ==
742 742  
743 -
744 744  User can upgrade the firmware for 1) bug fix, 2) new feature release.
745 745  
746 746  Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
747 747  
748 -(% style="color:red" %)**Notice, NSPH01 and LSPH01 share the same mother board. They use the same connection and method to update.**
678 +**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.**
749 749  
750 -
751 751  == 5.2  Can I calibrate NSPH01 to different soil types? ==
752 752  
753 -
754 754  NSPH01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
755 755  
756 -
757 757  = 6.  Trouble Shooting =
758 758  
759 759  == 6.1  ​Connection problem when uploading firmware ==
760 760  
761 -
762 762  **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
763 763  
764 -
765 765  == 6.2  AT Command input doesn't work ==
766 766  
692 +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 **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.
767 767  
768 -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.
769 -
770 -
771 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
772 -
773 -
774 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
775 -
776 -
777 777  = 7. ​ Order Info =
778 778  
779 -
780 780  Part Number**:** NSPH01
781 781  
782 -
783 783  = 8.  Packing Info =
784 784  
785 -
786 786  **Package Includes**:
787 787  
788 788  * NSPH01 NB-IoT pH Sensor x 1
... ... @@ -790,14 +790,11 @@
790 790  
791 791  **Dimension and weight**:
792 792  
793 -* Device Size: cm
794 -* Device Weight: g
795 -* Package Size / pcs : cm
796 -* Weight / pcs : g
707 +* Size: 195 x 125 x 55 mm
708 +* Weight:   420g
797 797  
798 798  = 9.  Support =
799 799  
800 -
801 801  * 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.
802 802  * 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]]
803 803  
image-20220923101327-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.1 KB
Content
image-20221009000933-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0