Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 45.6 >
edited by Xiaoling
on 2022/07/08 10:57
To version < 60.1 >
edited by Xiaoling
on 2022/07/08 14:04
>
Change comment: Uploaded new attachment "image-20220708140453-6.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,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,23 +147,24 @@
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  
163 -
164 -
165 -Connection:
166 -
167 167   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
168 168  
169 169   (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
... ... @@ -171,181 +171,176 @@
171 171   (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
172 172  
173 173  
174 -
175 175  In the PC, use below serial tool settings:
176 176  
177 -* Baud: ** (% style="background-color:green" %)9600**(%%)
178 -* Data bits:** (% style="background-color:green" %)8**(%%)
179 -* Stop bits: **(% style="background-color:green" %)1**(%%)
180 -* Parity: **(% style="background-color:green" %)None**(%%)
181 -* Flow Control: **(% style="background-color:green" %)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**
182 182  
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 +)))
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 **(% style="background-color:green" %)password: 12345678**(%%) to access AT Command input.
185 +[[image:image-20220708110657-3.png]]
185 185  
186 -[[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/]]
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/]]
191 191  
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
192 192  
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/]]
193 193  
194 -=== 2.2.4 Use CoAP protocol to uplink data === 
195 195  
196 +**Use below commands:**
196 196  
197 -(% style="background-color:red" %)Note: if you don’t have CoAP server, you can refer this link to set up one:
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
198 198  
199 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
202 +For parameter description, please refer to AT command set
200 200  
204 +[[image:1657249793983-486.png]]
201 201  
202 -Use below commands:
203 203  
204 -* **(% style="color:blue" %)AT+PRO=1**  (%%)  ~/~/ Set to use CoAP protocol to uplink
205 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
206 -* **(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
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.
207 207  
209 +[[image:1657249831934-534.png]]
208 208  
209 -For parameter description, please refer to AT command set
210 210  
211 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
212 212  
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
213 213  
214 -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.
215 +This feature is supported since firmware version v1.0.1
215 215  
216 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
217 217  
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
218 218  
219 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
222 +[[image:1657249864775-321.png]]
220 220  
221 221  
222 -This feature is supported since firmware version v1.0.1
225 +[[image:1657249930215-289.png]]
223 223  
224 224  
225 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
226 -* **AT+SERVADDR=120.24.4.116,5601   **~/~/ to set UDP server address and port
227 -* **AT+CFM=1       **~/~/If the server does not respond, this command is unnecessary
228 228  
229 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
229 +=== 2.2.6 Use MQTT protocol to uplink data ===
230 230  
231 +This feature is supported since firmware version v110
231 231  
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 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
236 236  
245 +[[image:1657249990869-686.png]]
237 237  
238 -1.
239 -11.
240 -111. Use MQTT protocol to uplink data
241 241  
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 +)))
242 242  
243 -This feature is supported since firmware version v110
244 244  
245 245  
246 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
247 -* **AT+SERVADDR=120.24.4.116,1883   **~/~/Set MQTT server address and port
248 -* **AT+CLIENT=CLIENT **~/~/Set up the CLIENT of MQTT
249 -* **AT+UNAME=UNAME                           **~/~/Set the username of MQTT
250 -* **AT+PWD=PWD                                      **~/~/Set the password of MQTT
251 -* **AT+PUBTOPIC=NSE01_PUB   **~/~/Set the sending topic of MQTT
252 -* **AT+SUBTOPIC=NSE01_SUB    **~/~/Set the subscription topic of MQTT
254 +=== 2.2.7 Use TCP protocol to uplink data ===
253 253  
256 +This feature is supported since firmware version v110
254 254  
255 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
256 256  
257 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
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
258 258  
262 +[[image:1657250217799-140.png]]
259 259  
260 -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.
261 261  
265 +[[image:1657250255956-604.png]]
262 262  
263 -1.
264 -11.
265 -111. Use TCP protocol to uplink data
266 266  
267 267  
268 -This feature is supported since firmware version v110
269 +=== 2.2.8 Change Update Interval ===
269 269  
271 +User can use below command to change the (% style="color:green" %)**uplink interval**.
270 270  
271 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
272 -* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
273 273  
274 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
275 +(((
276 +(% style="color:red" %)**NOTE:**
277 +)))
275 275  
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 +)))
276 276  
277 277  
278 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
279 279  
285 +== 2.3  Uplink Payload ==
280 280  
281 -1.
282 -11.
283 -111. Change Update Interval
287 +In this mode, uplink payload includes in total 18 bytes
284 284  
285 -User can use below command to change the **uplink interval**.
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"]]
286 286  
287 -**~ AT+TDC=600      **~/~/ Set Update Interval to 600s
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
288 288  
289 289  
290 -**NOTE:**
298 +[[image:image-20220708111918-4.png]]
291 291  
292 -1. By default, the device will send an uplink message every 1 hour.
293 293  
301 +The payload is ASCII string, representative same HEX:
294 294  
303 +0x72403155615900640c7817075e0a8c02f900 where:
295 295  
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
296 296  
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
297 297  
298 298  
316 +== 2.4  Payload Explanation and Sensor Interface ==
299 299  
300 -== 2.3 Uplink Payload ==
301 301  
319 +=== 2.4.1  Device ID ===
302 302  
303 -=== 2.3.1 MOD~=0(Default Mode) ===
321 +By default, the Device ID equal to the last 6 bytes of IMEI.
304 304  
305 -LSE01 will uplink payload via LoRaWAN with below payload format: 
323 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
306 306  
307 -(((
308 -Uplink payload includes in total 11 bytes.
309 -)))
325 +**Example:**
310 310  
311 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
312 -|(((
313 -**Size**
327 +AT+DEUI=A84041F15612
314 314  
315 -**(bytes)**
316 -)))|**2**|**2**|**2**|**2**|**2**|**1**
317 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
318 -Temperature
329 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
319 319  
320 -(Reserve, Ignore now)
321 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
322 -MOD & Digital Interrupt
323 323  
324 -(Optional)
325 -)))
326 326  
327 -=== 2.3.2 MOD~=1(Original value) ===
333 +=== 2.4.2  Version Info ===
328 328  
329 -This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
335 +Specify the software version: 0x64=100, means firmware version 1.00.
330 330  
331 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
332 -|(((
333 -**Size**
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
334 334  
335 -**(bytes)**
336 -)))|**2**|**2**|**2**|**2**|**2**|**1**
337 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
338 -Temperature
339 339  
340 -(Reserve, Ignore now)
341 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
342 -MOD & Digital Interrupt
343 343  
344 -(Optional)
345 -)))
341 +=== 2.4.3  Battery Info ===
346 346  
347 -=== 2.3.3 Battery Info ===
348 -
349 349  (((
350 350  Check the battery voltage for LSE01.
351 351  )))
... ... @@ -360,14 +360,32 @@
360 360  
361 361  
362 362  
363 -=== 2.3.4 Soil Moisture ===
357 +=== 2.4.4  Signal Strength ===
364 364  
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 +
365 365  (((
366 366  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.
367 367  )))
368 368  
369 369  (((
370 -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
371 371  )))
372 372  
373 373  (((
... ... @@ -380,10 +380,10 @@
380 380  
381 381  
382 382  
383 -=== 2.3.5 Soil Temperature ===
395 +=== 2.4.6  Soil Temperature ===
384 384  
385 385  (((
386 - Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is 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
387 387  )))
388 388  
389 389  (((
... ... @@ -400,7 +400,7 @@
400 400  
401 401  
402 402  
403 -=== 2.3.6 Soil Conductivity (EC) ===
415 +=== 2.4.7  Soil Conductivity (EC) ===
404 404  
405 405  (((
406 406  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).
... ... @@ -407,7 +407,7 @@
407 407  )))
408 408  
409 409  (((
410 -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.
411 411  )))
412 412  
413 413  (((
... ... @@ -422,52 +422,47 @@
422 422  
423 423  )))
424 424  
425 -=== 2.3.7 MOD ===
437 +=== 2.4.8  Digital Interrupt ===
426 426  
427 -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.
428 428  
429 -For example, bytes[10]=90
441 +The command is:
430 430  
431 -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]])**.**
432 432  
433 433  
434 -**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.
435 435  
436 -If payload = 0x0A00, workmode=0
437 437  
438 -If** **payload =** **0x0A01, workmode=1
449 +Example:
439 439  
451 +0x(00): Normal uplink packet.
440 440  
453 +0x(01): Interrupt Uplink Packet.
441 441  
442 -=== 2.3.8 ​Decode payload in The Things Network ===
443 443  
444 -While using TTN network, you can add the payload format to decode the payload.
445 445  
457 +=== 2.4.9  ​+5V Output ===
446 446  
447 -[[image:1654505570700-128.png]]
459 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
448 448  
449 -(((
450 -The payload decoder function for TTN is here:
451 -)))
452 452  
453 -(((
454 -LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
455 -)))
462 +The 5V output time can be controlled by AT Command.
456 456  
464 +(% style="color:blue" %)**AT+5VT=1000**
457 457  
458 -== 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.
459 459  
460 -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"]]
461 461  
462 462  
470 +== 2.5  Downlink Payload ==
463 463  
464 -== 2.5 Downlink Payload ==
465 -
466 466  By default, LSE50 prints the downlink payload to console port.
467 467  
468 -[[image:image-20220606165544-8.png]]
474 +[[image:image-20220708133731-5.png]]
469 469  
470 470  
477 +
471 471  (((
472 472  (% style="color:blue" %)**Examples:**
473 473  )))
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
image-20220708140453-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +132.7 KB
Content

Applications

Navigation

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