Last modified by Bei Jinggeng on 2024/03/30 17:53
<
From version < 58.1 >
edited by Bei Jinggeng
on 2024/03/30 17:45
To version < 56.9 >
edited by Xiaoling
on 2023/04/04 08:50
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -1,16 +3,6 @@
1 -
2 -
3 3  (% style="text-align:center" %)
4 4  [[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png||height="442" width="410"]]
5 5  
6 -
7 -
8 -
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents:**
15 15  
16 16  {{toc/}}
... ... @@ -22,29 +22,17 @@
22 22  == 1.1 ​ What is NSPH01 Soil pH Sensor ==
23 23  
24 24  
25 -(((
26 26  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 -)))
28 28  
29 -(((
30 30  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 -)))
32 32  
33 -(((
34 34  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 -)))
36 36  
37 -(((
38 38  NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
39 -)))
40 40  
41 -(((
42 42  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 -)))
44 44  
45 -(((
46 46  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 -)))
48 48  
49 49  
50 50  [[image:image-20220907153151-1.png]]
... ... @@ -119,6 +119,7 @@
119 119  [[image:image-20220907153300-2.png]]
120 120  
121 121  
100 +
122 122  = 2.  Use NSPH01 to communicate with IoT Server =
123 123  
124 124  == 2.1  How it works ==
... ... @@ -132,6 +132,7 @@
132 132  [[image:image-20220907153416-3.png]]
133 133  
134 134  
114 +
135 135  == 2.2 ​ Configure the NSPH01 ==
136 136  
137 137  === 2.2.1 Test Requirement ===
... ... @@ -183,8 +183,10 @@
183 183  
184 184  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.
185 185  
166 +
186 186  [[image:image-20220912144017-1.png]]
187 187  
169 +
188 188  (% 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]]
189 189  
190 190  
... ... @@ -280,9 +280,9 @@
280 280  
281 281  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.
282 282  
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  .....
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  .....
286 286  
287 287  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
288 288  
... ... @@ -449,12 +449,9 @@
449 449  
450 450  By default, NSPH01 prints the downlink payload to console port.
451 451  
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
434 +[[image:image-20220907154636-17.png]]
457 457  
436 +
458 458  (% style="color:blue" %)**Examples:**
459 459  
460 460  * (% style="color:#037691" %)** Set TDC**
... ... @@ -589,32 +589,8 @@
589 589  
590 590  After stable, user can use below command to calibrate.
591 591  
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 -)))
616 616  
617 - ​
572 +[[image:image-20220907154700-20.png]] ​
618 618  
619 619  
620 620  == 2.12  ​Firmware Change Log ==
... ... @@ -768,12 +768,6 @@
768 768  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.
769 769  
770 770  
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 -
777 777  = 7. ​ Order Info =
778 778  
779 779  
... ... @@ -780,6 +780,7 @@
780 780  Part Number**:** NSPH01
781 781  
782 782  
732 +
783 783  = 8.  Packing Info =
784 784  
785 785  
image-20240330174534-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -445.4 KB
Content
image-20240330174542-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -445.4 KB
Content

Applications

Navigation

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