<
From version < 56.1 >
edited by Edwin Chen
on 2022/10/09 00:09
To version < 41.1 >
edited by David Huang
on 2022/09/07 17:00
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.David
Content
... ... @@ -1,42 +1,31 @@
1 1  (% style="text-align:center" %)
2 -[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png||height="442" width="410"]]
2 +[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png]]
3 3  
4 -**Table of Contents:**
4 += **1. Introduction** =
5 5  
6 -{{toc/}}
6 +== **1.1 ​What is NSPH01 Soil pH Sensor** ==
7 7  
8 +The Dragino NSPH01 is a **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.
8 8  
10 +NSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** pH **with high accuracy and stable value. The NSPH01 probe can be buried into soil for long time use.
9 9  
10 -= 1.  Introduction =
11 -
12 -
13 -== 1.1 ​ What is NSPH01 Soil pH Sensor ==
14 -
15 -
16 -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.
17 -
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 -
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.
13 +\\NSPH01 supports different uplink methods include **TCP,MQTT,UDP and CoAP  **for different application requirement.
14 +\\NSPH01 is powered by  **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)
15 +\\To use NSPH01, user needs to check if there is NB-IoT coverage in local area and with the bands NSPH01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install NSPH01 to get NB-IoT network connection.
24 24  
25 -
17 +(% style="text-align:center" %)
26 26  [[image:image-20220907153151-1.png]]
27 27  
28 -
20 +(% style="text-align:center" %)
29 29  [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]]
30 30  
23 +**1.2 Features**
31 31  
32 -
33 -== 1.2  Features ==
34 -
35 -
36 36  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
37 37  * Monitor soil pH with temperature compensation.
38 38  * Monitor soil temperature
39 -* pH and Temperature alarm function
28 +* PH and Temperature alarm function
40 40  * Monitor Battery Level
41 41  * Support pH calibration by end user
42 42  * Uplink on periodically
... ... @@ -45,18 +45,17 @@
45 45  * IP68 rate for the Sensor Probe
46 46  * Ultra-Low Power consumption
47 47  * AT Commands to change parameters
48 -* Micro SIM card slot
37 +* Micro SIM card slot for NB-IoT SIM
49 49  * 8500mAh Battery for long term use
50 50  
51 -== 1.3  Specification ==
40 +**1.3  Specification**
52 52  
42 +**Common DC Characteristics:**
53 53  
54 -(% style="color:#037691" %)**Common DC Characteristics:**
55 -
56 56  * Supply Voltage: 2.1v ~~ 3.6v
57 57  * Operating Temperature: -40 ~~ 85°C
58 58  
59 -(% style="color:#037691" %)**NB-IoT Spec:**
47 +**NB-IoT Spec:**
60 60  
61 61  * - B1 @H-FDD: 2100MHz
62 62  * - B3 @H-FDD: 1800MHz
... ... @@ -65,11 +65,10 @@
65 65  * - B20 @H-FDD: 800MHz
66 66  * - B28 @H-FDD: 700MHz
67 67  
68 -== 1.4  Probe Specification ==
56 +**1.4 Probe Specification**
69 69  
58 +**Soil pH:**
70 70  
71 -(% style="color:#037691" %)**Soil pH:**
72 -
73 73  * Range: 3 ~~ 10 pH
74 74  * Resolution: 0.01 pH
75 75  * Accuracy: ±2% under (0~~50 ℃, Accuracy will poor under 0 due to frozen)
... ... @@ -77,7 +77,7 @@
77 77  * IP68 Protection
78 78  * Length: 3.5 meters
79 79  
80 -(% style="color:#037691" %)**Soil Temperature:**
67 +**Soil Temperature:**
81 81  
82 82  * Range -40℃~85℃
83 83  * Resolution: 0.1℃
... ... @@ -85,243 +85,199 @@
85 85  * IP68 Protection
86 86  * Length: 3.5 meters
87 87  
88 -== 1.5  ​Applications ==
75 +**1.5 ​Applications**
89 89  
90 -
91 91  * Smart Agriculture
92 92  
93 -== 1.6  Pin mapping and power on ==
79 +**1.6 Pin mapping and power on**
94 94  
95 -
81 +(% style="text-align:center" %)
96 96  [[image:image-20220907153300-2.png]]
97 97  
98 98  
85 +**2.  Use NSPH01 to communicate with IoT Server**
99 99  
100 -= 2.  Use NSPH01 to communicate with IoT Server =
87 +**2.1  How it works**
101 101  
102 -
103 -== 2.1  How it works ==
104 -
105 -
106 106  The NSPH01 is equipped with a NB-IoT module, the pre-loaded firmware in NSPH01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NSPH01.
107 107  
108 108  The diagram below shows the working flow in default firmware of NSPH01:
109 109  
110 -
93 +(% style="text-align:center" %)
111 111  [[image:image-20220907153416-3.png]]
112 112  
96 +**2.2 ​ Configure the NSPH01**
113 113  
98 +**2.2.1 Test Requirement**
114 114  
115 -== 2.2 Configure the NSPH01 ==
100 +To use NSPH01 in your city, make sure meet below requirements:
116 116  
117 -
118 -=== 2.2.1 Test Requirement ===
119 -
120 -
121 -To use NSPH01 in the field, make sure meet below requirements:
122 -
123 123  * Your local operator has already distributed a NB-IoT Network there.
124 124  * The local NB-IoT network used the band that NSPH01 supports.
125 125  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
126 126  
127 -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.
106 +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
128 128  
129 -
108 +(% style="text-align:center" %)
130 130  [[image:image-20220907153445-4.png]]
131 131  
132 132  
112 +**2.2.2 Insert SIM card**
133 133  
134 -=== 2.2.2 Insert SIM card ===
114 +Insert the NB-IoT Card get from your provider.
135 135  
116 +User need to take out the NB-IoT module and insert the SIM card like below:
136 136  
137 -User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
138 -
139 -
118 +(% style="text-align:center" %)
140 140  [[image:image-20220907153505-5.png]]
141 141  
121 +**2.2.3 Connect USB – TTL to NSPH01 to configure it**
142 142  
123 +User need to configure NSPH01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NSPH01 support AT Commands, user can use a USB to TTL adapter to connect to NSPH01 and use AT Commands to configure it, as below.
143 143  
144 -=== 2.2.3 Connect USB – TTL to NSPH01 to configure it ===
125 +**Connection:**
145 145  
127 + USB TTL GND <~-~-~-~-> GND
146 146  
147 -User need to configure NSPH01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NSPH01 support AT Commands, user can use a USB to TTL adapter to connect to NSPH01 and use AT Commands to configure it, as below.
129 + USB TTL TXD <~-~-~-~-> UART_RXD
148 148  
131 + USB TTL RXD <~-~-~-~-> UART_TXD
149 149  
150 -(% style="color:blue" %)**Connection:**
151 -
152 -**~ (% style="background-color:yellow" %) USB TTL GND <~-~-~-~->  GND(%%)**
153 -
154 -**~ (% style="background-color:yellow" %) USB TTL TXD  <~-~-~-~->  UART_RXD(%%)**
155 -
156 -**~ (% style="background-color:yellow" %) USB TTL RXD  <~-~-~-~->  UART_TXD(%%)**
157 -
158 -
159 159  In the PC, use below serial tool settings:
160 160  
161 -* Baud:  (% style="color:green" %)**9600**
162 -* Data bits:**  (% style="color:green" %)8(%%)**
163 -* Stop bits:  (% style="color:green" %)**1**
164 -* Parity:  (% style="color:green" %)**None**
165 -* Flow Control: (% style="color:green" %)**None**
135 +* Baud:  **9600**
136 +* Data bits:** 8**
137 +* Stop bits: **1**
138 +* Parity:  **None**
139 +* Flow Control: **None**
166 166  
167 -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.
141 +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 **password: 12345678** to access AT Command input.
168 168  
143 +(% style="text-align:center" %)
144 +[[image:image-20220907153529-6.png]]
169 169  
170 -[[image:image-20220912144017-1.png]]
146 +**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  
148 +**2.2.4 Use CoAP protocol to uplink data**
172 172  
173 -(% 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]]
150 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
174 174  
152 +**Use below commands:**
175 175  
154 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
155 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
156 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
176 176  
177 -=== 2.2.4 Use CoAP protocol to uplink data ===
178 -
179 -
180 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one:**(%%)** **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
181 -
182 -
183 -(% style="color:blue" %)**Use below commands:**
184 -
185 -* (% style="color:#037691" %)**AT+PRO=1**                         (%%) ~/~/  Set to use CoAP protocol to uplink
186 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
187 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
188 -
189 189  For parameter description, please refer to AT command set
190 190  
191 -
160 +(% style="text-align:center" %)
192 192  [[image:image-20220907153551-7.png||height="502" width="740"]]
193 193  
163 +After configure the server address and **reset the device** (via AT+ATZ ), NSPH01 will start to uplink sensor values to CoAP server.
194 194  
195 -After configure the server address and (% style="color:green" %)**reset the device (via AT+ATZ )**(%%), NSPH01 will start to uplink sensor values to CoAP server.
196 -
197 -
165 +(% style="text-align:center" %)
198 198  [[image:image-20220907153612-8.png||height="529" width="729"]]
199 199  
200 200  
169 +**2.2.5 Use UDP protocol to uplink data(Default protocol)**
201 201  
202 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
203 -
204 -
205 205  This feature is supported since firmware version v1.0.1
206 206  
207 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
208 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
209 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
173 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
174 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
175 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessar
210 210  
177 +(% style="text-align:center" %)
211 211  [[image:image-20220907153643-9.png||height="401" width="734"]]
212 212  
213 -
180 +(% style="text-align:center" %)
214 214  [[image:image-20220907153703-10.png||height="309" width="738"]]
215 215  
216 216  
184 +**2.2.6 Use MQTT protocol to uplink data**
217 217  
218 -=== 2.2.6 Use MQTT protocol to uplink data ===
219 -
220 -
221 221  This feature is supported since firmware version v110
222 222  
223 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/ Set to use MQTT protocol to uplink
224 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/ Set MQTT server address and port
225 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/ Set up the CLIENT of MQTT
226 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/ Set the username of MQTT
227 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/ Set the password of MQTT
228 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/ Set the sending topic of MQTT
229 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/ Set the subscription topic of MQTT
188 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
189 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
190 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
191 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
192 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
193 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
194 +* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
230 230  
196 +(% style="text-align:center" %)
231 231  [[image:image-20220907153739-11.png||height="491" width="764"]]
232 232  
233 -
199 +(% style="text-align:center" %)
234 234  [[image:image-20220907153751-12.png||height="555" width="769"]]
235 235  
236 -
237 237  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.
238 238  
204 +**2.2.7 Use TCP protocol to uplink data**
239 239  
240 -
241 -
242 -=== 2.2.7 Use TCP protocol to uplink data ===
243 -
244 -
245 245  This feature is supported since firmware version v110
246 246  
247 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
248 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ to set TCP server address and port
208 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
209 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
249 249  
211 +(% style="text-align:center" %)
250 250  [[image:image-20220907153818-13.png||height="486" width="668"]]
251 251  
252 -
214 +(% style="text-align:center" %)
253 253  [[image:image-20220907153827-14.png||height="236" width="684"]]
254 254  
217 +**2.2.8 Change Update Interval**
255 255  
219 +User can use below command to change the **uplink interval**.
256 256  
257 -=== 2.2.8 Change Update Interval ===
221 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
258 258  
223 +**NOTE:**
259 259  
260 -Users can use the below command to change the **uplink interval**.
225 +**~1. By default, the device will send an uplink message every 2 hour.**
261 261  
262 -* (% style="color:blue" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
227 +**2.3  Uplink Payload**
263 263  
264 -(% 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).**
265 -
266 -
267 -
268 -== 2.3  Uplink Payload ==
269 -
270 -
271 271  In this mode, uplink payload includes 87 bytes in total by default.
272 272  
273 273  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.
274 274  
275 -(% border="2" style="background-color:#ffffcc; color:green; width:1160px" %)
276 -|(% 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
277 -|(% 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  .....
233 +(% style="width:934px" %)
234 +|(% style="width:93px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:41px" %)**2**|(% style="width:126px" %)**1**|(% style="width:54px" %)**1**|(% style="width:84px" %)1|(% style="width:75px" %)2|(% style="width:133px" %)2|(% style="width:70px" %)2|(% style="width:127px" %)4   
235 +|(% style="width:93px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:41px" %)BAT|(% style="width:126px" %)Signal Strength|(% style="width:54px" %)MOD|(% style="width:84px" %)Interrupt|(% style="width:75px" %)Soil PH|(% style="width:133px" %)Soil Temperature|(% style="width:70px" %)Soil PH|(% style="width:127px" %)Time stamp  .....
278 278  
279 279  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
280 280  
239 +(% style="text-align:center" %)
281 281  [[image:image-20220907153902-15.png||height="581" width="804"]]
282 282  
283 283  
284 -(((
285 285  The payload is ASCII string, representative same HEX:
286 -)))
287 287  
288 -(((
289 -
290 -)))
245 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where:
291 291  
292 -(((
293 -**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__//(%%)**
294 -)))
247 +* Device ID: 0xf868411056754138 = f868411056754138
248 +* Version: 0x0064=100=1.0.0
295 295  
296 -(((
297 -
298 -
299 -where:
300 -)))
301 -
302 -* Device ID: 0xf868411056754138 = f868411056754138
303 -* Version:  0x0064=100=1.0.0
304 -* BAT:  0x0c78 = 3192 mV = 3.192V
305 -* Singal: 0x17 = 23
306 -* Mod:  0x01 = 1
250 +* BAT: 0x0c78 = 3192 mV = 3.192V
251 +* Singal: 0x17 = 23
252 +* Mod: 0x01 = 1
307 307  * 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 -* 8 sets of recorded data: Temperature,Soil PH,Time stamp :  010e022663154d77,.......
254 +* Soil PH: 0x0225= 549 = 5.49
255 +* Soil Temperature:0x010B =267=26.7 °C
256 +* Time stamp : 0x6315537b =1662342011
257 +* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb
258 +* 8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
313 313  
314 -== 2.4  Payload Explanation and Sensor Interface ==
260 +**2.4  Payload Explanation and Sensor Interface**
315 315  
262 +**2.4.1  Device ID**
316 316  
317 -=== 2.4.1  Device ID ===
318 -
319 -
320 320  By default, the Device ID equal to the last 15 bits of IMEI.
321 321  
322 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
266 +User can use **AT+DEUI** to set Device ID
323 323  
324 -
325 325  **Example:**
326 326  
327 327  AT+DEUI=868411056754138
... ... @@ -328,20 +328,14 @@
328 328  
329 329  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
330 330  
274 +**2.4.2  Version Info**
331 331  
332 -
333 -=== 2.4.2  Version Info ===
334 -
335 -
336 336  Specify the software version: 0x64=100, means firmware version 1.00.
337 337  
338 338  For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0.
339 339  
280 +**2.4.3  Battery Info**
340 340  
341 -
342 -=== 2.4.3  Battery Info ===
343 -
344 -
345 345  Check the battery voltage for NSPH01.
346 346  
347 347  Ex1: 0x0B45 = 2885mV
... ... @@ -348,11 +348,8 @@
348 348  
349 349  Ex2: 0x0B49 = 2889mV
350 350  
288 +**2.4.4  Signal Strength**
351 351  
352 -
353 -=== 2.4.4  Signal Strength ===
354 -
355 -
356 356  NB-IoT Network signal Strength.
357 357  
358 358  **Ex1: 0x1d = 29**
... ... @@ -367,25 +367,18 @@
367 367  
368 368  **99**    Not known or not detectable
369 369  
304 +**2.4.5  Soil PH**
370 370  
371 -
372 -=== 2.4.5  Soil PH ===
373 -
374 -
375 375  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.
376 376  
377 -For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is
308 +For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is
378 378  
379 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**
310 +**0229(H) = 549(D) /100 = 5.49.**
380 380  
312 +**2.4.6  Soil Temperature**
381 381  
314 +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
382 382  
383 -=== 2.4.6  Soil Temperature ===
384 -
385 -
386 -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
387 -
388 -
389 389  **Example**:
390 390  
391 391  If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
... ... @@ -392,62 +392,56 @@
392 392  
393 393  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
394 394  
322 +**2.4.7  Timestamp**
395 395  
396 -
397 -=== 2.4.7  Timestamp ===
398 -
399 -
400 400  Time stamp : 0x6315537b =1662342011
401 401  
402 402  Convert Unix timestamp to time 2022-9-5 9:40:11.
403 403  
328 +**2.4.8  Digital Interrupt**
404 404  
330 +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.
405 405  
406 -=== 2.4.8  Digital Interrupt ===
407 -
408 -
409 -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.
410 -
411 411  The command is:
412 412  
413 -(% 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]])**.**
334 +**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]])**.**
414 414  
415 415  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.
416 416  
338 +Example:
417 417  
418 -**Example:**
419 -
420 420  0x(00): Normal uplink packet.
421 421  
422 422  0x(01): Interrupt Uplink Packet.
423 423  
344 +**2.4.9  ​+5V Output**
424 424  
425 -
426 -=== 2.4.9  ​+5V Output ===
427 -
428 -
429 429  NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 
430 430  
431 431  The 5V output time can be controlled by AT Command.
432 432  
433 -(% style="color:blue" %)**AT+5VT=1000**
350 +**AT+5VT=1000**
434 434  
435 435  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
436 436  
437 437  
355 +**2.5  Downlink Payload**
438 438  
439 -== 2.5  Downlink Payload ==
440 -
441 -
442 442  By default, NSPH01 prints the downlink payload to console port.
443 443  
359 +(% style="text-align:center" %)
444 444  [[image:image-20220907154636-17.png]]
445 445  
446 446  
447 -(% style="color:blue" %)**Examples:**
448 448  
449 -* (% style="color:#037691" %)** Set TDC**
450 450  
365 +
366 +
367 +
368 +**Examples:**
369 +
370 +* **Set TDC**
371 +
451 451  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
452 452  
453 453  Payload:    01 00 00 1E    TDC=30S
... ... @@ -454,19 +454,16 @@
454 454  
455 455  Payload:    01 00 00 3C    TDC=60S
456 456  
457 -* (% style="color:#037691" %)** Reset**
378 +* **Reset**
458 458  
459 -If payload = 0x04FF, it will reset the NSPH01
380 +If payload = 0x04FF, it will reset the NSE01
460 460  
461 -* (% style="color:#037691" %)** INTMOD**
382 +* **INTMOD**
462 462  
463 463  Downlink Payload: 06000003, Set AT+INTMOD=3
464 464  
386 +**2.6  ​LED Indicator**
465 465  
466 -
467 -== 2.6  ​LED Indicator ==
468 -
469 -
470 470  The NSPH01 has an internal LED which is to show the status of different state.
471 471  
472 472  * 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)
... ... @@ -474,22 +474,16 @@
474 474  * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds.
475 475  * For each uplink probe, LED will be on for 500ms.
476 476  
477 -== 2.7  Installation and Maintain ==
395 +**2.7 Installation and Maintain**
478 478  
397 +**2.7.1 Before measurement**
479 479  
480 -=== 2.7.1  Before measurement ===
481 -
482 -
483 483  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. 
484 484  
401 +**2.7.2 Measurement**
485 485  
403 +**Measurement the soil surface:**
486 486  
487 -=== 2.7.2  Measurement ===
488 -
489 -
490 -(% style="color:#037691" %)**Measurement the soil surface:**
491 -
492 -
493 493  [[image:image-20220907154700-18.png]] ​
494 494  
495 495  Choose the proper measuring position. Split the surface soil according to the measured deep.
... ... @@ -500,18 +500,14 @@
500 500  
501 501  Put soil over the probe after insert. And start to measure.
502 502  
415 +**Measurement inside soil:**
503 503  
504 -(% style="color:#037691" %)**Measurement inside soil:**
505 -
506 506  Dig a hole with diameter > 20CM.
507 507  
508 508  Insert the probe inside, method like measure the surface.
509 509  
421 +**2.7.3 Maintain Probe**
510 510  
511 -
512 -=== 2.7.3  Maintain Probe ===
513 -
514 -
515 515  1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
516 516  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.
517 517  1. Probe reference electrode is also no strong, need to avoid strong force or hitting.
... ... @@ -519,13 +519,12 @@
519 519  1. Avoid the probes to touch oily matter. Which will cause issue in accuracy.
520 520  1. The probe is IP68 can be put in water.
521 521  
522 -== 2.8  PH and Temperature alarm function ==
430 +**2.8 PH and Temperature alarm function**
523 523  
432 +➢ AT Command:
524 524  
525 -(% style="color:#037691" %)**➢ AT Command:**
434 +AT+ PHALARM=min,max
526 526  
527 -(% style="color:blue" %)**AT+ PHALARM=min,max**
528 -
529 529  ² When min=3, and max≠0, Alarm higher than max
530 530  
531 531  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -532,11 +532,10 @@
532 532  
533 533  ² When min≠0 and max≠0, Alarm higher than max or lower than min
534 534  
442 +Example:
535 535  
536 -(% style="color:blue" %)**Example:**
444 +AT+ PHALARM =3,5 ~/~/ Alarm when PH lower than 5.
537 537  
538 -AT+ PHALARM =5,8  ~/~/ Alarm when PH lower than 5.
539 -
540 540  AT+ TEMPALARM=min,max
541 541  
542 542  ² When min=0, and max≠0, Alarm higher than max
... ... @@ -545,71 +545,55 @@
545 545  
546 546  ² When min≠0 and max≠0, Alarm higher than max or lower than min
547 547  
454 +Example:
548 548  
549 -(% style="color:blue" %)**Example:**
456 +AT+ TEMPALARM=0,20 ~/~/ Alarm when temperature lower than 20.
550 550  
551 -AT+ TEMPALARM=20,30  ~/~/ Alarm when temperature lower than 20.
552 552  
459 +**2.9 Set the number of data to be uploaded and the recording time**
553 553  
461 +➢ AT Command:
554 554  
555 -== 2.Set the number of data to be uploaded and the recording time ==
463 +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)
556 556  
557 557  
558 -(% style="color:#037691" %)**➢ AT Command:**
466 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
559 559  
560 -* (% 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)
561 -* (% 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.
468 +**2.10 Read or Clear cached data**
562 562  
563 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
470 + AT Command:
564 564  
565 -[[image:image-20221009000933-1.png||height="750" width="1043"]]
472 +AT+CDP ~/~/ Read cached data
566 566  
567 -
568 -
569 -== 2.10  Read or Clear cached data ==
570 -
571 -
572 -(% style="color:#037691" %)**➢ AT Command:**
573 -
574 -* (% style="color:blue" %)**AT+CDP**        (%%) ~/~/  Read cached data
575 -* (% style="color:blue" %)**AT+CDP=0**    (%%) ~/~/  Clear cached data
576 -
577 577  [[image:image-20220907154700-19.png]]
578 578  
579 579  
477 +AT+CDP=0 ~/~/ Clear cached data
580 580  
581 -== 2.11  Calibration ==
582 582  
480 +**2.11 Calibration**
583 583  
584 584  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).
585 585  
586 586  After stable, user can use below command to calibrate.
587 587  
588 -
589 589  [[image:image-20220907154700-20.png]] ​
590 590  
488 +**2.8  ​Firmware Change Log**
591 591  
490 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
592 592  
593 -== 2.12  Firmware Change Log ==
492 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
594 594  
494 +**2.9  ​Battery Analysis**
595 595  
596 -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]]
496 +**2.9.1  ​Battery Type**
597 597  
598 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
599 -
600 -
601 -
602 -== 2.13  ​Battery Analysis ==
603 -
604 -
605 -=== 2.13.1  ​Battery Type ===
606 -
607 -
608 608  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.
609 609  
610 610  The battery is designed to last for several years depends on the actually use environment and update interval. 
611 611  
612 -The battery-related documents as below:
502 +The battery related documents as below:
613 613  
614 614  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
615 615  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -617,18 +617,15 @@
617 617  
618 618  [[image:image-20220907154700-21.png]] ​
619 619  
510 +**2.9.2  Power consumption Analyze**
620 620  
621 -
622 -=== 2.13.2  Power consumption Analyze ===
623 -
624 -
625 625  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.
626 626  
627 627  Instruction to use as below:
628 628  
629 -(% 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/]]
516 +**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/]]
630 630  
631 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
518 +**Step 2: ** Open it and choose
632 632  
633 633  * Product Model
634 634  * Uplink Interval
... ... @@ -636,45 +636,34 @@
636 636  
637 637  And the Life expectation in difference case will be shown on the right.
638 638  
639 -
526 +(% style="text-align:center" %)
640 640  [[image:image-20220907154700-22.jpeg]]
641 641  
642 642  ​
643 643  
531 +**2.9.3  ​Battery Note**
644 644  
645 -=== 2.13.3  ​Battery Note ===
646 -
647 -
648 648  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.
649 649  
535 +**2.9.4  Replace the battery**
650 650  
651 -
652 -=== 2.13.4  Replace the battery ===
653 -
654 -
655 655  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).
656 656  
539 +**3. ​ Access NB-IoT Module**
657 657  
658 -
659 -= 3. ​ Access NB-IoT Module =
660 -
661 -
662 662  Users can directly access the AT command set of the NB-IoT module.
663 663  
664 664  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/]] 
665 665  
666 -
545 +(% style="text-align:center" %)
667 667  [[image:image-20220907154700-23.png]]
668 668  
669 669  ​
670 670  
550 +**4.  Using the AT Commands**
671 671  
672 -= 4.  Using the AT Commands =
552 +**4.1  Access AT Commands**
673 673  
674 -
675 -== 4.1  Access AT Commands ==
676 -
677 -
678 678  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]]
679 679  
680 680  AT+<CMD>?  : Help on <CMD>
... ... @@ -685,9 +685,8 @@
685 685  
686 686  AT+<CMD>=?  : Get the value
687 687  
564 +**General Commands**      
688 688  
689 -(% style="color:#037691" %)**General Commands**      
690 -
691 691  AT  : Attention       
692 692  
693 693  AT?  : Short Help     
... ... @@ -712,18 +712,13 @@
712 712  
713 713  AT+TR      : Get or Set record time"
714 714  
715 -AT+APN     : Get or set the APN
716 716  
717 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
718 -
719 -AT+DNSCFG  : Get or Set DNS Server
720 -
721 -AT+GETSENSORVALUE   : Returns the current sensor measurement
722 -
723 723  AT+NOUD      : Get or Set the number of data to be uploaded
724 724  
593 +
725 725  AT+CDP     : Read or Clear cached data
726 726  
596 +
727 727  AT+TEMPALARM      : Get or Set alarm of temp
728 728  
729 729  AT+PHALARM     : Get or Set alarm of PH
... ... @@ -731,18 +731,16 @@
731 731  AT+ PHCAL  : calibrate PH value
732 732  
733 733  
734 -(% style="color:#037691" %)**COAP Management**      
604 +**COAP Management**      
735 735  
736 736  AT+URI            : Resource parameters
737 737  
608 +**UDP Management**
738 738  
739 -(% style="color:#037691" %)**UDP Management**
740 -
741 741  AT+CFM          : Upload confirmation mode (only valid for UDP)
742 742  
612 +**MQTT Management**
743 743  
744 -(% style="color:#037691" %)**MQTT Management**
745 -
746 746  AT+CLIENT               : Get or Set MQTT client
747 747  
748 748  AT+UNAME  : Get or Set MQTT Username
... ... @@ -753,78 +753,54 @@
753 753  
754 754  AT+SUBTOPIC  : Get or Set MQTT subscription topic
755 755  
624 +**Information**          
756 756  
757 -(% style="color:#037691" %)**Information**          
758 -
759 759  AT+FDR  : Factory Data Reset
760 760  
761 761  AT+PWORD  : Serial Access Password
762 762  
630 +**​5.  FAQ**
763 763  
632 +**5.1 ​ How to Upgrade Firmware**
764 764  
765 -= ​5.  FAQ =
766 -
767 -
768 -== 5.1 ​ How to Upgrade Firmware ==
769 -
770 -
771 771  User can upgrade the firmware for 1) bug fix, 2) new feature release.
772 772  
773 773  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]]
774 774  
775 -(% style="color:red" %)**Notice, NSPH01 and LSPH01 share the same mother board. They use the same connection and method to update.**
638 +**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.**
776 776  
640 +**5.2  Can I calibrate NSPH01 to different soil types?**
777 777  
778 -
779 -== 5.2  Can I calibrate NSPH01 to different soil types? ==
780 -
781 -
782 782  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]].
783 783  
644 +**6.  Trouble Shooting**
784 784  
646 +**6.1  ​Connection problem when uploading firmware**
785 785  
786 -= 6.  Trouble Shooting =
787 -
788 -
789 -== 6.1  ​Connection problem when uploading firmware ==
790 -
791 -
792 792  **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]]
793 793  
650 +**6.2  AT Command input doesn't work**
794 794  
652 +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.
795 795  
796 -== 6. AT Command input doesn't work ==
654 +**7. Order Info**
797 797  
798 -
799 -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.
800 -
801 -
802 -
803 -= 7. ​ Order Info =
804 -
805 -
806 806  Part Number**:** NSPH01
807 807  
658 +**8.  Packing Info**
808 808  
809 -
810 -= 8.  Packing Info =
811 -
812 -
813 813  **Package Includes**:
814 814  
815 -* NSPH01 NB-IoT pH Sensor x 1
662 +* NSPH01 NB-IoT Soil Moisture & EC Sensor x 1
816 816  * External antenna x 1
817 817  
818 818  **Dimension and weight**:
819 819  
820 -* Device Size: cm
821 -* Device Weight: g
822 -* Package Size / pcs : cm
823 -* Weight / pcs : g
667 +* Size: 195 x 125 x 55 mm
668 +* Weight:   420g
824 824  
825 -= 9.  Support =
670 +**9.  Support**
826 826  
827 -
828 828  * 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.
829 829  * 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]]
830 830  
image-20220912144017-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -149.6 KB
Content
image-20220923101327-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.1 KB
Content
image-20221009000933-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0