Last modified by Bei Jinggeng on 2024/03/30 17:53
<
From version < 53.1 >
edited by David Huang
on 2022/10/08 11:47
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -48,7 +48,6 @@
48 48  * Micro SIM card slot
49 49  * 8500mAh Battery for long term use
50 50  
51 -
52 52  == 1.3  Specification ==
53 53  
54 54  
... ... @@ -66,7 +66,6 @@
66 66  * - B20 @H-FDD: 800MHz
67 67  * - B28 @H-FDD: 700MHz
68 68  
69 -
70 70  == 1.4  Probe Specification ==
71 71  
72 72  
... ... @@ -87,16 +87,13 @@
87 87  * IP68 Protection
88 88  * Length: 3.5 meters
89 89  
88 +== 1.5 ​Applications ==
90 90  
91 -== 1.5  ​Applications ==
92 -
93 -
94 94  * Smart Agriculture
95 95  
92 +== 1.6 Pin mapping and power on ==
96 96  
97 -== 1.6  Pin mapping and power on ==
98 98  
99 -
100 100  [[image:image-20220907153300-2.png]]
101 101  
102 102  
... ... @@ -128,10 +128,9 @@
128 128  * The local NB-IoT network used the band that NSPH01 supports.
129 129  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
130 130  
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.
131 131  
132 -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.
133 133  
134 -
135 135  [[image:image-20220907153445-4.png]]
136 136  
137 137  
... ... @@ -141,7 +141,6 @@
141 141  
142 142  User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
143 143  
144 -
145 145  [[image:image-20220907153505-5.png]]
146 146  
147 147  
... ... @@ -168,8 +168,8 @@
168 168  * Stop bits:  (% style="color:green" %)**1**
169 169  * Parity:  (% style="color:green" %)**None**
170 170  * Flow Control: (% style="color:green" %)**None**
164 +*
171 171  
172 -
173 173  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.
174 174  
175 175  
... ... @@ -209,12 +209,11 @@
209 209  
210 210  
211 211  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
212 212  
213 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
214 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
215 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
216 -
217 -
218 218  [[image:image-20220907153643-9.png||height="401" width="734"]]
219 219  
220 220  
... ... @@ -221,19 +221,17 @@
221 221  [[image:image-20220907153703-10.png||height="309" width="738"]]
222 222  
223 223  
224 -
225 225  === 2.2.6 Use MQTT protocol to uplink data ===
226 226  
227 -
228 228  This feature is supported since firmware version v110
229 229  
230 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/ Set to use MQTT protocol to uplink
231 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/ Set MQTT server address and port
232 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/ Set up the CLIENT of MQTT
233 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/ Set the username of MQTT
234 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/ Set the password of MQTT
235 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/ Set the sending topic of MQTT
236 -* (% 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
237 237  
238 238  
239 239  [[image:image-20220907153739-11.png||height="491" width="764"]]
... ... @@ -241,7 +241,6 @@
241 241  
242 242  [[image:image-20220907153751-12.png||height="555" width="769"]]
243 243  
244 -
245 245  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.
246 246  
247 247  
... ... @@ -249,11 +249,10 @@
249 249  
250 250  === 2.2.7 Use TCP protocol to uplink data ===
251 251  
252 -
253 253  This feature is supported since firmware version v110
254 254  
255 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
256 -* (% 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
257 257  
258 258  
259 259  [[image:image-20220907153818-13.png||height="486" width="668"]]
... ... @@ -263,76 +263,55 @@
263 263  
264 264  
265 265  
254 +
266 266  === 2.2.8 Change Update Interval ===
267 267  
268 -
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 -
277 277  == 2.3  Uplink Payload ==
278 278  
279 -
280 280  In this mode, uplink payload includes 87 bytes in total by default.
281 281  
282 282  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.
283 283  
284 -(% border="2" style="background-color:#ffffcc; color:green; width:1160px" %)
285 -|(% style="width:96px" %)**Size(bytes)**|(% style="width:83px" %)**8**|(% style="width:44px" %)**2**|(% style="width:42px" %)**2**|(% style="width:124px" %)1|(% style="width:57px" %)1|(% style="width:80px" %)1|(% style="width:69px" %)2|(% style="width:134px" %)2|(% style="width:98px" %)4|(% style="width:134px" %)2|(% style="width:68px" %)2|(% style="width:125px" %)4
286 -|(% 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  .....
287 287  
288 288  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
289 289  
275 +(% style="text-align:center" %)
290 290  [[image:image-20220907153902-15.png||height="581" width="804"]]
291 291  
292 292  
293 -(((
294 294  The payload is ASCII string, representative same HEX:
295 -)))
296 296  
297 -(((
298 -
299 -)))
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:
300 300  
301 -(((
302 -**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__//(%%)**
303 -)))
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,.......
304 304  
305 -(((
306 -
307 -
308 -where:
309 -)))
310 -
311 -* Device ID: 0xf868411056754138 = f868411056754138
312 -* Version:  0x0064=100=1.0.0
313 -* BAT:  0x0c78 = 3192 mV = 3.192V
314 -* Singal: 0x17 = 23
315 -* Mod:  0x01 = 1
316 -* Interrupt: 0x00= 0
317 -* Soil PH:  0x0225= 549 = 5.49
318 -* Soil Temperature: 0x010b =267=26.7 °C
319 -* Time stamp :  0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
320 -* Soil Temperature,Soil PH,Time stamp :  010b0226631550fb
321 -* 8 sets of recorded data: Temperature,Soil PH,Time stamp :  010e022663154d77,.......
322 -
323 -
324 -
325 325  == 2.4  Payload Explanation and Sensor Interface ==
326 326  
327 -
328 328  === 2.4.1  Device ID ===
329 329  
330 -
331 331  By default, the Device ID equal to the last 15 bits of IMEI.
332 332  
333 -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
334 334  
335 -
336 336  **Example:**
337 337  
338 338  AT+DEUI=868411056754138
... ... @@ -339,20 +339,14 @@
339 339  
340 340  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
341 341  
342 -
343 -
344 344  === 2.4.2  Version Info ===
345 345  
346 -
347 347  Specify the software version: 0x64=100, means firmware version 1.00.
348 348  
349 349  For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0.
350 350  
351 -
352 -
353 353  === 2.4.3  Battery Info ===
354 354  
355 -
356 356  Check the battery voltage for NSPH01.
357 357  
358 358  Ex1: 0x0B45 = 2885mV
... ... @@ -359,11 +359,8 @@
359 359  
360 360  Ex2: 0x0B49 = 2889mV
361 361  
362 -
363 -
364 364  === 2.4.4  Signal Strength ===
365 365  
366 -
367 367  NB-IoT Network signal Strength.
368 368  
369 369  **Ex1: 0x1d = 29**
... ... @@ -378,25 +378,18 @@
378 378  
379 379  **99**    Not known or not detectable
380 380  
381 -
382 -
383 383  === 2.4.5  Soil PH ===
384 384  
385 -
386 386  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.
387 387  
388 -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
389 389  
390 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**
345 +**0229(H) = 549(D) /100 = 5.49.**
391 391  
392 -
393 -
394 394  === 2.4.6  Soil Temperature ===
395 395  
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
396 396  
397 -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
398 -
399 -
400 400  **Example**:
401 401  
402 402  If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
... ... @@ -403,62 +403,56 @@
403 403  
404 404  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
405 405  
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 -
417 417  === 2.4.8  Digital Interrupt ===
418 418  
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.
419 419  
420 -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.
421 -
422 422  The command is:
423 423  
424 -(% 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]])**.**
425 425  
426 426  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.
427 427  
373 +Example:
428 428  
429 -**Example:**
430 -
431 431  0x(00): Normal uplink packet.
432 432  
433 433  0x(01): Interrupt Uplink Packet.
434 434  
435 -
436 -
437 437  === 2.4.9  ​+5V Output ===
438 438  
439 -
440 440  NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 
441 441  
442 442  The 5V output time can be controlled by AT Command.
443 443  
444 -(% style="color:blue" %)**AT+5VT=1000**
385 +**AT+5VT=1000**
445 445  
446 446  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
447 447  
448 448  
449 -
450 450  == 2.5  Downlink Payload ==
451 451  
452 -
453 453  By default, NSPH01 prints the downlink payload to console port.
454 454  
394 +(% style="text-align:center" %)
455 455  [[image:image-20220907154636-17.png]]
456 456  
457 457  
458 -(% style="color:blue" %)**Examples:**
459 459  
460 -* (% style="color:#037691" %)** Set TDC**
461 461  
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,19 +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 -
478 478  == 2.6  ​LED Indicator ==
479 479  
480 -
481 481  The NSPH01 has an internal LED which is to show the status of different state.
482 482  
483 483  * 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)
... ... @@ -485,24 +485,16 @@
485 485  * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds.
486 486  * For each uplink probe, LED will be on for 500ms.
487 487  
430 +== 2.7 Installation and Maintain ==
488 488  
432 +=== 2.7.1 Before measurement ===
489 489  
490 -== 2.7  Installation and Maintain ==
491 -
492 -
493 -=== 2.7.1  Before measurement ===
494 -
495 -
496 496  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. 
497 497  
436 +=== 2.7.2 Measurement ===
498 498  
438 +**Measurement the soil surface:**
499 499  
500 -=== 2.7.2  Measurement ===
501 -
502 -
503 -(% style="color:#037691" %)**Measurement the soil surface:**
504 -
505 -
506 506  [[image:image-20220907154700-18.png]] ​
507 507  
508 508  Choose the proper measuring position. Split the surface soil according to the measured deep.
... ... @@ -513,18 +513,14 @@
513 513  
514 514  Put soil over the probe after insert. And start to measure.
515 515  
450 +**Measurement inside soil:**
516 516  
517 -(% style="color:#037691" %)**Measurement inside soil:**
518 -
519 519  Dig a hole with diameter > 20CM.
520 520  
521 521  Insert the probe inside, method like measure the surface.
522 522  
456 +=== 2.7.3 Maintain Probe ===
523 523  
524 -
525 -=== 2.7.3  Maintain Probe ===
526 -
527 -
528 528  1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
529 529  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.
530 530  1. Probe reference electrode is also no strong, need to avoid strong force or hitting.
... ... @@ -532,15 +532,12 @@
532 532  1. Avoid the probes to touch oily matter. Which will cause issue in accuracy.
533 533  1. The probe is IP68 can be put in water.
534 534  
465 +== 2.8 PH and Temperature alarm function ==
535 535  
467 +➢ AT Command:
536 536  
537 -== 2.8  PH and Temperature alarm function ==
469 +AT+ PHALARM=min,max
538 538  
539 -
540 -(% style="color:#037691" %)**➢ AT Command:**
541 -
542 -(% style="color:blue" %)**AT+ PHALARM=min,max**
543 -
544 544  ² When min=3, and max≠0, Alarm higher than max
545 545  
546 546  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -547,11 +547,10 @@
547 547  
548 548  ² When min≠0 and max≠0, Alarm higher than max or lower than min
549 549  
477 +Example:
550 550  
551 -(% style="color:blue" %)**Example:**
479 +AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5.
552 552  
553 -AT+ PHALARM =5,8  ~/~/ Alarm when PH lower than 5.
554 -
555 555  AT+ TEMPALARM=min,max
556 556  
557 557  ² When min=0, and max≠0, Alarm higher than max
... ... @@ -560,64 +560,50 @@
560 560  
561 561  ² When min≠0 and max≠0, Alarm higher than max or lower than min
562 562  
489 +Example:
563 563  
564 -(% style="color:blue" %)**Example:**
491 +AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
565 565  
566 -AT+ TEMPALARM=20,30  ~/~/ Alarm when temperature lower than 20.
567 567  
494 +== 2.9 Set the number of data to be uploaded and the recording time ==
568 568  
496 +➢ AT Command:
569 569  
570 -== 2.9  Set the number of data to be uploaded and the recording time ==
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)
571 571  
500 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
572 572  
573 -(% style="color:#037691" %)**➢ AT Command:**
574 574  
575 -* (% 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)
576 -* (% 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.
503 +== 2.10 Read or Clear cached data ==
577 577  
505 +➢ AT Command:
578 578  
579 -This link explains the relationship between TR, NOUD and TDC more clearly** : **[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]]
507 +AT+CDP ~/~/ Read cached data
580 580  
581 -== 2.10  Read or Clear cached data ==
582 -
583 -
584 -(% style="color:#037691" %)**➢ AT Command:**
585 -
586 -* (% style="color:blue" %)**AT+CDP**        (%%) ~/~/  Read cached data
587 -* (% style="color:blue" %)**AT+CDP=0**    (%%) ~/~/  Clear cached data
588 -
589 -
590 590  [[image:image-20220907154700-19.png]]
591 591  
592 592  
512 +AT+CDP=0 ~/~/ Clear cached data
593 593  
594 -== 2.11  Calibration ==
595 595  
515 +== 2.11 Calibration ==
596 596  
597 597  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).
598 598  
599 599  After stable, user can use below command to calibrate.
600 600  
601 -
602 602  [[image:image-20220907154700-20.png]] ​
603 603  
604 -
605 -
606 606  == 2.12  ​Firmware Change Log ==
607 607  
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]]
608 608  
609 -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]]
527 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
610 610  
611 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
612 -
613 -
614 -
615 615  == 2.13  ​Battery Analysis ==
616 616  
617 -
618 618  === 2.13.1  ​Battery Type ===
619 619  
620 -
621 621  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.
622 622  
623 623  The battery is designed to last for several years depends on the actually use environment and update interval. 
... ... @@ -630,18 +630,15 @@
630 630  
631 631  [[image:image-20220907154700-21.png]] ​
632 632  
633 -
634 -
635 635  === 2.13.2  Power consumption Analyze ===
636 636  
637 -
638 638  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.
639 639  
640 640  Instruction to use as below:
641 641  
642 -(% 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/]]
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/]]
643 643  
644 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
553 +**Step 2: ** Open it and choose
645 645  
646 646  * Product Model
647 647  * Uplink Interval
... ... @@ -649,45 +649,34 @@
649 649  
650 650  And the Life expectation in difference case will be shown on the right.
651 651  
652 -
561 +(% style="text-align:center" %)
653 653  [[image:image-20220907154700-22.jpeg]]
654 654  
655 655  ​
656 656  
657 -
658 658  === 2.13.3  ​Battery Note ===
659 659  
660 -
661 661  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.
662 662  
663 -
664 -
665 665  === 2.13.4  Replace the battery ===
666 666  
667 -
668 668  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).
669 669  
670 -
671 -
672 672  = 3. ​ Access NB-IoT Module =
673 673  
674 -
675 675  Users can directly access the AT command set of the NB-IoT module.
676 676  
677 677  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/]] 
678 678  
679 -
580 +(% style="text-align:center" %)
680 680  [[image:image-20220907154700-23.png]]
681 681  
682 682  ​
683 683  
684 -
685 685  = 4.  Using the AT Commands =
686 686  
687 -
688 688  == 4.1  Access AT Commands ==
689 689  
690 -
691 691  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]]
692 692  
693 693  AT+<CMD>?  : Help on <CMD>
... ... @@ -698,9 +698,8 @@
698 698  
699 699  AT+<CMD>=?  : Get the value
700 700  
599 +**General Commands**      
701 701  
702 -(% style="color:#037691" %)**General Commands**      
703 -
704 704  AT  : Attention       
705 705  
706 706  AT?  : Short Help     
... ... @@ -744,18 +744,16 @@
744 744  AT+ PHCAL  : calibrate PH value
745 745  
746 746  
747 -(% style="color:#037691" %)**COAP Management**      
644 +**COAP Management**      
748 748  
749 749  AT+URI            : Resource parameters
750 750  
648 +**UDP Management**
751 751  
752 -(% style="color:#037691" %)**UDP Management**
753 -
754 754  AT+CFM          : Upload confirmation mode (only valid for UDP)
755 755  
652 +**MQTT Management**
756 756  
757 -(% style="color:#037691" %)**MQTT Management**
758 -
759 759  AT+CLIENT               : Get or Set MQTT client
760 760  
761 761  AT+UNAME  : Get or Set MQTT Username
... ... @@ -766,63 +766,42 @@
766 766  
767 767  AT+SUBTOPIC  : Get or Set MQTT subscription topic
768 768  
664 +**Information**          
769 769  
770 -(% style="color:#037691" %)**Information**          
771 -
772 772  AT+FDR  : Factory Data Reset
773 773  
774 774  AT+PWORD  : Serial Access Password
775 775  
776 -
777 -
778 778  = ​5.  FAQ =
779 779  
780 -
781 781  == 5.1 ​ How to Upgrade Firmware ==
782 782  
783 -
784 784  User can upgrade the firmware for 1) bug fix, 2) new feature release.
785 785  
786 786  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]]
787 787  
788 -(% 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.**
789 789  
790 -
791 -
792 792  == 5.2  Can I calibrate NSPH01 to different soil types? ==
793 793  
794 -
795 795  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]].
796 796  
797 -
798 -
799 799  = 6.  Trouble Shooting =
800 800  
801 -
802 802  == 6.1  ​Connection problem when uploading firmware ==
803 803  
804 -
805 805  **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]]
806 806  
807 -
808 -
809 809  == 6.2  AT Command input doesn't work ==
810 810  
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.
811 811  
812 -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.
813 -
814 -
815 -
816 816  = 7. ​ Order Info =
817 817  
818 -
819 819  Part Number**:** NSPH01
820 820  
821 -
822 -
823 823  = 8.  Packing Info =
824 824  
825 -
826 826  **Package Includes**:
827 827  
828 828  * NSPH01 NB-IoT pH Sensor x 1
... ... @@ -830,16 +830,11 @@
830 830  
831 831  **Dimension and weight**:
832 832  
833 -* Device Size: cm
834 -* Device Weight: g
835 -* Package Size / pcs : cm
836 -* Weight / pcs : g
707 +* Size: 195 x 125 x 55 mm
708 +* Weight:   420g
837 837  
838 -
839 -
840 840  = 9.  Support =
841 841  
842 -
843 843  * 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.
844 844  * 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]]
845 845  
image-20220923101327-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.1 KB
Content

Applications

Navigation

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