Changes for page NSPH01-NB-IoT Soil pH Sensor User Manual
Last modified by Bei Jinggeng on 2024/03/30 17:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 = 1. Introduction = 11 11 12 - 13 13 == 1.1 What is NSPH01 Soil pH Sensor == 14 14 15 15 ... ... @@ -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 21 +NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 25 25 23 +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) 24 + 25 +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 + 27 + 26 26 [[image:image-20220907153151-1.png]] 27 27 28 28 ... ... @@ -29,7 +29,6 @@ 29 29 [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]] 30 30 31 31 32 - 33 33 == 1.2 Features == 34 34 35 35 ... ... @@ -48,9 +48,6 @@ 48 48 * Micro SIM card slot 49 49 * 8500mAh Battery for long term use 50 50 51 - 52 - 53 - 54 54 == 1.3 Specification == 55 55 56 56 ... ... @@ -61,16 +61,13 @@ 61 61 62 62 (% style="color:#037691" %)**NB-IoT Spec:** 63 63 64 -* -B1 @H-FDD: 2100MHz65 -* -B3 @H-FDD: 1800MHz66 -* -B8 @H-FDD: 900MHz67 -* -B5 @H-FDD: 850MHz68 -* -B20 @H-FDD: 800MHz69 -* -B28 @H-FDD: 700MHz62 +* B1 @H-FDD: 2100MHz 63 +* B3 @H-FDD: 1800MHz 64 +* B8 @H-FDD: 900MHz 65 +* B5 @H-FDD: 850MHz 66 +* B20 @H-FDD: 800MHz 67 +* B28 @H-FDD: 700MHz 70 70 71 - 72 - 73 - 74 74 == 1.4 Probe Specification == 75 75 76 76 ... ... @@ -83,8 +83,6 @@ 83 83 * IP68 Protection 84 84 * Length: 3.5 meters 85 85 86 - 87 - 88 88 (% style="color:#037691" %)**Soil Temperature:** 89 89 90 90 * Range -40℃~85℃ ... ... @@ -93,17 +93,11 @@ 93 93 * IP68 Protection 94 94 * Length: 3.5 meters 95 95 96 - 97 - 98 - 99 99 == 1.5 Applications == 100 100 101 101 102 102 * Smart Agriculture 103 103 104 - 105 - 106 - 107 107 == 1.6 Pin mapping and power on == 108 108 109 109 ... ... @@ -113,7 +113,6 @@ 113 113 114 114 = 2. Use NSPH01 to communicate with IoT Server = 115 115 116 - 117 117 == 2.1 How it works == 118 118 119 119 ... ... @@ -128,7 +128,6 @@ 128 128 129 129 == 2.2 Configure the NSPH01 == 130 130 131 - 132 132 === 2.2.1 Test Requirement === 133 133 134 134 ... ... @@ -138,22 +138,21 @@ 138 138 * The local NB-IoT network used the band that NSPH01 supports. 139 139 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 140 140 141 -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 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. 142 142 143 143 144 144 [[image:image-20220907153445-4.png]] 145 145 146 146 147 - 148 148 === 2.2.2 Insert SIM card === 149 149 150 150 151 151 User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%)) 152 152 137 + 153 153 [[image:image-20220907153505-5.png]] 154 154 155 155 156 - 157 157 === 2.2.3 Connect USB – TTL to NSPH01 to configure it === 158 158 159 159 ... ... @@ -176,7 +176,6 @@ 176 176 * Stop bits: (% style="color:green" %)**1** 177 177 * Parity: (% style="color:green" %)**None** 178 178 * Flow Control: (% style="color:green" %)**None** 179 -* 180 180 181 181 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. 182 182 ... ... @@ -187,7 +187,6 @@ 187 187 (% 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]] 188 188 189 189 190 - 191 191 === 2.2.4 Use CoAP protocol to uplink data === 192 192 193 193 ... ... @@ -212,7 +212,6 @@ 212 212 [[image:image-20220907153612-8.png||height="529" width="729"]] 213 213 214 214 215 - 216 216 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 217 217 218 218 ... ... @@ -228,7 +228,6 @@ 228 228 [[image:image-20220907153703-10.png||height="309" width="738"]] 229 229 230 230 231 - 232 232 === 2.2.6 Use MQTT protocol to uplink data === 233 233 234 234 ... ... @@ -251,8 +251,6 @@ 251 251 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. 252 252 253 253 254 - 255 - 256 256 === 2.2.7 Use TCP protocol to uplink data === 257 257 258 258 ... ... @@ -267,7 +267,6 @@ 267 267 [[image:image-20220907153827-14.png||height="236" width="684"]] 268 268 269 269 270 - 271 271 === 2.2.8 Change Update Interval === 272 272 273 273 ... ... @@ -278,7 +278,6 @@ 278 278 (% 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).** 279 279 280 280 281 - 282 282 == 2.3 Uplink Payload == 283 283 284 284 ... ... @@ -286,9 +286,9 @@ 286 286 287 287 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. 288 288 289 -(% border=" 2" style="background-color:#ffffcc; color:green; width:1160px" %)290 -|(% 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" %)4291 -|(% 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 ..... 265 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 266 +|=(% 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** 267 +|=(% 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 ..... 292 292 293 293 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data. 294 294 ... ... @@ -295,28 +295,48 @@ 295 295 [[image:image-20220907153902-15.png||height="581" width="804"]] 296 296 297 297 274 +((( 298 298 The payload is ASCII string, representative same HEX: 276 +))) 299 299 300 -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: 278 +((( 279 + 280 +))) 301 301 302 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 303 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0 304 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 305 -* (% style="color:red" %)Singal: 0x17 = 23 306 -* (% style="color:blue" %)Mod: 0x01 = 1 307 -* (% style="color:green" %)Interrupt: 0x00= 0 308 -* Soil PH: 0x0225= 549 = 5.49 309 -* Soil Temperature: 0x010B =267=26.7 °C 310 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 311 -* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb 312 -* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,....... 282 +((( 283 +**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__//(%%)** 284 +))) 313 313 286 +((( 287 + 314 314 289 +**where:** 290 +))) 315 315 292 +* (% style="color:#037691" %)**Device ID:**(%%)** **0xf868411056754138 = f868411056754138 316 316 317 - ==2.4Payload Explanationand Sensor Interface==294 +* (% style="color:#037691" %)**Version:** (%%) 0x0064=100=1.0.0 318 318 296 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c78 = 3192 mV = 3.192V 319 319 298 +* (% style="color:#037691" %)**Singal:** (%%)0x17 = 23 299 + 300 +* (% style="color:#037691" %)**Mod:** (%%) 0x01 = 1 301 + 302 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 303 + 304 +* (% style="color:#037691" %)**Soil PH:** (%%) 0x0225= 549 = 5.49 305 + 306 +* (% style="color:#037691" %)**Soil Temperature:**(%%) 0x010b =267=26.7 °C 307 + 308 +* (% style="color:#037691" %)**Time stamp :** (%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 309 + 310 +* (% style="color:#037691" %)**Soil Temperature,Soil PH,Time stamp : **(%%) 010b0226631550fb 311 + 312 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%) Temperature,Soil PH,Time stamp : 010e022663154d77,....... 313 + 314 +== 2.4 Payload Explanation and Sensor Interface == 315 + 320 320 === 2.4.1 Device ID === 321 321 322 322 ... ... @@ -332,7 +332,6 @@ 332 332 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 333 333 334 334 335 - 336 336 === 2.4.2 Version Info === 337 337 338 338 ... ... @@ -341,7 +341,6 @@ 341 341 For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0. 342 342 343 343 344 - 345 345 === 2.4.3 Battery Info === 346 346 347 347 ... ... @@ -352,7 +352,6 @@ 352 352 Ex2: 0x0B49 = 2889mV 353 353 354 354 355 - 356 356 === 2.4.4 Signal Strength === 357 357 358 358 ... ... @@ -371,7 +371,6 @@ 371 371 **99** Not known or not detectable 372 372 373 373 374 - 375 375 === 2.4.5 Soil PH === 376 376 377 377 ... ... @@ -382,7 +382,6 @@ 382 382 (% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.** 383 383 384 384 385 - 386 386 === 2.4.6 Soil Temperature === 387 387 388 388 ... ... @@ -396,7 +396,6 @@ 396 396 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 397 397 398 398 399 - 400 400 === 2.4.7 Timestamp === 401 401 402 402 ... ... @@ -405,7 +405,6 @@ 405 405 Convert Unix timestamp to time 2022-9-5 9:40:11. 406 406 407 407 408 - 409 409 === 2.4.8 Digital Interrupt === 410 410 411 411 ... ... @@ -425,7 +425,6 @@ 425 425 0x(01): Interrupt Uplink Packet. 426 426 427 427 428 - 429 429 === 2.4.9 +5V Output === 430 430 431 431 ... ... @@ -438,7 +438,6 @@ 438 438 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 439 439 440 440 441 - 442 442 == 2.5 Downlink Payload == 443 443 444 444 ... ... @@ -466,7 +466,6 @@ 466 466 Downlink Payload: 06000003, Set AT+INTMOD=3 467 467 468 468 469 - 470 470 == 2.6 LED Indicator == 471 471 472 472 ... ... @@ -477,12 +477,8 @@ 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 - 481 - 482 - 483 483 == 2.7 Installation and Maintain == 484 484 485 - 486 486 === 2.7.1 Before measurement === 487 487 488 488 ... ... @@ -489,7 +489,6 @@ 489 489 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. 490 490 491 491 492 - 493 493 === 2.7.2 Measurement === 494 494 495 495 ... ... @@ -514,7 +514,6 @@ 514 514 Insert the probe inside, method like measure the surface. 515 515 516 516 517 - 518 518 === 2.7.3 Maintain Probe === 519 519 520 520 ... ... @@ -525,9 +525,6 @@ 525 525 1. Avoid the probes to touch oily matter. Which will cause issue in accuracy. 526 526 1. The probe is IP68 can be put in water. 527 527 528 - 529 - 530 - 531 531 == 2.8 PH and Temperature alarm function == 532 532 533 533 ... ... @@ -560,7 +560,6 @@ 560 560 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 561 561 562 562 563 - 564 564 == 2.9 Set the number of data to be uploaded and the recording time == 565 565 566 566 ... ... @@ -569,7 +569,9 @@ 569 569 * (% 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) 570 570 * (% 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. 571 571 548 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 572 572 550 +[[image:image-20221009000933-1.png||height="750" width="1043"]] 573 573 574 574 575 575 == 2.10 Read or Clear cached data == ... ... @@ -580,11 +580,9 @@ 580 580 * (% style="color:blue" %)**AT+CDP** (%%) ~/~/ Read cached data 581 581 * (% style="color:blue" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 582 582 583 - 584 584 [[image:image-20220907154700-19.png]] 585 585 586 586 587 - 588 588 == 2.11 Calibration == 589 589 590 590 ... ... @@ -596,73 +596,22 @@ 596 596 [[image:image-20220907154700-20.png]] 597 597 598 598 599 - 600 600 == 2.12 Firmware Change Log == 601 601 602 602 603 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1 zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]578 +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]] 604 604 605 605 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 606 606 607 607 583 +== 2.13 Battery & Power Consumption == 608 608 609 -== 2.13 Battery Analysis == 610 610 586 +NSPH01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 611 611 612 - === 2.13.1 BatteryType===588 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 613 613 614 614 615 -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. 616 - 617 -The battery is designed to last for several years depends on the actually use environment and update interval. 618 - 619 -The battery-related documents as below: 620 - 621 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 622 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 623 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 624 - 625 -[[image:image-20220907154700-21.png]] 626 - 627 - 628 - 629 -=== 2.13.2 Power consumption Analyze === 630 - 631 - 632 -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. 633 - 634 -Instruction to use as below: 635 - 636 -(% 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/]] 637 - 638 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 639 - 640 -* Product Model 641 -* Uplink Interval 642 -* Working Mode 643 - 644 -And the Life expectation in difference case will be shown on the right. 645 - 646 - 647 -[[image:image-20220907154700-22.jpeg]] 648 - 649 - 650 - 651 - 652 -=== 2.13.3 Battery Note === 653 - 654 - 655 -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. 656 - 657 - 658 - 659 -=== 2.13.4 Replace the battery === 660 - 661 - 662 -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). 663 - 664 - 665 - 666 666 = 3. Access NB-IoT Module = 667 667 668 668 ... ... @@ -675,10 +675,8 @@ 675 675 676 676 677 677 678 - 679 679 = 4. Using the AT Commands = 680 680 681 - 682 682 == 4.1 Access AT Commands == 683 683 684 684 ... ... @@ -768,10 +768,8 @@ 768 768 AT+PWORD : Serial Access Password 769 769 770 770 771 - 772 772 = 5. FAQ = 773 773 774 - 775 775 == 5.1 How to Upgrade Firmware == 776 776 777 777 ... ... @@ -782,7 +782,6 @@ 782 782 (% style="color:red" %)**Notice, NSPH01 and LSPH01 share the same mother board. They use the same connection and method to update.** 783 783 784 784 785 - 786 786 == 5.2 Can I calibrate NSPH01 to different soil types? == 787 787 788 788 ... ... @@ -789,10 +789,8 @@ 789 789 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]]. 790 790 791 791 792 - 793 793 = 6. Trouble Shooting = 794 794 795 - 796 796 == 6.1 Connection problem when uploading firmware == 797 797 798 798 ... ... @@ -799,7 +799,6 @@ 799 799 **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]] 800 800 801 801 802 - 803 803 == 6.2 AT Command input doesn't work == 804 804 805 805 ... ... @@ -806,7 +806,6 @@ 806 806 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. 807 807 808 808 809 - 810 810 = 7. Order Info = 811 811 812 812 ... ... @@ -829,9 +829,6 @@ 829 829 * Package Size / pcs : cm 830 830 * Weight / pcs : g 831 831 832 - 833 - 834 - 835 835 = 9. Support = 836 836 837 837
- 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