Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 145.1
edited by Edwin Chen
on 2024/02/29 23:34
Change comment: There is no comment for this version
To version 144.1
edited by Edwin Chen
on 2024/02/29 23:32
Change comment: Uploaded new attachment "image-20240229233154-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -643,15 +643,6 @@
643 643  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
644 644  1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn;t lost 6 continue data. There will not data lost.
645 645  
646 -
647 -== 4.2 Why the uplink JSON format is not standard? ==
648 -
649 -The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
650 -
651 -[[image:image-20240229233154-1.png]]
652 -
653 -
654 -
655 655  = 5. Trouble Shooting: =
656 656  
657 657  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==