Changes for page NSPH01-NB-IoT Soil pH Sensor User Manual
Last modified by Bei Jinggeng on 2024/03/30 17:53
Change comment:
Uploaded new attachment "image-20240330174542-2.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - Content
-
... ... @@ -1,6 +1,16 @@ 1 + 2 + 1 1 (% style="text-align:center" %) 2 2 [[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png||height="442" width="410"]] 3 3 6 + 7 + 8 + 9 + 10 + 11 + 12 + 13 + 4 4 **Table of Contents:** 5 5 6 6 {{toc/}} ... ... @@ -12,17 +12,29 @@ 12 12 == 1.1 What is NSPH01 Soil pH Sensor == 13 13 14 14 25 +((( 15 15 The Dragino NSPH01 is a (% style="color:blue" %)**NB-IoT soil pH sensor**(%%) for IoT of Agriculture. It is designed to measure the soil pH and soil temperature, so to send to the platform to analyze the soil acid or alkali level. The probe is IP68 waterproof. 27 +))) 16 16 29 +((( 17 17 NSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** (% style="color:blue" %)pH (%%)**with high accuracy and stable value. The NSPH01 probe can be buried into soil for long time use. 31 +))) 18 18 33 +((( 19 19 NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 35 +))) 20 20 37 +((( 21 21 NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 39 +))) 22 22 41 +((( 23 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) 43 +))) 24 24 45 +((( 25 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. 47 +))) 26 26 27 27 28 28 [[image:image-20220907153151-1.png]] ... ... @@ -97,7 +97,6 @@ 97 97 [[image:image-20220907153300-2.png]] 98 98 99 99 100 - 101 101 = 2. Use NSPH01 to communicate with IoT Server = 102 102 103 103 == 2.1 How it works == ... ... @@ -111,7 +111,6 @@ 111 111 [[image:image-20220907153416-3.png]] 112 112 113 113 114 - 115 115 == 2.2 Configure the NSPH01 == 116 116 117 117 === 2.2.1 Test Requirement === ... ... @@ -163,10 +163,8 @@ 163 163 164 164 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. 165 165 166 - 167 167 [[image:image-20220912144017-1.png]] 168 168 169 - 170 170 (% 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]] 171 171 172 172 ... ... @@ -262,9 +262,9 @@ 262 262 263 263 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. 264 264 265 -(% border="1 .5" style="background-color:#ffffcc;color:green;width:520px" %)266 -| =(% scope="row"style="width:;" %)**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:;" %)**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 .....283 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 284 +|(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:20px" %)**2**|(% style="background-color:#4f81bd; color:white; width:23px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:20px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:51px" %)**2**|(% style="background-color:#4f81bd; color:white; width:49px" %)**4**|(% style="background-color:#4f81bd; color:white; width:49px" %)**2**|(% style="background-color:#4f81bd; color:white; width:34px" %)**2**|(% style="background-color:#4f81bd; color:white; width:39px" %)**4** 285 +|(% style="width:96px" %)Value|(% style="width:83px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:42px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:57px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:69px" %)Soil PH|(% style="width:134px" %)Soil Temperature|(% style="width:98px" %)Time stamp|(% style="width:134px" %)Soil Temperature|(% style="width:68px" %)Soil PH|(% style="width:125px" %)Time stamp ..... 268 268 269 269 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data. 270 270 ... ... @@ -431,9 +431,12 @@ 431 431 432 432 By default, NSPH01 prints the downlink payload to console port. 433 433 434 -[[image:image-20220907154636-17.png]] 452 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 453 +|=(% style="width: 183px; background-color:#4F81BD;color:white" %)**Downlink Control Type**|=(% style="width: 55px; background-color:#4F81BD;color:white" %)FPort|=(% style="width: 93px; background-color:#4F81BD;color:white" %)**Type Code**|=(% style="width: 179px; background-color:#4F81BD;color:white" %)**Downlink payload size(bytes)** 454 +|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 455 +|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 456 +|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 435 435 436 - 437 437 (% style="color:blue" %)**Examples:** 438 438 439 439 * (% style="color:#037691" %)** Set TDC** ... ... @@ -568,8 +568,32 @@ 568 568 569 569 After stable, user can use below command to calibrate. 570 570 592 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 593 +|(% style="background-color:#4f81bd; color:white; width:118px" %)**pH buffer solution**|(% style="background-color:#4f81bd; color:white; width:149px" %)**AT Command to calibrate**|(% style="background-color:#4f81bd; color:white; width:149px" %)**Downlink Command**|(% style="background-color:#4f81bd; color:white; width:99px" %)**Read Cal Value** 594 +|(% style="width:149px" %)4.00|(% style="width:197px" %)AT+PHCAL=4|(% style="width:206px" %)((( 595 +0x13 04 596 +Reply with Calibrate payload 597 +)))|(% style="width:136px" %)((( 598 +AT+PHCAL=? 599 +Example 41,61,91 600 +))) 601 +|(% style="width:149px" %)6.86|(% style="width:197px" %)AT+PHCAL=6|(% style="width:206px" %)((( 602 +0x13 06 603 +Reply with Calibrate payload 604 +)))|(% style="width:136px" %)AT+PHCAL=? 605 +|(% style="width:149px" %)9.18|(% style="width:197px" %)AT+PHCAL=9|(% style="width:206px" %)((( 606 +0x13 09 607 +Reply with Calibrate payload 608 +)))|(% style="width:136px" %)AT+PHCAL=? 609 +|(% style="width:149px" %)Factory Default|(% style="width:197px" %)AT+PHCAL=15|(% style="width:206px" %)((( 610 +0x13 15 611 +Reply with Calibrate payload 612 +)))|(% style="width:136px" %)((( 613 +AT+PHCAL=? 614 +Example 151 615 +))) 571 571 572 - [[image:image-20220907154700-20.png]]617 + 573 573 574 574 575 575 == 2.12 Firmware Change Log == ... ... @@ -723,6 +723,12 @@ 723 723 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. 724 724 725 725 771 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 772 + 773 + 774 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 775 + 776 + 726 726 = 7. Order Info = 727 727 728 728 ... ... @@ -729,7 +729,6 @@ 729 729 Part Number**:** NSPH01 730 730 731 731 732 - 733 733 = 8. Packing Info = 734 734 735 735
- image-20240330174534-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +445.4 KB - Content
- image-20240330174542-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +445.4 KB - Content