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

Applications

Navigation

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