Skip to Content
Last modified by Xiaoling on 2025/07/16 11:58
From version 114.1
edited by Mengting Qiu
on 2024/11/04 20:33
Change comment: There is no comment for this version
To version 115.1
edited by Mengting Qiu
on 2024/11/04 20:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -245,7 +245,6 @@
245 245  
246 246  [[image:image-20241104200506-7.png]]
247 247  
248 -
249 249  
250 250  Example in TTN:
251 251  
... ... @@ -259,7 +259,6 @@
259 259  
260 260  [[image:image-20241104200449-6.png]]
261 261  
262 -
263 263  
264 264  Example in TTN:
265 265  
... ... @@ -520,46 +520,10 @@
520 520  Downlink Payload: 05010101, Set AT+CFM=1 or 05000000 , set AT+CFM=1,1,1
521 521  
522 522  
523 -== 2.6 Datalog Feature ==
524 524  
522 +== 2.6 Set Device Time ==
525 525  
526 -Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, SE0X-LB will store the reading for future retrieving purposes.
527 527  
528 -
529 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
530 -
531 -
532 -Set PNACKMD=1, SE0X-LB will wait for ACK for every uplink, when there is no LoRaWAN network,SE0X-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
533 -
534 -* (((
535 -a) SE0X-LB will do an ACK check for data records sending to make sure every data arrive server.
536 -)))
537 -* (((
538 -b) SE0X-LB will send data in **CONFIRMED Mode** when PNACKMD=1, but SE0X-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if SE0X-LB gets a ACK, SE0X-LB will consider there is a network connection and resend all NONE-ACK messages.
539 -
540 -
541 -)))
542 -
543 -=== 2.6.2 Unix TimeStamp ===
544 -
545 -
546 -SE0X-LB uses Unix TimeStamp format based on
547 -
548 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220523001219-11.png?width=627&height=97&rev=1.1||alt="图片-20220523001219-11.png" height="97" width="627"]]
549 -
550 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
551 -
552 -Below is the converter example
553 -
554 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220523001219-12.png?width=720&height=298&rev=1.1||alt="图片-20220523001219-12.png" height="298" width="720"]]
555 -
556 -
557 -So, we can use AT+TIMESTAMP=1719999000 or downlink 3066851A1800 to set the current time 2024 – July ~-~- 3 Wednesday
558 -
559 -
560 -=== 2.6.3 Set Device Time ===
561 -
562 -
563 563  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
564 564  
565 565  Once SE0X-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to SE0X-LB. If SE01-LB fails to get the time from the server, SE0X-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
... ... @@ -567,96 +567,7 @@
567 567  (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
568 568  
569 569  
570 -=== 2.6.4 Datalog Uplink payload (FPORT~=3) ===
571 571  
572 -
573 -The Datalog uplinks will use below payload format.
574 -
575 -**Retrieval data payload:**
576 -
577 -(% style="color:blue" %)**MOD=0:**
578 -
579 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
580 -|=(% style="width: 56.66px; background-color: rgb(79, 129, 189); color: white;" %)(((
581 -**Size(bytes)**
582 -)))|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)2|=(% style="background-color: rgb(79, 129, 189); color: white; width: 56.66px;" %)2|=(% style="background-color: rgb(79, 129, 189); color: white; width: 56.66px;" %)2|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**4**
583 -|Value|Humidity|(((
584 -Temperature
585 -)))|Soil Conductivity (EC)|Humidity2|(% style="width:56.66px" %)(((
586 -Temperature2
587 -)))|(% style="width:56.66px" %)Soil Conductivity 2(EC)|(((
588 -datalog identifier
589 -)))|Unix Time Stamp
590 -
591 -(% style="color:blue" %)**MOD=1:**
592 -
593 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
594 -|=(% style="width: 56.66px; background-color: rgb(79, 129, 189); color: white;" %)(((
595 -**Size(bytes)**
596 -)))|=(% style="background-color:#4F81BD;color:white" %)2|=(% style="background-color:#4F81BD;color:white" %)2|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)2|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 56.66px;" %)**2**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 56.66px;" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**4**
597 -|Value|Bytes reserved, meaningless|raw water soil |Soil Conductivity (EC)|Bytes reserved, meaningless|(((
598 -raw water soil 2
599 -)))|(% style="width:56.66px" %)Soil Conductivity 2 (EC)|(% style="width:56.66px" %)datalog identifier|Unix Time Stamp
600 -
601 -(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
602 -
603 -* Poll Message Flag is set to 1.
604 -
605 -* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
606 -
607 -For example, in US915 band, the max payload for different DR is:
608 -
609 -(% style="color:blue" %)**a) DR0:**(%%) max is 11 bytes so one entry of data
610 -
611 -(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
612 -
613 -(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
614 -
615 -(% style="color:blue" %)**d) DR3:**(%%) total payload includes 22 entries of data.
616 -
617 -If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0   
618 -
619 -
620 -**Example:**
621 -
622 -If SE0X-LB has below data inside Flash:
623 -
624 -[[image:image-20240703190349-1.png||height="530" width="800"]]
625 -
626 -If user sends below downlink command: 316685282866852A8005
627 -
628 -Where : Start time: 66852828 = time 2024-07-03 10:30:00
629 -
630 - Stop time: 66852A80 = time 2024-07-03 10:40:00
631 -
632 -
633 -=== 2.6.5 Poll sensor value ===
634 -
635 -
636 -Users can poll sensor values based on timestamps. Below is the downlink command.
637 -
638 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:425.818px" %)
639 -|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
640 -|(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
641 -|(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
642 -
643 -(((
644 -Timestamp start and Timestamp end-use Unix TimeStamp format as mentioned above. Devices will reply with all data logs during this period, using the uplink interval.
645 -)))
646 -
647 -(((
648 -For example, downlink command [[image:image-20240703190533-2.png]]
649 -)))
650 -
651 -(((
652 -Is to check 2024-07-03 10:30:00 to 2024-07-03 10:40:00
653 -)))
654 -
655 -(((
656 -Uplink Internal =5s，means SE0X-LB will send one packet every 5s. range 5~~255s.
657 -)))
658 -
659 -
660 660  == 2.7 Frequency Plans ==
661 661  
662 662  
... ... @@ -849,6 +849,34 @@
849 849  
850 850  * Example 2: Downlink Payload: 0701F4  **~-~-->**  AT+5VT=500
851 851  
725 +
726 +=== 3.3.5 Setting the sensor address ===
727 +
728 +
729 +Function:Change the sensor address to 0x01, 0x02, 0x03, 0x04
730 +
731 +(% style="color:blue" %)**AT Command: AT+MADD**
732 +
733 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
734 +|=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response**
735 +|(% style="width:154px" %)AT+MADD=1|(% style="width:196px" %)Set sensor address to 01|(% style="width:157px" %)(((
736 +Successfully modified sensor address to 0x01
737 +
738 +
739 +OK
740 +)))
741 +|(% style="width:154px" %)AT+MADD=2|(% style="width:196px" %)Set sensor address to 02|(% style="width:157px" %)(((
742 +Successfully modified sensor address to 0x02
743 +
744 +
745 +OK
746 +)))
747 +
748 +(% style="color:blue" %)**Downlink Command: 0x**
749 +
750 +
751 +
752 +
852 852  = 4. Battery & Power Consumption =
853 853  
854 854