Last modified by Bei Jinggeng on 2024/03/30 17:53
<
From version < 56.4 >
edited by Xiaoling
on 2022/10/25 16:40
To version < 43.1 >
edited by David Huang
on 2022/09/07 17:05
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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