Skip to Content
Last modified by Mengting Qiu on 2025/07/03 15:42
From version 170.1
edited by Mengting Qiu
on 2025/06/09 13:49
Change comment: Uploaded new attachment "image-20250609134901-2.png", version {1}
To version 171.2
edited by Mengting Qiu
on 2025/06/09 14:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -711,21 +711,21 @@
711 711  * Example 2: Downlink Payload: AC 02 01 02 02 02 03 02  ~/~/  AT+DATACONV2=1,2+2,2+3,2
712 712  
713 713  
714 -
715 715  **For example:**
716 716  
717 717  This is my configuration:
718 718  
719 -[[image:image-20250605091006-1.png]]
718 +[[image:image-20250609134137-1.png]]
720 720  
721 721  
722 722  * AT+COMMAND1=0C!,0,2,0  After sending the concurrent command of device 0, the data will not be cut, and the next command will be sent immediately.
723 -* AT+COMMAND2=0M!,1,2,0  After sending the concurrent command of device 0, do not cut the data and wait for one second. (The last concurrent command needs to wait for the measurement time of all sensors)
724 -* AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
722 +* AT+COMMAND2=1C!,1,2,0  After sending a concurrent command to device 1, do not truncate the data and wait for one second. (Concurrent commands will be sampled with the command with the longest waiting time; for example, if the waiting time in the current device is set to 1s, the concurrent command will default to a maximum waiting time of 1s.)
723 +* AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
724 +* AT+COMMAND4=1D0!,0,0,0  Query the data measured by device 1
725 725  
726 726  This is the data obtained:
727 727  
728 -[[image:image-20250516145402-2.png]]
728 +[[image:image-20250609134901-2.png]]
729 729  
730 730  
731 731  When using the AT+DATACONVx command,
... ... @@ -733,20 +733,31 @@
733 733  The data of RETURN3 will be converted into 2 data, the first data is +95, and the second data is +260.
734 734  
735 735  * AT+DATACONV3=1,2+2,2  The first data is uploaded as 2 bytes and the second data is uploaded as 2 bytes. The form converted to hexadecimal is as shown above,as below:
736 +* (((
737 +AT+DATACONV4=1,3+2,2+3,2  The first data uploads 3 bytes, the second data also uploads 2 bytes, and the third data also uploads 2 bytes. The hexadecimal form is shown above and as shown in the following figure:
738 +)))
736 736  
737 -[[image:image-20250516144559-1.png]]
740 +[[image:image-20250609141343-1.png]]
738 738  
739 -0C90 01 005F 0104
742 +**For example,the uplink payload as below:**
740 740  
741 -(% style="color:#037691" %)**BAT**(%%): 0x0c90 = 3216mV = 3.216V
744 +0CE4 01 00C6 0103 02DB99 00FD 0001
742 742  
746 +(% style="color:#037691" %)**BAT**(%%): 0x0CE4 = 3300mV = 3.300V
747 +
743 743  (% style="color:#037691" %)**Payload Version**(%%): 0x01, Means: v1.0 version
744 744  
745 -(% style="color:#037691" %)**Data 1: **(%%)0x005F(H) = 95(D) / 100 = 0.95
750 +(% style="color:#037691" %)**Data 1: **(%%)0x00C6(H) = 198(D) / 100 = 19.8
746 746  
747 -(% style="color:#037691" %)**Data 2: **(%%)0x0104(H) = 260(D) / 10 = 26.0
752 +(% style="color:#037691" %)**Data 2: **(%%)0x0103(H) = 259(D) / 10 = 25.9
748 748  
754 +(% style="color:#037691" %)**Data 3: **(%%)0x02DB99(H) = 187289(D) / 100 = 1872.89
749 749  
756 +(% style="color:#037691" %)**Data 4: **(%%)0x00FD(H) = 253(D) / 10 = 25.3
757 +
758 +(% style="color:#037691" %)**Data 5: **(%%)0x0001(H) = 1(D) = 1
759 +
760 +
750 750  == 2.4 Uplink Payload ==
751 751  
752 752  === 2.4.1 Device Payload, FPORT~=5 ===
image-20250609141343-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content