Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 45.4 >
edited by Xiaoling
on 2022/07/08 10:36
To version < 59.1 >
edited by Xiaoling
on 2022/07/08 13:54
>
Change comment: Uploaded new attachment "1657259653666-883.png", version {1}

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,223 +135,214 @@
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  
146 -1.
147 -11.
148 -111. Insert SIM card
144 +=== 2.2.2 Insert SIM card ===
149 149  
150 150  Insert the NB-IoT Card get from your provider.
151 151  
152 -
153 153  User need to take out the NB-IoT module and insert the SIM card like below:
154 154  
155 155  
156 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]
151 +[[image:1657249468462-536.png]]
157 157  
158 158  
159 -1.
160 -11.
161 -111. Connect USB – TTL to NSE01 to configure it
162 162  
155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
163 163  
164 -User need to configure NSE01 via serial port to set the **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.
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 +)))
165 165  
166 166  
164 +**Connection:**
167 167  
166 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
168 168  
169 -Connection:
168 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
170 170  
171 -USB TTL GND <~-~-~-~-> GND
170 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
172 172  
173 -USB TTL TXD <~-~-~-~-> UART_RXD
174 174  
175 -USB TTL RXD <~-~-~-~-> UART_TXD
176 -
177 -
178 -
179 179  In the PC, use below serial tool settings:
180 180  
181 -* Baud: **9600**
182 -* Data bits:** 8**
183 -* Stop bits: **1**
184 -* Parity: **None**
185 -* Flow Control: **None**
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**
186 186  
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 +)))
187 187  
188 -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.
185 +[[image:image-20220708110657-3.png]]
189 189  
190 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]]
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/]]
191 191  
192 -Note: the valid AT Commands can be found at:
193 193  
194 -[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
195 195  
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
196 196  
197 -1.
198 -11.
199 -111. Use CoAP protocol to uplink data 
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/]]
200 200  
201 201  
202 -Note: if you don’t have CoAP server, you can refer this link to set up one:
196 +**Use below commands:**
203 203  
204 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
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
205 205  
202 +For parameter description, please refer to AT command set
206 206  
207 -Use below commands:
204 +[[image:1657249793983-486.png]]
208 208  
209 -* **AT+PRO=1**    ~/~/ Set to use CoAP protocol to uplink
210 -* **AT+SERVADDR=120.24.4.116,5683   **~/~/ to set CoAP server address and port
211 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0"       **~/~/Set COAP resource path
212 212  
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.
213 213  
214 -For parameter description, please refer to AT command set
209 +[[image:1657249831934-534.png]]
215 215  
216 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
217 217  
218 218  
219 -After configure the server address and **reset the device** (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
220 220  
221 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
215 +This feature is supported since firmware version v1.0.1
222 222  
223 -1.
224 -11.
225 -111. Use UDP protocol to uplink data(Default protocol)
226 226  
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
227 227  
228 -This feature is supported since firmware version v1.0.1
222 +[[image:1657249864775-321.png]]
229 229  
230 230  
231 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
232 -* **AT+SERVADDR=120.24.4.116,5601   **~/~/ to set UDP server address and port
233 -* **AT+CFM=1       **~/~/If the server does not respond, this command is unnecessary
225 +[[image:1657249930215-289.png]]
234 234  
235 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
236 236  
237 237  
229 +=== 2.2.6 Use MQTT protocol to uplink data ===
238 238  
231 +This feature is supported since firmware version v110
239 239  
240 240  
241 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
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
242 242  
242 +[[image:1657249978444-674.png]]
243 243  
244 -1.
245 -11.
246 -111. Use MQTT protocol to uplink data
247 247  
245 +[[image:1657249990869-686.png]]
248 248  
249 -This feature is supported since firmware version v110
250 250  
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 +)))
251 251  
252 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
253 -* **AT+SERVADDR=120.24.4.116,1883   **~/~/Set MQTT server address and port
254 -* **AT+CLIENT=CLIENT **~/~/Set up the CLIENT of MQTT
255 -* **AT+UNAME=UNAME                           **~/~/Set the username of MQTT
256 -* **AT+PWD=PWD                                      **~/~/Set the password of MQTT
257 -* **AT+PUBTOPIC=NSE01_PUB   **~/~/Set the sending topic of MQTT
258 -* **AT+SUBTOPIC=NSE01_SUB    **~/~/Set the subscription topic of MQTT
259 259  
260 260  
261 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
254 +=== 2.2.7 Use TCP protocol to uplink data ===
262 262  
263 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
256 +This feature is supported since firmware version v110
264 264  
265 265  
266 -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.
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
267 267  
262 +[[image:1657250217799-140.png]]
268 268  
269 -1.
270 -11.
271 -111. Use TCP protocol to uplink data
272 272  
265 +[[image:1657250255956-604.png]]
273 273  
274 -This feature is supported since firmware version v110
275 275  
276 276  
277 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
278 -* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
269 +=== 2.2.8 Change Update Interval ===
279 279  
280 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
271 +User can use below command to change the (% style="color:green" %)**uplink interval**.
281 281  
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
282 282  
275 +(((
276 +(% style="color:red" %)**NOTE:**
277 +)))
283 283  
284 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 +)))
285 285  
286 286  
287 -1.
288 -11.
289 -111. Change Update Interval
290 290  
291 -User can use below command to change the **uplink interval**.
285 +== 2.3  Uplink Payload ==
292 292  
293 -**~ AT+TDC=600      **~/~/ Set Update Interval to 600s
287 +In this mode, uplink payload includes in total 18 bytes
294 294  
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"]]
295 295  
296 -**NOTE:**
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
297 297  
298 -1. By default, the device will send an uplink message every 1 hour.
299 299  
298 +[[image:image-20220708111918-4.png]]
300 300  
301 301  
301 +The payload is ASCII string, representative same HEX:
302 302  
303 +0x72403155615900640c7817075e0a8c02f900 where:
303 303  
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
304 304  
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
305 305  
306 -== 2.3 Uplink Payload ==
307 307  
316 +== 2.4  Payload Explanation and Sensor Interface ==
308 308  
309 -=== 2.3.1 MOD~=0(Default Mode) ===
310 310  
311 -LSE01 will uplink payload via LoRaWAN with below payload format: 
319 +=== 2.4.1  Device ID ===
312 312  
313 -(((
314 -Uplink payload includes in total 11 bytes.
315 -)))
321 +By default, the Device ID equal to the last 6 bytes of IMEI.
316 316  
317 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
318 -|(((
319 -**Size**
323 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
320 320  
321 -**(bytes)**
322 -)))|**2**|**2**|**2**|**2**|**2**|**1**
323 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
324 -Temperature
325 +**Example:**
325 325  
326 -(Reserve, Ignore now)
327 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
328 -MOD & Digital Interrupt
327 +AT+DEUI=A84041F15612
329 329  
330 -(Optional)
331 -)))
329 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
332 332  
333 -=== 2.3.2 MOD~=1(Original value) ===
334 334  
335 -This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
336 336  
337 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
338 -|(((
339 -**Size**
333 +=== 2.4.2  Version Info ===
340 340  
341 -**(bytes)**
342 -)))|**2**|**2**|**2**|**2**|**2**|**1**
343 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
344 -Temperature
335 +Specify the software version: 0x64=100, means firmware version 1.00.
345 345  
346 -(Reserve, Ignore now)
347 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
348 -MOD & Digital Interrupt
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
349 349  
350 -(Optional)
351 -)))
352 352  
353 -=== 2.3.3 Battery Info ===
354 354  
341 +=== 2.4.3  Battery Info ===
342 +
355 355  (((
356 356  Check the battery voltage for LSE01.
357 357  )))
... ... @@ -366,14 +366,32 @@
366 366  
367 367  
368 368  
369 -=== 2.3.4 Soil Moisture ===
357 +=== 2.4.4  Signal Strength ===
370 370  
359 +NB-IoT Network signal Strength.
360 +
361 +**Ex1: 0x1d = 29**
362 +
363 +(% style="color:blue" %)**0**(%%)  -113dBm or less
364 +
365 +(% style="color:blue" %)**1**(%%)  -111dBm
366 +
367 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
368 +
369 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
370 +
371 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
372 +
373 +
374 +
375 +=== 2.4.5  Soil Moisture ===
376 +
371 371  (((
372 372  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.
373 373  )))
374 374  
375 375  (((
376 -For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
382 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
377 377  )))
378 378  
379 379  (((
... ... @@ -386,10 +386,10 @@
386 386  
387 387  
388 388  
389 -=== 2.3.5 Soil Temperature ===
395 +=== 2.4.6  Soil Temperature ===
390 390  
391 391  (((
392 - 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
398 + 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
393 393  )))
394 394  
395 395  (((
... ... @@ -406,7 +406,7 @@
406 406  
407 407  
408 408  
409 -=== 2.3.6 Soil Conductivity (EC) ===
415 +=== 2.4.7  Soil Conductivity (EC) ===
410 410  
411 411  (((
412 412  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).
... ... @@ -413,7 +413,7 @@
413 413  )))
414 414  
415 415  (((
416 -For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
422 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
417 417  )))
418 418  
419 419  (((
... ... @@ -428,52 +428,47 @@
428 428  
429 429  )))
430 430  
431 -=== 2.3.7 MOD ===
437 +=== 2.4.8  Digital Interrupt ===
432 432  
433 -Firmware version at least v2.1 supports changing mode.
439 +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.
434 434  
435 -For example, bytes[10]=90
441 +The command is:
436 436  
437 -mod=(bytes[10]>>7)&0x01=1.
443 +(% 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]])**.**
438 438  
439 439  
440 -**Downlink Command:**
446 +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.
441 441  
442 -If payload = 0x0A00, workmode=0
443 443  
444 -If** **payload =** **0x0A01, workmode=1
449 +Example:
445 445  
451 +0x(00): Normal uplink packet.
446 446  
453 +0x(01): Interrupt Uplink Packet.
447 447  
448 -=== 2.3.8 ​Decode payload in The Things Network ===
449 449  
450 -While using TTN network, you can add the payload format to decode the payload.
451 451  
457 +=== 2.4.9  ​+5V Output ===
452 452  
453 -[[image:1654505570700-128.png]]
459 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
454 454  
455 -(((
456 -The payload decoder function for TTN is here:
457 -)))
458 458  
459 -(((
460 -LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
461 -)))
462 +The 5V output time can be controlled by AT Command.
462 462  
464 +(% style="color:blue" %)**AT+5VT=1000**
463 463  
464 -== 2.4 Uplink Interval ==
466 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
465 465  
466 -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"]]
467 467  
468 468  
470 +== 2.5  Downlink Payload ==
469 469  
470 -== 2.5 Downlink Payload ==
471 -
472 472  By default, LSE50 prints the downlink payload to console port.
473 473  
474 -[[image:image-20220606165544-8.png]]
474 +[[image:image-20220708133731-5.png]]
475 475  
476 476  
477 +
477 477  (((
478 478  (% style="color:blue" %)**Examples:**
479 479  )))
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
1657259653666-883.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +344.4 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
image-20220708133731-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 KB
Content

Applications

Navigation

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