Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 45.5 >
edited by Xiaoling
on 2022/07/08 10:39
To version < 57.7 >
edited by Xiaoling
on 2022/07/08 11:54
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -59,8 +59,6 @@
59 59  * Micro SIM card slot for NB-IoT SIM
60 60  * 8500mAh Battery for long term use
61 61  
62 -
63 -
64 64  == 1.3  Specification ==
65 65  
66 66  
... ... @@ -69,7 +69,6 @@
69 69  * Supply Voltage: 2.1v ~~ 3.6v
70 70  * Operating Temperature: -40 ~~ 85°C
71 71  
72 -
73 73  (% style="color:#037691" %)**NB-IoT Spec:**
74 74  
75 75  * - B1 @H-FDD: 2100MHz
... ... @@ -79,7 +79,6 @@
79 79  * - B20 @H-FDD: 800MHz
80 80  * - B28 @H-FDD: 700MHz
81 81  
82 -
83 83  (% style="color:#037691" %)**Probe Specification:**
84 84  
85 85  Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
... ... @@ -126,6 +126,7 @@
126 126  
127 127  == 2.2 ​ Configure the NSE01 ==
128 128  
125 +
129 129  === 2.2.1 Test Requirement ===
130 130  
131 131  
... ... @@ -135,11 +135,12 @@
135 135  * The local NB-IoT network used the band that NSE01 supports.
136 136  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137 137  
138 -
135 +(((
139 139  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
137 +)))
140 140  
141 141  
142 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.gif]]
140 +[[image:1657249419225-449.png]]
143 143  
144 144  
145 145  
... ... @@ -147,207 +147,202 @@
147 147  
148 148  Insert the NB-IoT Card get from your provider.
149 149  
150 -
151 151  User need to take out the NB-IoT module and insert the SIM card like below:
152 152  
153 153  
154 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]
151 +[[image:1657249468462-536.png]]
155 155  
156 156  
154 +
157 157  === 2.2.3 Connect USB – TTL to NSE01 to configure it ===
158 158  
157 +(((
158 +(((
159 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
160 +)))
161 +)))
159 159  
160 -User need to configure NSE01 via serial port to set the **(% style="color:blue" %)Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
161 161  
164 +**Connection:**
162 162  
166 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
163 163  
168 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
164 164  
165 -Connection:
170 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
166 166  
167 -USB TTL GND <~-~-~-~-> GND
168 168  
169 -USB TTL TXD <~-~-~-~-> UART_RXD
173 +In the PC, use below serial tool settings:
170 170  
171 -USB TTL RXD <~-~-~-~-> UART_TXD
175 +* Baud:  (% style="color:green" %)**9600**
176 +* Data bits:** (% style="color:green" %)8(%%)**
177 +* Stop bits: (% style="color:green" %)**1**
178 +* Parity:  (% style="color:green" %)**None**
179 +* Flow Control: (% style="color:green" %)**None**
172 172  
181 +(((
182 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
183 +)))
173 173  
185 +[[image:image-20220708110657-3.png]]
174 174  
175 -In the PC, use below serial tool settings:
187 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
176 176  
177 -* Baud: **9600**
178 -* Data bits:** 8**
179 -* Stop bits: **1**
180 -* Parity: **None**
181 -* Flow Control: **None**
182 182  
183 183  
184 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
185 185  
186 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]]
193 +(% 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/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
187 187  
188 -Note: the valid AT Commands can be found at:
189 189  
190 -[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
196 +**Use below commands:**
191 191  
198 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
199 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
200 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
192 192  
193 -1.
194 -11.
195 -111. Use CoAP protocol to uplink data 
202 +For parameter description, please refer to AT command set
196 196  
204 +[[image:1657249793983-486.png]]
197 197  
198 -Note: if you don’t have CoAP server, you can refer this link to set up one:
199 199  
200 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
207 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
201 201  
209 +[[image:1657249831934-534.png]]
202 202  
203 -Use below commands:
204 204  
205 -* **AT+PRO=1**    ~/~/ Set to use CoAP protocol to uplink
206 -* **AT+SERVADDR=120.24.4.116,5683   **~/~/ to set CoAP server address and port
207 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0"       **~/~/Set COAP resource path
208 208  
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
209 209  
210 -For parameter description, please refer to AT command set
215 +This feature is supported since firmware version v1.0.1
211 211  
212 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
213 213  
218 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
220 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
214 214  
215 -After configure the server address and **reset the device** (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
222 +[[image:1657249864775-321.png]]
216 216  
217 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
218 218  
219 -1.
220 -11.
221 -111. Use UDP protocol to uplink data(Default protocol)
225 +[[image:1657249930215-289.png]]
222 222  
223 223  
224 -This feature is supported since firmware version v1.0.1
225 225  
229 +=== 2.2.6 Use MQTT protocol to uplink data ===
226 226  
227 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
228 -* **AT+SERVADDR=120.24.4.116,5601   **~/~/ to set UDP server address and port
229 -* **AT+CFM=1       **~/~/If the server does not respond, this command is unnecessary
231 +This feature is supported since firmware version v110
230 230  
231 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
232 232  
234 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
235 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
236 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
237 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
238 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
239 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
240 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
233 233  
242 +[[image:1657249978444-674.png]]
234 234  
235 235  
245 +[[image:1657249990869-686.png]]
236 236  
237 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
238 238  
248 +(((
249 +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.
250 +)))
239 239  
240 -1.
241 -11.
242 -111. Use MQTT protocol to uplink data
243 243  
244 244  
254 +=== 2.2.7 Use TCP protocol to uplink data ===
255 +
245 245  This feature is supported since firmware version v110
246 246  
247 247  
248 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
249 -* **AT+SERVADDR=120.24.4.116,1883   **~/~/Set MQTT server address and port
250 -* **AT+CLIENT=CLIENT **~/~/Set up the CLIENT of MQTT
251 -* **AT+UNAME=UNAME                           **~/~/Set the username of MQTT
252 -* **AT+PWD=PWD                                      **~/~/Set the password of MQTT
253 -* **AT+PUBTOPIC=NSE01_PUB   **~/~/Set the sending topic of MQTT
254 -* **AT+SUBTOPIC=NSE01_SUB    **~/~/Set the subscription topic of MQTT
259 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
260 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
255 255  
262 +[[image:1657250217799-140.png]]
256 256  
257 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
258 258  
259 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
265 +[[image:1657250255956-604.png]]
260 260  
261 261  
262 -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.
263 263  
269 +=== 2.2.8 Change Update Interval ===
264 264  
265 -1.
266 -11.
267 -111. Use TCP protocol to uplink data
271 +User can use below command to change the (% style="color:green" %)**uplink interval**.
268 268  
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
269 269  
270 -This feature is supported since firmware version v110
275 +(((
276 +(% style="color:red" %)**NOTE:**
277 +)))
271 271  
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 +)))
272 272  
273 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
274 -* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
275 275  
276 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
277 277  
285 +== 2.3  Uplink Payload ==
278 278  
287 +In this mode, uplink payload includes in total 18 bytes
279 279  
280 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 +|=(% style="width: 50px;" %)(((
291 +**Size(bytes)**
292 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
293 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
281 281  
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
282 282  
283 -1.
284 -11.
285 -111. Change Update Interval
286 286  
287 -User can use below command to change the **uplink interval**.
298 +[[image:image-20220708111918-4.png]]
288 288  
289 -**~ AT+TDC=600      **~/~/ Set Update Interval to 600s
290 290  
301 +The payload is ASCII string, representative same HEX:
291 291  
292 -**NOTE:**
303 +0x72403155615900640c7817075e0a8c02f900 where:
293 293  
294 -1. By default, the device will send an uplink message every 1 hour.
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
295 295  
308 +* BAT: 0x0c78 = 3192 mV = 3.192V
309 +* Singal: 0x17 = 23
310 +* Soil Moisture: 0x075e= 1886 = 18.86  %
311 +* Soil Temperature:0x0a8c =2700=27 °C
312 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
313 +* Interrupt: 0x00 = 0
296 296  
297 297  
298 298  
317 +== 2.4  Payload Explanation and Sensor Interface ==
299 299  
300 300  
320 +=== 2.4.1  Device ID ===
301 301  
302 -== 2.3 Uplink Payload ==
322 +By default, the Device ID equal to the last 6 bytes of IMEI.
303 303  
324 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
304 304  
305 -=== 2.3.1 MOD~=0(Default Mode) ===
326 +**Example:**
306 306  
307 -LSE01 will uplink payload via LoRaWAN with below payload format: 
328 +AT+DEUI=A84041F15612
308 308  
309 -(((
310 -Uplink payload includes in total 11 bytes.
311 -)))
330 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
312 312  
313 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
314 -|(((
315 -**Size**
316 316  
317 -**(bytes)**
318 -)))|**2**|**2**|**2**|**2**|**2**|**1**
319 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
320 -Temperature
321 321  
322 -(Reserve, Ignore now)
323 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
324 -MOD & Digital Interrupt
334 +=== 2.4.2  Version Info ===
325 325  
326 -(Optional)
327 -)))
336 +Specify the software version: 0x64=100, means firmware version 1.00.
328 328  
329 -=== 2.3.2 MOD~=1(Original value) ===
338 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
330 330  
331 -This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
332 332  
333 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
334 -|(((
335 -**Size**
336 336  
337 -**(bytes)**
338 -)))|**2**|**2**|**2**|**2**|**2**|**1**
339 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
340 -Temperature
342 +=== 2.4.3  Battery Info ===
341 341  
342 -(Reserve, Ignore now)
343 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
344 -MOD & Digital Interrupt
345 -
346 -(Optional)
347 -)))
348 -
349 -=== 2.3.3 Battery Info ===
350 -
351 351  (((
352 352  Check the battery voltage for LSE01.
353 353  )))
... ... @@ -362,14 +362,32 @@
362 362  
363 363  
364 364  
365 -=== 2.3.4 Soil Moisture ===
358 +=== 2.4.4  Signal Strength ===
366 366  
360 +NB-IoT Network signal Strength.
361 +
362 +**Ex1: 0x1d = 29**
363 +
364 +(% style="color:blue" %)**0**(%%)  -113dBm or less
365 +
366 +(% style="color:blue" %)**1**(%%)  -111dBm
367 +
368 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
369 +
370 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
371 +
372 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
373 +
374 +
375 +
376 +=== 2.4.5  Soil Moisture ===
377 +
367 367  (((
368 368  Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
369 369  )))
370 370  
371 371  (((
372 -For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
383 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
373 373  )))
374 374  
375 375  (((
... ... @@ -382,10 +382,10 @@
382 382  
383 383  
384 384  
385 -=== 2.3.5 Soil Temperature ===
396 +=== 2.4.6  Soil Temperature ===
386 386  
387 387  (((
388 - 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
399 + 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
389 389  )))
390 390  
391 391  (((
... ... @@ -402,7 +402,7 @@
402 402  
403 403  
404 404  
405 -=== 2.3.6 Soil Conductivity (EC) ===
416 +=== 2.4.7  Soil Conductivity (EC) ===
406 406  
407 407  (((
408 408  Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
... ... @@ -409,7 +409,7 @@
409 409  )))
410 410  
411 411  (((
412 -For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
423 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
413 413  )))
414 414  
415 415  (((
... ... @@ -424,39 +424,41 @@
424 424  
425 425  )))
426 426  
427 -=== 2.3.7 MOD ===
438 +=== 2.4.8  Digital Interrupt ===
428 428  
429 -Firmware version at least v2.1 supports changing mode.
440 +Digital Interrupt refers to pin **(% style="color:blue" %)GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
430 430  
431 -For example, bytes[10]=90
442 +The command is:
432 432  
433 -mod=(bytes[10]>>7)&0x01=1.
444 +**(% 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]]**).**
434 434  
435 435  
436 -**Downlink Command:**
447 +The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up.
437 437  
438 -If payload = 0x0A00, workmode=0
439 439  
440 -If** **payload =** **0x0A01, workmode=1
450 +Example:
441 441  
452 +0x(00): Normal uplink packet.
442 442  
454 +0x(01): Interrupt Uplink Packet.
443 443  
444 -=== 2.3.8 ​Decode payload in The Things Network ===
445 445  
446 -While using TTN network, you can add the payload format to decode the payload.
447 447  
448 448  
449 -[[image:1654505570700-128.png]]
459 +=== 2.4.9  ​+5V Output ===
450 450  
451 -(((
452 -The payload decoder function for TTN is here:
453 -)))
454 454  
455 -(((
456 -LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
457 -)))
462 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
458 458  
459 459  
465 +The 5V output time can be controlled by AT Command.
466 +
467 +(% style="color:blue" %)**AT+5VT=1000**
468 +
469 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
470 +
471 +
472 +
460 460  == 2.4 Uplink Interval ==
461 461  
462 462  The LSE01 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
1657249419225-449.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +81.0 KB
Content
1657249468462-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657249793983-486.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
1657249831934-534.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.5 KB
Content
1657249864775-321.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +87.0 KB
Content
1657249930215-289.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
1657249978444-674.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +139.5 KB
Content
1657249990869-686.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +96.9 KB
Content
1657250217799-140.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.7 KB
Content
1657250255956-604.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +99.0 KB
Content
image-20220708110657-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +251.7 KB
Content
image-20220708111918-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +38.8 KB
Content

Applications

Navigation

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