<
From version < 27.1 >
edited by Xiaoling
on 2023/01/31 13:55
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.
... ... @@ -313,12 +313,9 @@
313 313  
314 314  
315 315  
316 +== 2.3 ​Uplink Payload ==
316 316  
317 317  
318 -
319 -1.
320 -11. ​Uplink Payload
321 -
322 322  Uplink payloads have two types:
323 323  
324 324  * Distance Value: Use FPORT=2
... ... @@ -327,27 +327,24 @@
327 327  The application server should parse the correct value based on FPORT settings.
328 328  
329 329  
327 +=== 2.3.1 Device Status, FPORT~=5 ===
330 330  
331 -1.
332 -11.
333 -111. Device Status, FPORT=5
334 334  
335 335  Include device configure status. Once PS-LB Joined the network, it will uplink this message to the server.
336 336  
337 -
338 338  Users can also use the downlink command(0x26 01) to ask PS-LB to resend this uplink.
339 339  
340 340  
335 +(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
341 341  |(% colspan="6" %)**Device Status (FPORT=5)**
342 -|**Size (bytes)**|**1**|**2**|**1**|**1**|**2**
343 -|**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
344 344  
345 345  Example parse in TTNv3
346 346  
347 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
342 +[[image:1675144504430-490.png]]
348 348  
349 349  
350 -
351 351  **Sensor Model**: For PS-LB, this value is 0x16
352 352  
353 353  **Firmware Version**: 0x0100, Means: v1.0.0 version
... ... @@ -401,33 +401,25 @@
401 401  Ex2: 0x0B49 = 2889mV
402 402  
403 403  
398 +=== 1.3.2 Sensor value, FPORT~=2 ===
404 404  
405 -1.
406 -11.
407 -111. Sensor value, FPORT=2
408 408  
409 409  Uplink payload includes in total 9 bytes.
410 410  
411 411  
412 -|(((
413 -**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]]
414 414  
415 -**(bytes)**
416 -)))|**2**|**2**|**2**|**2**|**1**
417 -|**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]]
418 418  
419 419  
420 420  
414 +=== 2.3.3 Battery Info ===
421 421  
422 422  
423 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
424 -
425 -
426 -
427 -1.
428 -11.
429 -111. Battery Info
430 -
431 431  Check the battery voltage for PS-LB.
432 432  
433 433  Ex1: 0x0B45 = 2885mV
... ... @@ -435,50 +435,45 @@
435 435  Ex2: 0x0B49 = 2889mV
436 436  
437 437  
438 -1.
439 -11.
440 -111. Probe Model
424 +=== 2.3.4 Probe Model ===
441 441  
426 +
442 442  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. 
443 443  
444 444  
445 445  For example.
446 446  
447 -|**Part Number**|**Probe Used**|**0~~20mA scale**|**Example: 10mA meaning**
448 -|PS-LB-I3|immersion type with 3 meters cable|0~~3 meters|1.5 meters pure water
449 -|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
450 450  
451 451  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.
452 452  
453 453  
454 -1.
455 -11.
456 -111. 0~~20mA value (IDC_IN)
440 +=== 2.3.5 0~~20mA value (IDC_IN) ===
457 457  
442 +
458 458  The output value from Pressure Probe, use together with Probe Model to get the pressure value or water level.
459 459  
460 -
461 461  **Example**:
462 462  
463 463  27AE(H) = 10158 (D)/1000 = 10.158mA.
464 464  
465 465  
466 -1.
467 -11.
468 -111. 0~~30V value ( pin VDC_IN)
450 +=== 2.3.6 0~~30V value ( pin VDC_IN) ===
469 469  
452 +
470 470  Measure the voltage value. The range is 0 to 30V.
471 471  
472 -
473 473  **Example**:
474 474  
475 475  138E(H) = 5006(D)/1000= 5.006V
476 476  
477 477  
478 -1.
479 -11.
480 -111. IN1&IN2&INT pin
460 +=== 2.3.7 IN1&IN2&INT pin ===
481 481  
462 +
482 482  IN1 and IN2 are used as digital input pins.
483 483  
484 484  **Example**:
... ... @@ -488,10 +488,8 @@
488 488  09 (H) :(0x09&0x04)>>2=0    IN2 pin is low level.
489 489  
490 490  
491 -
492 492  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.
493 493  
494 -
495 495  **Example:**
496 496  
497 497  09 (H) : (0x09&0x02)>>1=1    The level of the interrupt pin.
... ... @@ -501,101 +501,78 @@
501 501  0x01: Interrupt Uplink Packet.
502 502  
503 503  
483 +=== 2.3.8 ​Decode payload in The Things Network ===
504 504  
505 505  
506 -
507 -
508 -
509 -1.
510 -11.
511 -111. ​Decode payload in The Things Network
512 -
513 513  While using TTN network, you can add the payload format to decode the payload.
514 514  
515 515  
516 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
489 +[[image:1675144839454-913.png]]
517 517  
518 -PS-LB TTN Payload Decoder:
519 519  
520 -[[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]]
521 521  
522 522  
523 -1.
524 -11. Uplink Interval
495 +== 2.4 Uplink Interval ==
525 525  
497 +
526 526  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:
527 527  
528 528  [[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]]
529 529  
530 530  
503 +== 2.5 Show Data in DataCake IoT Server ==
531 531  
532 -1.
533 -11. ​Show Data in DataCake IoT Server
534 534  
535 535  [[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:
536 536  
537 537  
538 -**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.
539 539  
540 -**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:
541 541  
542 542  
543 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
514 +[[image:1675144951092-237.png]]
544 544  
545 545  
546 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
517 +[[image:1675144960452-126.png]]
547 547  
548 548  
549 -Step 3: Create an account or log in Datacake.
520 +**Step 3:** Create an account or log in Datacake.
550 550  
551 -Step 4: Create PS-LB product.
522 +**Step 4:** Create PS-LB product.
552 552  
553 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
524 +[[image:1675145004465-869.png]]
554 554  
555 555  
527 +[[image:1675145018212-853.png]]
556 556  
557 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
558 558  
559 559  
560 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
561 561  
532 +[[image:1675145029119-717.png]]
562 562  
563 -Step 5: add payload decode
564 564  
535 +**Step 5: **add payload decode
565 565  
566 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
537 +[[image:1675145051360-659.png]]
567 567  
568 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
569 569  
540 +[[image:1675145060812-420.png]]
570 570  
571 571  
543 +
572 572  After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
573 573  
574 574  
575 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
547 +[[image:1675145081239-376.png]]
576 576  
577 577  
550 +== 2.6 Frequency Plans ==
578 578  
579 579  
580 -
581 -
582 -
583 -
584 -
585 -
586 -
587 -
588 -
589 -
590 -
591 -
592 -
593 -1.
594 -11. Frequency Plans
595 -
596 596  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.
597 597  
598 -
599 599  [[https:~~/~~/wiki.dragino.com/index.php?title=End_Device_Frequency_Band>>url:https://wiki.dragino.com/index.php?title=End_Device_Frequency_Band]]
600 600  
601 601  
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