Skip to Content
Last modified by Mengting Qiu on 2025/07/03 15:42
From version 152.1
edited by Mengting Qiu
on 2025/05/16 10:37
Change comment: Uploaded new attachment "image-20250516103652-3.png", version {1}
To version 153.1
edited by Mengting Qiu
on 2025/05/16 11:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -682,16 +682,27 @@
682 682  
683 683  This is my configuration:
684 684  
685 -[[image:image-20250516100849-1.png]]
685 +[[image:image-20250516103205-2.png]]
686 686  
687 687  
688 -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.
688 +* 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.
689 +* 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)
690 +* AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
689 689  
690 -AT+COMMAND2=0M!,2,1,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)
691 691  
693 +This is the data obtained:
692 692  
695 +[[image:image-20250516103652-3.png]]
693 693  
694 694  
698 +When using the AT+DATACONVx command,
699 +
700 +The data of RETURN3 will be converted into 2 data, the first data is +101, and the second data is +263.
701 +
702 +* 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:
703 +
704 +
705 +
695 695  == 2.4 Uplink Payload ==
696 696  
697 697  === 2.4.1 Device Payload, FPORT~=5 ===