<
From version < 26.1 >
edited by Xiaoling
on 2023/01/31 13:49
To version < 37.2 >
edited by Xiaoling
on 2023/01/31 14:05
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -197,7 +197,7 @@
197 197  [[image:1675071855856-879.png]]
198 198  
199 199  
200 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:black; width:510px" %)
200 +(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
201 201  |(% style="width:138px" %)**Behavior on ACT**|(% style="width:100px" %)**Function**|**Action**
202 202  |(% style="width:138px" %)Pressing ACT between 1s < time < 3s|(% style="width:100px" %)Send an uplink|(((
203 203  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, **blue led** will blink once.
... ... @@ -244,21 +244,28 @@
244 244  [[image:1675143884058-338.png]]
245 245  
246 246  
247 +[[image:1675143899218-599.png]]
247 247  
248 248  
249 -1. Configure PS-LB to connect to LoRaWAN network
250 -11. How it works
250 +[[image:1675143909447-639.png]]
251 251  
252 +
253 += 2. Configure PS-LB to connect to LoRaWAN network =
254 +
255 +== 2.1 How it works ==
256 +
257 +
252 252  The PS-LB is configured as **LoRaWAN OTAA Class A** mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and activate the PS-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
253 253  
254 254  
255 -1.
256 -11. ​Quick guide to connect to LoRaWAN server (OTAA)
257 257  
262 +== 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
263 +
264 +
258 258  Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example.
259 259  
260 260  
261 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
268 +[[image:1675144005218-297.png]]
262 262  
263 263  
264 264  The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
... ... @@ -268,58 +268,47 @@
268 268  
269 269  Each PS-LB is shipped with a sticker with the default device EUI as below:
270 270  
278 +[[image:image-20230131134744-2.jpeg]]
271 271  
272 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
273 273  
274 274  
275 -
276 -
277 -
278 278  You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
279 279  
280 280  
281 281  **Register the device**
282 282  
283 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
287 +[[image:1675144099263-405.png]]
284 284  
285 285  
286 286  **Add APP EUI and DEV EUI**
287 287  
292 +[[image:1675144117571-832.png]]
288 288  
289 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
290 290  
291 -
292 292  **Add APP EUI in the application**
293 293  
294 294  
295 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
298 +[[image:1675144143021-195.png]]
296 296  
297 297  
298 298  **Add APP KEY**
299 299  
300 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
303 +[[image:1675144157838-392.png]]
301 301  
302 -
303 303  **Step 2**: Activate on PS-LB
304 304  
305 305  
306 306  Press the button for 5 seconds to activate the PS-LB.
307 307  
308 -
309 309  **Green led** will fast blink 5 times, device will enter **OTA mode** for 3 seconds. And then start to JOIN LoRaWAN network. **Green led** will solidly turn on for 5 seconds after joined in network.
310 310  
311 -
312 312  After join success, it will start to upload messages to TTN and you can see the messages in the panel.
313 313  
314 314  
315 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
316 316  
316 +== 2.3 ​Uplink Payload ==
317 317  
318 318  
319 -
320 -1.
321 -11. ​Uplink Payload
322 -
323 323  Uplink payloads have two types:
324 324  
325 325  * Distance Value: Use FPORT=2
... ... @@ -328,27 +328,24 @@
328 328  The application server should parse the correct value based on FPORT settings.
329 329  
330 330  
327 +=== 2.3.1 Device Status, FPORT~=5 ===
331 331  
332 -1.
333 -11.
334 -111. Device Status, FPORT=5
335 335  
336 336  Include device configure status. Once PS-LB Joined the network, it will uplink this message to the server.
337 337  
338 -
339 339  Users can also use the downlink command(0x26 01) to ask PS-LB to resend this uplink.
340 340  
341 341  
335 +(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
342 342  |(% colspan="6" %)**Device Status (FPORT=5)**
343 -|**Size (bytes)**|**1**|**2**|**1**|**1**|**2**
344 -|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT
337 +|(% style="width:103px" %)**Size (bytes)**|(% style="width:72px" %)**1**|**2**|**1**|**1**|**2**
338 +|(% style="width:103px" %)**Value**|(% style="width:72px" %)Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT
345 345  
346 346  Example parse in TTNv3
347 347  
348 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
342 +[[image:1675144504430-490.png]]
349 349  
350 350  
351 -
352 352  **Sensor Model**: For PS-LB, this value is 0x16
353 353  
354 354  **Firmware Version**: 0x0100, Means: v1.0.0 version
... ... @@ -402,33 +402,25 @@
402 402  Ex2: 0x0B49 = 2889mV
403 403  
404 404  
398 +=== 1.3.2 Sensor value, FPORT~=2 ===
405 405  
406 -1.
407 -11.
408 -111. Sensor value, FPORT=2
409 409  
410 410  Uplink payload includes in total 9 bytes.
411 411  
412 412  
413 -|(((
414 -**Size**
404 +(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
405 +|(% style="width:97px" %)(((
406 +**Size(bytes)**
407 +)))|(% style="width:48px" %)**2**|(% style="width:58px" %)**2**|**2**|**2**|**1**
408 +|(% style="width:97px" %)**Value**|(% style="width:48px" %)[[BAT>>path:#bat]]|(% style="width:58px" %)[[Probe Model>>path:#Probe_Model]]|0 ~~ 20mA value|[[0 ~~~~ 30v value>>path:#Voltage_30v]]|[[IN1 &IN2 Interrupt  flag>>path:#Int_pin]]
415 415  
416 -**(bytes)**
417 -)))|**2**|**2**|**2**|**2**|**1**
418 -|**Value**|[[BAT>>path:#bat]]|[[Probe Model>>path:#Probe_Model]]|0 ~~ 20mA value|[[0 ~~~~ 30v value>>path:#Voltage_30v]]|[[IN1 &IN2 Interrupt  flag>>path:#Int_pin]]
410 +[[image:1675144608950-310.png]]
419 419  
420 420  
421 421  
414 +=== 2.3.3 Battery Info ===
422 422  
423 423  
424 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
425 -
426 -
427 -
428 -1.
429 -11.
430 -111. Battery Info
431 -
432 432  Check the battery voltage for PS-LB.
433 433  
434 434  Ex1: 0x0B45 = 2885mV
... ... @@ -436,50 +436,45 @@
436 436  Ex2: 0x0B49 = 2889mV
437 437  
438 438  
439 -1.
440 -11.
441 -111. Probe Model
424 +=== 2.3.4 Probe Model ===
442 442  
426 +
443 443  PS-LB has different kind of probe, 0~~20mA represent the full scale of the measuring range. So a 15mA output means different meaning for different probe. 
444 444  
445 445  
446 446  For example.
447 447  
448 -|**Part Number**|**Probe Used**|**0~~20mA scale**|**Example: 10mA meaning**
449 -|PS-LB-I3|immersion type with 3 meters cable|0~~3 meters|1.5 meters pure water
450 -|PS-LB-I5|immersion type with 5 meters cable|0~~5 meters|2.5 meters pure water
432 +(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
433 +|(% style="width:111px" %)**Part Number**|(% style="width:158px" %)**Probe Used**|**0~~20mA scale**|**Example: 10mA meaning**
434 +|(% style="width:111px" %)PS-LB-I3|(% style="width:158px" %)immersion type with 3 meters cable|0~~3 meters|1.5 meters pure water
435 +|(% style="width:111px" %)PS-LB-I5|(% style="width:158px" %)immersion type with 5 meters cable|0~~5 meters|2.5 meters pure water
451 451  
452 452  The probe model field provides the convenient for server to identical how it should parse the 0~~20mA sensor value and get the correct value.
453 453  
454 454  
455 -1.
456 -11.
457 -111. 0~~20mA value (IDC_IN)
440 +=== 2.3.5 0~~20mA value (IDC_IN) ===
458 458  
442 +
459 459  The output value from Pressure Probe, use together with Probe Model to get the pressure value or water level.
460 460  
461 -
462 462  **Example**:
463 463  
464 464  27AE(H) = 10158 (D)/1000 = 10.158mA.
465 465  
466 466  
467 -1.
468 -11.
469 -111. 0~~30V value ( pin VDC_IN)
450 +=== 2.3.6 0~~30V value ( pin VDC_IN) ===
470 470  
452 +
471 471  Measure the voltage value. The range is 0 to 30V.
472 472  
473 -
474 474  **Example**:
475 475  
476 476  138E(H) = 5006(D)/1000= 5.006V
477 477  
478 478  
479 -1.
480 -11.
481 -111. IN1&IN2&INT pin
460 +=== 2.3.7 IN1&IN2&INT pin ===
482 482  
462 +
483 483  IN1 and IN2 are used as digital input pins.
484 484  
485 485  **Example**:
... ... @@ -489,10 +489,8 @@
489 489  09 (H) :(0x09&0x04)>>2=0    IN2 pin is low level.
490 490  
491 491  
492 -
493 493  This data field shows if this packet is generated by **Interrupt Pin** or not. [[Click here>>path:#Int_mod]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal.
494 494  
495 -
496 496  **Example:**
497 497  
498 498  09 (H) : (0x09&0x02)>>1=1    The level of the interrupt pin.
... ... @@ -502,101 +502,78 @@
502 502  0x01: Interrupt Uplink Packet.
503 503  
504 504  
483 +=== 2.3.8 ​Decode payload in The Things Network ===
505 505  
506 506  
507 -
508 -
509 -
510 -1.
511 -11.
512 -111. ​Decode payload in The Things Network
513 -
514 514  While using TTN network, you can add the payload format to decode the payload.
515 515  
516 516  
517 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
489 +[[image:1675144839454-913.png]]
518 518  
519 -PS-LB TTN Payload Decoder:
520 520  
521 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
492 +PS-LB TTN Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
522 522  
523 523  
524 -1.
525 -11. Uplink Interval
495 +== 2.4 Uplink Interval ==
526 526  
497 +
527 527  The PS-LB by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link:
528 528  
529 529  [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands#Change_Uplink_Interval>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands#Change_Uplink_Interval]]
530 530  
531 531  
503 +== 2.5 Show Data in DataCake IoT Server ==
532 532  
533 -1.
534 -11. ​Show Data in DataCake IoT Server
535 535  
536 536  [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
537 537  
538 538  
539 -**Step 1**: Be sure that your device is programmed and properly connected to the network at this time.
509 +**Step 1: **Be sure that your device is programmed and properly connected to the network at this time.
540 540  
541 -**Step 2**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:
511 +**Step 2:** To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:
542 542  
543 543  
544 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
514 +[[image:1675144951092-237.png]]
545 545  
546 546  
547 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
517 +[[image:1675144960452-126.png]]
548 548  
549 549  
550 -Step 3: Create an account or log in Datacake.
520 +**Step 3:** Create an account or log in Datacake.
551 551  
552 -Step 4: Create PS-LB product.
522 +**Step 4:** Create PS-LB product.
553 553  
554 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
524 +[[image:1675145004465-869.png]]
555 555  
556 556  
527 +[[image:1675145018212-853.png]]
557 557  
558 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
559 559  
560 560  
561 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
562 562  
532 +[[image:1675145029119-717.png]]
563 563  
564 -Step 5: add payload decode
565 565  
535 +**Step 5: **add payload decode
566 566  
567 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
537 +[[image:1675145051360-659.png]]
568 568  
569 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
570 570  
540 +[[image:1675145060812-420.png]]
571 571  
572 572  
543 +
573 573  After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
574 574  
575 575  
576 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
547 +[[image:1675145081239-376.png]]
577 577  
578 578  
550 +== 2.6 Frequency Plans ==
579 579  
580 580  
581 -
582 -
583 -
584 -
585 -
586 -
587 -
588 -
589 -
590 -
591 -
592 -
593 -
594 -1.
595 -11. Frequency Plans
596 -
597 597  The PS-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
598 598  
599 -
600 600  [[https:~~/~~/wiki.dragino.com/index.php?title=End_Device_Frequency_Band>>url:https://wiki.dragino.com/index.php?title=End_Device_Frequency_Band]]
601 601  
602 602  
... ... @@ -977,3 +977,4 @@
977 977  
978 978  [[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]]
979 979  
935 +
1675144504430-490.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +37.2 KB
Content
1675144608950-310.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.5 KB
Content
1675144839454-913.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
1675144951092-237.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.2 KB
Content
1675144960452-126.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +66.6 KB
Content
1675145004465-869.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +112.9 KB
Content
1675145018212-853.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +199.6 KB
Content
1675145029119-717.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.6 KB
Content
1675145051360-659.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +49.2 KB
Content
1675145060812-420.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 KB
Content
1675145081239-376.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0