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 < 56.8 >
edited by Xiaoling
on 2022/10/25 16:46
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,11 +18,14 @@
18 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 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.
24 24  
22 +NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
25 25  
24 +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)
25 +
26 +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.
27 +
28 +
26 26  [[image:image-20220907153151-1.png]]
27 27  
28 28  
... ... @@ -48,6 +48,8 @@
48 48  * Micro SIM card slot
49 49  * 8500mAh Battery for long term use
50 50  
54 +
55 +
51 51  == 1.3  Specification ==
52 52  
53 53  
... ... @@ -65,6 +65,8 @@
65 65  * - B20 @H-FDD: 800MHz
66 66  * - B28 @H-FDD: 700MHz
67 67  
73 +
74 +
68 68  == 1.4  Probe Specification ==
69 69  
70 70  
... ... @@ -85,13 +85,18 @@
85 85  * IP68 Protection
86 86  * Length: 3.5 meters
87 87  
88 -== 1.5 ​Applications ==
89 89  
96 +
97 +== 1.5  ​Applications ==
98 +
99 +
90 90  * Smart Agriculture
91 91  
92 -== 1.6 Pin mapping and power on ==
93 93  
94 94  
104 +== 1.6  Pin mapping and power on ==
105 +
106 +
95 95  [[image:image-20220907153300-2.png]]
96 96  
97 97  
... ... @@ -123,7 +123,7 @@
123 123  * The local NB-IoT network used the band that NSPH01 supports.
124 124  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
125 125  
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.
138 +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 128  
129 129  [[image:image-20220907153445-4.png]]
... ... @@ -135,6 +135,7 @@
135 135  
136 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 137  
150 +
138 138  [[image:image-20220907153505-5.png]]
139 139  
140 140  
... ... @@ -161,7 +161,6 @@
161 161  * Stop bits:  (% style="color:green" %)**1**
162 162  * Parity:  (% style="color:green" %)**None**
163 163  * Flow Control: (% style="color:green" %)**None**
164 -*
165 165  
166 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.
167 167  
... ... @@ -202,11 +202,11 @@
202 202  
203 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  
218 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
220 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
221 +
210 210  [[image:image-20220907153643-9.png||height="401" width="734"]]
211 211  
212 212  
... ... @@ -213,37 +213,38 @@
213 213  [[image:image-20220907153703-10.png||height="309" width="738"]]
214 214  
215 215  
228 +
216 216  === 2.2.6 Use MQTT protocol to uplink data ===
217 217  
231 +
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
234 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/ Set to use MQTT protocol to uplink
235 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/ Set MQTT server address and port
236 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/ Set up the CLIENT of MQTT
237 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/ Set the username of MQTT
238 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/ Set the password of MQTT
239 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/ Set the sending topic of MQTT
240 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/ Set the subscription topic of MQTT
227 227  
228 -
229 229  [[image:image-20220907153739-11.png||height="491" width="764"]]
230 230  
231 231  
232 232  [[image:image-20220907153751-12.png||height="555" width="769"]]
233 233  
247 +
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 236  
237 237  
238 -
239 239  === 2.2.7 Use TCP protocol to uplink data ===
240 240  
254 +
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
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
245 245  
246 -
247 247  [[image:image-20220907153818-13.png||height="486" width="668"]]
248 248  
249 249  
... ... @@ -251,55 +251,86 @@
251 251  
252 252  
253 253  
254 -
255 255  === 2.2.8 Change Update Interval ===
256 256  
269 +
257 257  Users can use the below command to change the **uplink interval**.
258 258  
259 -* **(% style="color:blue" %)AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
272 +* (% style="color:blue" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
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).**
274 +(% 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).**
262 262  
263 263  
277 +
264 264  == 2.3  Uplink Payload ==
265 265  
280 +
266 266  In this mode, uplink payload includes 87 bytes in total by default.
267 267  
268 268  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.
269 269  
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  .....
285 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
286 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:20px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:50px" %)**2**|(% style="width:35px" %)**2**|(% style="width:40px" %)**4**
287 +|=(% 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  .....
272 272  
273 273  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
274 274  
275 -(% style="text-align:center" %)
276 276  [[image:image-20220907153902-15.png||height="581" width="804"]]
277 277  
278 278  
294 +(((
279 279  The payload is ASCII string, representative same HEX:
296 +)))
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:
298 +(((
299 +
300 +)))
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
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,.......
302 +(((
303 +**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__//(%%)**
304 +)))
294 294  
306 +(((
307 +
308 +
309 +**where:**
310 +)))
311 +
312 +* (% style="color:#037691" %)**Device ID:**(%%)** **0xf868411056754138 = f868411056754138
313 +
314 +* (% style="color:#037691" %)**Version:**  (%%) 0x0064=100=1.0.0
315 +
316 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0c78 = 3192 mV = 3.192V
317 +
318 +* (% style="color:#037691" %)**Singal:** (%%)0x17 = 23
319 +
320 +* (% style="color:#037691" %)**Mod:** (%%) 0x01 = 1
321 +
322 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
323 +
324 +* (% style="color:#037691" %)**Soil PH:** (%%) 0x0225= 549 = 5.49
325 +
326 +* (% style="color:#037691" %)**Soil Temperature:**(%%) 0x010b =267=26.7 °C
327 +
328 +* (% style="color:#037691" %)**Time stamp :**   (%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
329 +
330 +* (% style="color:#037691" %)**Soil Temperature,Soil PH,Time stamp : **(%%) 010b0226631550fb
331 +
332 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%) Temperature,Soil PH,Time stamp :  010e022663154d77,.......
333 +
334 +
335 +
295 295  == 2.4  Payload Explanation and Sensor Interface ==
296 296  
338 +
297 297  === 2.4.1  Device ID ===
298 298  
341 +
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
344 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
302 302  
346 +
303 303  **Example:**
304 304  
305 305  AT+DEUI=868411056754138
... ... @@ -306,14 +306,20 @@
306 306  
307 307  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
308 308  
353 +
354 +
309 309  === 2.4.2  Version Info ===
310 310  
357 +
311 311  Specify the software version: 0x64=100, means firmware version 1.00.
312 312  
313 313  For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0.
314 314  
362 +
363 +
315 315  === 2.4.3  Battery Info ===
316 316  
366 +
317 317  Check the battery voltage for NSPH01.
318 318  
319 319  Ex1: 0x0B45 = 2885mV
... ... @@ -320,8 +320,11 @@
320 320  
321 321  Ex2: 0x0B49 = 2889mV
322 322  
373 +
374 +
323 323  === 2.4.4  Signal Strength ===
324 324  
377 +
325 325  NB-IoT Network signal Strength.
326 326  
327 327  **Ex1: 0x1d = 29**
... ... @@ -336,18 +336,25 @@
336 336  
337 337  **99**    Not known or not detectable
338 338  
392 +
393 +
339 339  === 2.4.5  Soil PH ===
340 340  
396 +
341 341  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.
342 342  
343 -For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is
399 +For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is
344 344  
345 -**0229(H) = 549(D) /100 = 5.49.**
401 +(% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**
346 346  
403 +
404 +
347 347  === 2.4.6  Soil Temperature ===
348 348  
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
350 350  
408 +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
409 +
410 +
351 351  **Example**:
352 352  
353 353  If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
... ... @@ -354,56 +354,62 @@
354 354  
355 355  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
356 356  
417 +
418 +
357 357  === 2.4.7  Timestamp ===
358 358  
421 +
359 359  Time stamp : 0x6315537b =1662342011
360 360  
361 361  Convert Unix timestamp to time 2022-9-5 9:40:11.
362 362  
426 +
427 +
363 363  === 2.4.8  Digital Interrupt ===
364 364  
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.
366 366  
431 +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.
432 +
367 367  The command is:
368 368  
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]])**.**
435 +(% 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]])**.**
370 370  
371 371  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.
372 372  
373 -Example:
374 374  
440 +**Example:**
441 +
375 375  0x(00): Normal uplink packet.
376 376  
377 377  0x(01): Interrupt Uplink Packet.
378 378  
446 +
447 +
379 379  === 2.4.9  ​+5V Output ===
380 380  
450 +
381 381  NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 
382 382  
383 383  The 5V output time can be controlled by AT Command.
384 384  
385 -**AT+5VT=1000**
455 +(% style="color:blue" %)**AT+5VT=1000**
386 386  
387 387  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
388 388  
389 389  
460 +
390 390  == 2.5  Downlink Payload ==
391 391  
463 +
392 392  By default, NSPH01 prints the downlink payload to console port.
393 393  
394 -(% style="text-align:center" %)
395 395  [[image:image-20220907154636-17.png]]
396 396  
397 397  
469 +(% style="color:blue" %)**Examples:**
398 398  
471 +* (% style="color:#037691" %)** Set TDC**
399 399  
400 -
401 -
402 -
403 -**Examples:**
404 -
405 -* **Set TDC**
406 -
407 407  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
408 408  
409 409  Payload:    01 00 00 1E    TDC=30S
... ... @@ -410,16 +410,19 @@
410 410  
411 411  Payload:    01 00 00 3C    TDC=60S
412 412  
413 -* **Reset**
479 +* (% style="color:#037691" %)** Reset**
414 414  
415 415  If payload = 0x04FF, it will reset the NSPH01
416 416  
417 -* **INTMOD**
483 +* (% style="color:#037691" %)** INTMOD**
418 418  
419 419  Downlink Payload: 06000003, Set AT+INTMOD=3
420 420  
487 +
488 +
421 421  == 2.6  ​LED Indicator ==
422 422  
491 +
423 423  The NSPH01 has an internal LED which is to show the status of different state.
424 424  
425 425  * 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)
... ... @@ -427,16 +427,24 @@
427 427  * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds.
428 428  * For each uplink probe, LED will be on for 500ms.
429 429  
430 -== 2.7 Installation and Maintain ==
431 431  
432 -=== 2.7.1 Before measurement ===
433 433  
501 +== 2.7  Installation and Maintain ==
502 +
503 +
504 +=== 2.7.1  Before measurement ===
505 +
506 +
434 434  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. 
435 435  
436 -=== 2.7.2 Measurement ===
437 437  
438 -**Measurement the soil surface:**
439 439  
511 +=== 2.7.2  Measurement ===
512 +
513 +
514 +(% style="color:#037691" %)**Measurement the soil surface:**
515 +
516 +
440 440  [[image:image-20220907154700-18.png]] ​
441 441  
442 442  Choose the proper measuring position. Split the surface soil according to the measured deep.
... ... @@ -447,14 +447,18 @@
447 447  
448 448  Put soil over the probe after insert. And start to measure.
449 449  
450 -**Measurement inside soil:**
451 451  
528 +(% style="color:#037691" %)**Measurement inside soil:**
529 +
452 452  Dig a hole with diameter > 20CM.
453 453  
454 454  Insert the probe inside, method like measure the surface.
455 455  
456 -=== 2.7.3 Maintain Probe ===
457 457  
535 +
536 +=== 2.7.3  Maintain Probe ===
537 +
538 +
458 458  1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
459 459  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.
460 460  1. Probe reference electrode is also no strong, need to avoid strong force or hitting.
... ... @@ -462,12 +462,15 @@
462 462  1. Avoid the probes to touch oily matter. Which will cause issue in accuracy.
463 463  1. The probe is IP68 can be put in water.
464 464  
465 -== 2.8 PH and Temperature alarm function ==
466 466  
467 -➢ AT Command:
468 468  
469 -AT+ PHALARM=min,max
548 +== 2.8  PH and Temperature alarm function ==
470 470  
550 +
551 +(% style="color:#037691" %)**➢ AT Command:**
552 +
553 +(% style="color:blue" %)**AT+ PHALARM=min,max**
554 +
471 471  ² When min=3, and max≠0, Alarm higher than max
472 472  
473 473  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -474,10 +474,11 @@
474 474  
475 475  ² When min≠0 and max≠0, Alarm higher than max or lower than min
476 476  
477 -Example:
478 478  
479 -AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5.
562 +(% style="color:blue" %)**Example:**
480 480  
564 +AT+ PHALARM =5,8  ~/~/ Alarm when PH lower than 5.
565 +
481 481  AT+ TEMPALARM=min,max
482 482  
483 483  ² When min=0, and max≠0, Alarm higher than max
... ... @@ -486,50 +486,66 @@
486 486  
487 487  ² When min≠0 and max≠0, Alarm higher than max or lower than min
488 488  
489 -Example:
490 490  
491 -AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
575 +(% style="color:blue" %)**Example:**
492 492  
577 +AT+ TEMPALARM=20,30  ~/~/ Alarm when temperature lower than 20.
493 493  
494 -== 2.9 Set the number of data to be uploaded and the recording time ==
495 495  
496 -➢ AT Command:
497 497  
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)
581 +== 2.9  Set the number of data to be uploaded and the recording time ==
499 499  
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  
584 +(% style="color:#037691" %)**➢ AT Command:**
502 502  
503 -== 2.10 Read or Clear cached data ==
586 +* (% 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)
587 +* (% 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.
504 504  
505 -➢ AT Command:
589 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
506 506  
507 -AT+CDP ~/~/ Read cached data
591 +[[image:image-20221009000933-1.png||height="750" width="1043"]]
508 508  
593 +
594 +
595 +== 2.10  Read or Clear cached data ==
596 +
597 +
598 +(% style="color:#037691" %)**➢ AT Command:**
599 +
600 +* (% style="color:blue" %)**AT+CDP**        (%%) ~/~/  Read cached data
601 +* (% style="color:blue" %)**AT+CDP=0**    (%%) ~/~/  Clear cached data
602 +
509 509  [[image:image-20220907154700-19.png]]
510 510  
511 511  
512 -AT+CDP=0 ~/~/ Clear cached data
513 513  
607 +== 2.11  Calibration ==
514 514  
515 -== 2.11 Calibration ==
516 516  
517 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).
518 518  
519 519  After stable, user can use below command to calibrate.
520 520  
614 +
521 521  [[image:image-20220907154700-20.png]] ​
522 522  
617 +
618 +
523 523  == 2.12  ​Firmware Change Log ==
524 524  
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]]
526 526  
527 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
622 +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]]
528 528  
624 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
625 +
626 +
627 +
529 529  == 2.13  ​Battery Analysis ==
530 530  
630 +
531 531  === 2.13.1  ​Battery Type ===
532 532  
633 +
533 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.
534 534  
535 535  The battery is designed to last for several years depends on the actually use environment and update interval. 
... ... @@ -542,15 +542,18 @@
542 542  
543 543  [[image:image-20220907154700-21.png]] ​
544 544  
646 +
647 +
545 545  === 2.13.2  Power consumption Analyze ===
546 546  
650 +
547 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.
548 548  
549 549  Instruction to use as below:
550 550  
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/]]
655 +(% style="color:blue" %)**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/]]
552 552  
553 -**Step 2: ** Open it and choose
657 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
554 554  
555 555  * Product Model
556 556  * Uplink Interval
... ... @@ -558,34 +558,45 @@
558 558  
559 559  And the Life expectation in difference case will be shown on the right.
560 560  
561 -(% style="text-align:center" %)
665 +
562 562  [[image:image-20220907154700-22.jpeg]]
563 563  
564 564  ​
565 565  
670 +
566 566  === 2.13.3  ​Battery Note ===
567 567  
673 +
568 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 569  
676 +
677 +
570 570  === 2.13.4  Replace the battery ===
571 571  
680 +
572 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 573  
683 +
684 +
574 574  = 3. ​ Access NB-IoT Module =
575 575  
687 +
576 576  Users can directly access the AT command set of the NB-IoT module.
577 577  
578 578  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/]] 
579 579  
580 -(% style="text-align:center" %)
692 +
581 581  [[image:image-20220907154700-23.png]]
582 582  
583 583  ​
584 584  
697 +
585 585  = 4.  Using the AT Commands =
586 586  
700 +
587 587  == 4.1  Access AT Commands ==
588 588  
703 +
589 589  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]]
590 590  
591 591  AT+<CMD>?  : Help on <CMD>
... ... @@ -596,8 +596,9 @@
596 596  
597 597  AT+<CMD>=?  : Get the value
598 598  
599 -**General Commands**      
600 600  
715 +(% style="color:#037691" %)**General Commands**      
716 +
601 601  AT  : Attention       
602 602  
603 603  AT?  : Short Help     
... ... @@ -641,16 +641,18 @@
641 641  AT+ PHCAL  : calibrate PH value
642 642  
643 643  
644 -**COAP Management**      
760 +(% style="color:#037691" %)**COAP Management**      
645 645  
646 646  AT+URI            : Resource parameters
647 647  
648 -**UDP Management**
649 649  
765 +(% style="color:#037691" %)**UDP Management**
766 +
650 650  AT+CFM          : Upload confirmation mode (only valid for UDP)
651 651  
652 -**MQTT Management**
653 653  
770 +(% style="color:#037691" %)**MQTT Management**
771 +
654 654  AT+CLIENT               : Get or Set MQTT client
655 655  
656 656  AT+UNAME  : Get or Set MQTT Username
... ... @@ -661,42 +661,63 @@
661 661  
662 662  AT+SUBTOPIC  : Get or Set MQTT subscription topic
663 663  
664 -**Information**          
665 665  
783 +(% style="color:#037691" %)**Information**          
784 +
666 666  AT+FDR  : Factory Data Reset
667 667  
668 668  AT+PWORD  : Serial Access Password
669 669  
789 +
790 +
670 670  = ​5.  FAQ =
671 671  
793 +
672 672  == 5.1 ​ How to Upgrade Firmware ==
673 673  
796 +
674 674  User can upgrade the firmware for 1) bug fix, 2) new feature release.
675 675  
676 676  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]]
677 677  
678 -**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.**
801 +(% style="color:red" %)**Notice, NSPH01 and LSPH01 share the same mother board. They use the same connection and method to update.**
679 679  
803 +
804 +
680 680  == 5.2  Can I calibrate NSPH01 to different soil types? ==
681 681  
807 +
682 682  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]].
683 683  
810 +
811 +
684 684  = 6.  Trouble Shooting =
685 685  
814 +
686 686  == 6.1  ​Connection problem when uploading firmware ==
687 687  
817 +
688 688  **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]]
689 689  
820 +
821 +
690 690  == 6.2  AT Command input doesn't work ==
691 691  
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.
693 693  
825 +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.
826 +
827 +
828 +
694 694  = 7. ​ Order Info =
695 695  
831 +
696 696  Part Number**:** NSPH01
697 697  
834 +
835 +
698 698  = 8.  Packing Info =
699 699  
838 +
700 700  **Package Includes**:
701 701  
702 702  * NSPH01 NB-IoT pH Sensor x 1
... ... @@ -704,11 +704,16 @@
704 704  
705 705  **Dimension and weight**:
706 706  
707 -* Size: 195 x 125 x 55 mm
708 -* Weight:   420g
846 +* Device Size: cm
847 +* Device Weight: g
848 +* Package Size / pcs : cm
849 +* Weight / pcs : g
709 709  
851 +
852 +
710 710  = 9.  Support =
711 711  
855 +
712 712  * 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.
713 713  * 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]]
714 714  
image-20220923101327-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +12.1 KB
Content
image-20221009000933-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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