<
From version < 56.14 >
edited by Xiaoling
on 2023/05/23 17:08
To version < 51.4 >
edited by Xiaoling
on 2022/09/12 15:04
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,34 +9,20 @@
9 9  
10 10  = 1.  Introduction =
11 11  
12 +
12 12  == 1.1 ​ What is NSPH01 Soil pH Sensor ==
13 13  
14 14  
15 -(((
16 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 18  
19 -(((
20 20  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.
21 -)))
22 22  
23 -(((
24 24  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.
25 -)))
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.
26 26  
27 -(((
28 -NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
29 -)))
30 30  
31 -(((
32 -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)
33 -)))
34 -
35 -(((
36 -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.
37 -)))
38 -
39 -
40 40  [[image:image-20220907153151-1.png]]
41 41  
42 42  
... ... @@ -43,6 +43,7 @@
43 43  [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]]
44 44  
45 45  
32 +
46 46  == 1.2  Features ==
47 47  
48 48  
... ... @@ -71,12 +71,12 @@
71 71  
72 72  (% style="color:#037691" %)**NB-IoT Spec:**
73 73  
74 -* B1 @H-FDD: 2100MHz
75 -* B3 @H-FDD: 1800MHz
76 -* B8 @H-FDD: 900MHz
77 -* B5 @H-FDD: 850MHz
78 -* B20 @H-FDD: 800MHz
79 -* 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
80 80  
81 81  == 1.4  Probe Specification ==
82 82  
... ... @@ -98,19 +98,20 @@
98 98  * IP68 Protection
99 99  * Length: 3.5 meters
100 100  
101 -== 1.5  ​Applications ==
88 +== 1.5 ​Applications ==
102 102  
103 -
104 104  * Smart Agriculture
105 105  
106 -== 1.6  Pin mapping and power on ==
92 +== 1.6 Pin mapping and power on ==
107 107  
108 108  
109 109  [[image:image-20220907153300-2.png]]
110 110  
111 111  
98 +
112 112  = 2.  Use NSPH01 to communicate with IoT Server =
113 113  
101 +
114 114  == 2.1  How it works ==
115 115  
116 116  
... ... @@ -122,8 +122,10 @@
122 122  [[image:image-20220907153416-3.png]]
123 123  
124 124  
113 +
125 125  == 2.2 ​ Configure the NSPH01 ==
126 126  
116 +
127 127  === 2.2.1 Test Requirement ===
128 128  
129 129  
... ... @@ -133,21 +133,22 @@
133 133  * The local NB-IoT network used the band that NSPH01 supports.
134 134  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
135 135  
136 -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.
137 137  
138 138  
139 139  [[image:image-20220907153445-4.png]]
140 140  
141 141  
132 +
142 142  === 2.2.2 Insert SIM card ===
143 143  
144 144  
145 145  User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
146 146  
147 -
148 148  [[image:image-20220907153505-5.png]]
149 149  
150 150  
141 +
151 151  === 2.2.3 Connect USB – TTL to NSPH01 to configure it ===
152 152  
153 153  
... ... @@ -170,6 +170,7 @@
170 170  * Stop bits:  (% style="color:green" %)**1**
171 171  * Parity:  (% style="color:green" %)**None**
172 172  * Flow Control: (% style="color:green" %)**None**
164 +*
173 173  
174 174  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.
175 175  
... ... @@ -180,6 +180,7 @@
180 180  (% 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]]
181 181  
182 182  
175 +
183 183  === 2.2.4 Use CoAP protocol to uplink data ===
184 184  
185 185  
... ... @@ -204,6 +204,7 @@
204 204  [[image:image-20220907153612-8.png||height="529" width="729"]]
205 205  
206 206  
200 +
207 207  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
208 208  
209 209  
... ... @@ -213,6 +213,8 @@
213 213  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
214 214  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
215 215  
210 +
211 +
216 216  [[image:image-20220907153643-9.png||height="401" width="734"]]
217 217  
218 218  
... ... @@ -219,6 +219,7 @@
219 219  [[image:image-20220907153703-10.png||height="309" width="738"]]
220 220  
221 221  
218 +
222 222  === 2.2.6 Use MQTT protocol to uplink data ===
223 223  
224 224  
... ... @@ -232,6 +232,8 @@
232 232  * (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/ Set the sending topic of MQTT
233 233  * (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/ Set the subscription topic of MQTT
234 234  
232 +
233 +
235 235  [[image:image-20220907153739-11.png||height="491" width="764"]]
236 236  
237 237  
... ... @@ -241,6 +241,8 @@
241 241  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.
242 242  
243 243  
243 +
244 +
244 244  === 2.2.7 Use TCP protocol to uplink data ===
245 245  
246 246  
... ... @@ -249,6 +249,8 @@
249 249  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
250 250  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ to set TCP server address and port
251 251  
253 +
254 +
252 252  [[image:image-20220907153818-13.png||height="486" width="668"]]
253 253  
254 254  
... ... @@ -255,9 +255,10 @@
255 255  [[image:image-20220907153827-14.png||height="236" width="684"]]
256 256  
257 257  
258 -=== 2.2.8 Change Update Interval ===
259 259  
260 260  
263 +=== 2.2.8 Change Update Interval ===
264 +
261 261  Users can use the below command to change the **uplink interval**.
262 262  
263 263  * (% style="color:blue" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
... ... @@ -267,70 +267,43 @@
267 267  
268 268  == 2.3  Uplink Payload ==
269 269  
270 -
271 271  In this mode, uplink payload includes 87 bytes in total by default.
272 272  
273 273  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.
274 274  
275 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:520px" %)
276 -|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**4**
277 -|(% 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  .....
278 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
279 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Soil PH|Soil Temperature|Time stamp|Soil Temperature|Soil PH|Time stamp  .....
278 278  
279 279  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
280 280  
283 +(% style="text-align:center" %)
281 281  [[image:image-20220907153902-15.png||height="581" width="804"]]
282 282  
283 283  
284 -(((
285 285  The payload is ASCII string, representative same HEX:
286 -)))
287 287  
288 -(((
289 -
290 -)))
289 +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:
291 291  
292 -(((
293 -**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__//(%%)**
294 -)))
291 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
292 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0
293 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
294 +* (% style="color:red" %)Singal: 0x17 = 23
295 +* (% style="color:blue" %)Mod: 0x01 = 1
296 +* (% style="color:green" %)Interrupt: 0x00= 0
297 +* Soil PH: 0x0225= 549 = 5.49
298 +* Soil Temperature:0x010B =267=26.7 °C
299 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
300 +* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb
301 +* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
295 295  
296 -(((
297 -
298 -
299 -**where:**
300 -)))
301 -
302 -* (% style="color:#037691" %)**Device ID:**(%%)** **0xf868411056754138 = f868411056754138
303 -
304 -* (% style="color:#037691" %)**Version:**  (%%) 0x0064=100=1.0.0
305 -
306 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0c78 = 3192 mV = 3.192V
307 -
308 -* (% style="color:#037691" %)**Singal:** (%%)0x17 = 23
309 -
310 -* (% style="color:#037691" %)**Mod:** (%%) 0x01 = 1
311 -
312 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
313 -
314 -* (% style="color:#037691" %)**Soil PH:** (%%) 0x0225= 549 = 5.49
315 -
316 -* (% style="color:#037691" %)**Soil Temperature:**(%%) 0x010b =267=26.7 °C
317 -
318 -* (% style="color:#037691" %)**Time stamp :**   (%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
319 -
320 -* (% style="color:#037691" %)**Soil Temperature,Soil PH,Time stamp : **(%%) 010b0226631550fb
321 -
322 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%) Temperature,Soil PH,Time stamp :  010e022663154d77,.......
323 -
324 324  == 2.4  Payload Explanation and Sensor Interface ==
325 325  
326 326  === 2.4.1  Device ID ===
327 327  
328 -
329 329  By default, the Device ID equal to the last 15 bits of IMEI.
330 330  
331 331  User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
332 332  
333 -
334 334  **Example:**
335 335  
336 336  AT+DEUI=868411056754138
... ... @@ -337,18 +337,14 @@
337 337  
338 338  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
339 339  
340 -
341 341  === 2.4.2  Version Info ===
342 342  
343 -
344 344  Specify the software version: 0x64=100, means firmware version 1.00.
345 345  
346 346  For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0.
347 347  
348 -
349 349  === 2.4.3  Battery Info ===
350 350  
351 -
352 352  Check the battery voltage for NSPH01.
353 353  
354 354  Ex1: 0x0B45 = 2885mV
... ... @@ -355,10 +355,8 @@
355 355  
356 356  Ex2: 0x0B49 = 2889mV
357 357  
358 -
359 359  === 2.4.4  Signal Strength ===
360 360  
361 -
362 362  NB-IoT Network signal Strength.
363 363  
364 364  **Ex1: 0x1d = 29**
... ... @@ -373,23 +373,18 @@
373 373  
374 374  **99**    Not known or not detectable
375 375  
376 -
377 377  === 2.4.5  Soil PH ===
378 378  
379 -
380 380  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.
381 381  
382 -For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is
351 +For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is
383 383  
384 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**
353 +**0229(H) = 549(D) /100 = 5.49.**
385 385  
386 -
387 387  === 2.4.6  Soil Temperature ===
388 388  
357 +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
389 389  
390 -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
391 -
392 -
393 393  **Example**:
394 394  
395 395  If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
... ... @@ -396,42 +396,35 @@
396 396  
397 397  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
398 398  
399 -
400 400  === 2.4.7  Timestamp ===
401 401  
402 -
403 403  Time stamp : 0x6315537b =1662342011
404 404  
405 405  Convert Unix timestamp to time 2022-9-5 9:40:11.
406 406  
407 -
408 408  === 2.4.8  Digital Interrupt ===
409 409  
373 +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.
410 410  
411 -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.
412 -
413 413  The command is:
414 414  
415 -(% 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]])**.**
377 +**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]])**.**
416 416  
417 417  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.
418 418  
381 +Example:
419 419  
420 -**Example:**
421 -
422 422  0x(00): Normal uplink packet.
423 423  
424 424  0x(01): Interrupt Uplink Packet.
425 425  
426 -
427 427  === 2.4.9  ​+5V Output ===
428 428  
429 -
430 430  NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 
431 431  
432 432  The 5V output time can be controlled by AT Command.
433 433  
434 -(% style="color:blue" %)**AT+5VT=1000**
393 +**AT+5VT=1000**
435 435  
436 436  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
437 437  
... ... @@ -438,20 +438,21 @@
438 438  
439 439  == 2.5  Downlink Payload ==
440 440  
441 -
442 442  By default, NSPH01 prints the downlink payload to console port.
443 443  
444 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:479.818px" %)
445 -|=(% style="width: 183px; background-color:#D9E2F3;color:#0070C0" %)**Downlink Control Type**|=(% style="width: 55px; background-color:#D9E2F3;color:#0070C0" %)FPort|=(% style="width: 93px; background-color:#D9E2F3;color:#0070C0" %)**Type Code**|=(% style="width: 146px; background-color: rgb(217, 226, 243); color: rgb(0, 112, 192);" %)**Downlink payload size(bytes)**
446 -|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4
447 -|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2
448 -|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4
402 +(% style="text-align:center" %)
403 +[[image:image-20220907154636-17.png]]
449 449  
450 450  
451 -(% style="color:blue" %)**Examples:**
452 452  
453 -* (% style="color:#037691" %)** Set TDC**
454 454  
408 +
409 +
410 +
411 +**Examples:**
412 +
413 +* **Set TDC**
414 +
455 455  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
456 456  
457 457  Payload:    01 00 00 1E    TDC=30S
... ... @@ -458,18 +458,16 @@
458 458  
459 459  Payload:    01 00 00 3C    TDC=60S
460 460  
461 -* (% style="color:#037691" %)** Reset**
421 +* **Reset**
462 462  
463 463  If payload = 0x04FF, it will reset the NSPH01
464 464  
465 -* (% style="color:#037691" %)** INTMOD**
425 +* **INTMOD**
466 466  
467 467  Downlink Payload: 06000003, Set AT+INTMOD=3
468 468  
469 -
470 470  == 2.6  ​LED Indicator ==
471 471  
472 -
473 473  The NSPH01 has an internal LED which is to show the status of different state.
474 474  
475 475  * 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)
... ... @@ -477,20 +477,16 @@
477 477  * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds.
478 478  * For each uplink probe, LED will be on for 500ms.
479 479  
480 -== 2.7  Installation and Maintain ==
438 +== 2.7 Installation and Maintain ==
481 481  
482 -=== 2.7.1  Before measurement ===
440 +=== 2.7.1 Before measurement ===
483 483  
484 -
485 485  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. 
486 486  
444 +=== 2.7.2 Measurement ===
487 487  
488 -=== 2.7.2  Measurement ===
446 +**Measurement the soil surface:**
489 489  
490 -
491 -(% style="color:#037691" %)**Measurement the soil surface:**
492 -
493 -
494 494  [[image:image-20220907154700-18.png]] ​
495 495  
496 496  Choose the proper measuring position. Split the surface soil according to the measured deep.
... ... @@ -501,17 +501,14 @@
501 501  
502 502  Put soil over the probe after insert. And start to measure.
503 503  
458 +**Measurement inside soil:**
504 504  
505 -(% style="color:#037691" %)**Measurement inside soil:**
506 -
507 507  Dig a hole with diameter > 20CM.
508 508  
509 509  Insert the probe inside, method like measure the surface.
510 510  
464 +=== 2.7.3 Maintain Probe ===
511 511  
512 -=== 2.7.3  Maintain Probe ===
513 -
514 -
515 515  1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
516 516  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.
517 517  1. Probe reference electrode is also no strong, need to avoid strong force or hitting.
... ... @@ -519,13 +519,12 @@
519 519  1. Avoid the probes to touch oily matter. Which will cause issue in accuracy.
520 520  1. The probe is IP68 can be put in water.
521 521  
522 -== 2.8  PH and Temperature alarm function ==
473 +== 2.8 PH and Temperature alarm function ==
523 523  
475 +➢ AT Command:
524 524  
525 -(% style="color:#037691" %)**➢ AT Command:**
477 +AT+ PHALARM=min,max
526 526  
527 -(% style="color:blue" %)**AT+ PHALARM=min,max**
528 -
529 529  ² When min=3, and max≠0, Alarm higher than max
530 530  
531 531  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -532,11 +532,10 @@
532 532  
533 533  ² When min≠0 and max≠0, Alarm higher than max or lower than min
534 534  
485 +Example:
535 535  
536 -(% style="color:blue" %)**Example:**
487 +AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5.
537 537  
538 -AT+ PHALARM =5,8  ~/~/ Alarm when PH lower than 5.
539 -
540 540  AT+ TEMPALARM=min,max
541 541  
542 542  ² When min=0, and max≠0, Alarm higher than max
... ... @@ -545,71 +545,98 @@
545 545  
546 546  ² When min≠0 and max≠0, Alarm higher than max or lower than min
547 547  
497 +Example:
548 548  
549 -(% style="color:blue" %)**Example:**
499 +AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
550 550  
551 -AT+ TEMPALARM=20,30  ~/~/ Alarm when temperature lower than 20.
552 552  
502 +== 2.9 Set the number of data to be uploaded and the recording time ==
553 553  
554 -== 2.9  Set the number of data to be uploaded and the recording time ==
504 + AT Command:
555 555  
506 +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)
556 556  
557 -(% style="color:#037691" %)**➢ AT Command:**
508 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
558 558  
559 -* (% 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)
560 -* (% 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.
561 561  
562 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
511 +== 2.10 Read or Clear cached data ==
563 563  
564 -[[image:image-20221009000933-1.png||height="750" width="1043"]]
513 +➢ AT Command:
565 565  
515 +AT+CDP ~/~/ Read cached data
566 566  
567 -== 2.10  Read or Clear cached data ==
517 +[[image:image-20220907154700-19.png]]
568 568  
569 569  
570 -(% style="color:#037691" %)**➢ AT Command:**
520 +AT+CDP=0 ~/~/ Clear cached data
571 571  
572 -* (% style="color:blue" %)**AT+CDP**        (%%) ~/~/  Read cached data
573 -* (% style="color:blue" %)**AT+CDP=0**    (%%) ~/~/  Clear cached data
574 574  
575 -[[image:image-20220907154700-19.png]]
523 +== 2.11 Calibration ==
576 576  
525 +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).
577 577  
578 -== 2.11  Calibration ==
527 +After stable, user can use below command to calibrate.
579 579  
529 +[[image:image-20220907154700-20.png]] ​
580 580  
581 -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).
531 +== 2.12  ​Firmware Change Log ==
582 582  
583 -After stable, user can use below command to calibrate.
533 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
584 584  
535 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
585 585  
586 -[[image:image-20220907154700-20.png]]
537 +== 2.13 Battery Analysis ==
587 587  
539 +=== 2.13.1  ​Battery Type ===
588 588  
589 -== 2.1 ​Firmware Change Log ==
541 +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.
590 590  
543 +The battery is designed to last for several years depends on the actually use environment and update interval. 
591 591  
592 -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]]
545 +The battery-related documents as below:
593 593  
594 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
547 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
548 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
549 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
595 595  
551 +[[image:image-20220907154700-21.png]] ​
596 596  
597 -== 2.13 Battery & Power Consumption ==
553 +=== 2.13.2  Power consumption Analyze ===
598 598  
555 +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.
599 599  
600 -NSPH01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
557 +Instruction to use as below:
601 601  
602 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
559 +**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/]]
603 603  
561 +**Step 2: ** Open it and choose
604 604  
605 -= 3. ​ Access NB-IoT Module =
563 +* Product Model
564 +* Uplink Interval
565 +* Working Mode
606 606  
567 +And the Life expectation in difference case will be shown on the right.
607 607  
569 +(% style="text-align:center" %)
570 +[[image:image-20220907154700-22.jpeg]]
571 +
572 +​
573 +
574 +=== 2.13.3  ​Battery Note ===
575 +
576 +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.
577 +
578 +=== 2.13.4  Replace the battery ===
579 +
580 +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).
581 +
582 += 3. ​ Access NB-IoT Module =
583 +
608 608  Users can directly access the AT command set of the NB-IoT module.
609 609  
610 610  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/]] 
611 611  
612 -
588 +(% style="text-align:center" %)
613 613  [[image:image-20220907154700-23.png]]
614 614  
615 615  ​
... ... @@ -618,7 +618,6 @@
618 618  
619 619  == 4.1  Access AT Commands ==
620 620  
621 -
622 622  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]]
623 623  
624 624  AT+<CMD>?  : Help on <CMD>
... ... @@ -629,9 +629,8 @@
629 629  
630 630  AT+<CMD>=?  : Get the value
631 631  
607 +**General Commands**      
632 632  
633 -(% style="color:#037691" %)**General Commands**      
634 -
635 635  AT  : Attention       
636 636  
637 637  AT?  : Short Help     
... ... @@ -675,18 +675,16 @@
675 675  AT+ PHCAL  : calibrate PH value
676 676  
677 677  
678 -(% style="color:#037691" %)**COAP Management**      
652 +**COAP Management**      
679 679  
680 680  AT+URI            : Resource parameters
681 681  
656 +**UDP Management**
682 682  
683 -(% style="color:#037691" %)**UDP Management**
684 -
685 685  AT+CFM          : Upload confirmation mode (only valid for UDP)
686 686  
660 +**MQTT Management**
687 687  
688 -(% style="color:#037691" %)**MQTT Management**
689 -
690 690  AT+CLIENT               : Get or Set MQTT client
691 691  
692 692  AT+UNAME  : Get or Set MQTT Username
... ... @@ -697,61 +697,42 @@
697 697  
698 698  AT+SUBTOPIC  : Get or Set MQTT subscription topic
699 699  
672 +**Information**          
700 700  
701 -(% style="color:#037691" %)**Information**          
702 -
703 703  AT+FDR  : Factory Data Reset
704 704  
705 705  AT+PWORD  : Serial Access Password
706 706  
707 -
708 708  = ​5.  FAQ =
709 709  
710 710  == 5.1 ​ How to Upgrade Firmware ==
711 711  
712 -
713 713  User can upgrade the firmware for 1) bug fix, 2) new feature release.
714 714  
715 715  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]]
716 716  
717 -(% style="color:red" %)**Notice, NSPH01 and LSPH01 share the same mother board. They use the same connection and method to update.**
686 +**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.**
718 718  
719 -
720 720  == 5.2  Can I calibrate NSPH01 to different soil types? ==
721 721  
722 -
723 723  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]].
724 724  
725 -
726 726  = 6.  Trouble Shooting =
727 727  
728 728  == 6.1  ​Connection problem when uploading firmware ==
729 729  
730 -
731 731  **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]]
732 732  
733 -
734 734  == 6.2  AT Command input doesn't work ==
735 735  
700 +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.
736 736  
737 -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.
738 -
739 -
740 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
741 -
742 -
743 -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]]//**.
744 -
745 -
746 746  = 7. ​ Order Info =
747 747  
748 -
749 749  Part Number**:** NSPH01
750 750  
751 -
752 752  = 8.  Packing Info =
753 753  
754 -
755 755  **Package Includes**:
756 756  
757 757  * NSPH01 NB-IoT pH Sensor x 1
... ... @@ -759,14 +759,11 @@
759 759  
760 760  **Dimension and weight**:
761 761  
762 -* Device Size: cm
763 -* Device Weight: g
764 -* Package Size / pcs : cm
765 -* Weight / pcs : g
715 +* Size: 195 x 125 x 55 mm
716 +* Weight:   420g
766 766  
767 767  = 9.  Support =
768 768  
769 -
770 770  * 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.
771 771  * 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]]
772 772  
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