<
From version < 147.1 >
edited by Edwin Chen
on 2024/03/03 16:50
To version < 148.1 >
edited by Edwin Chen
on 2024/03/17 00:13
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -653,11 +653,13 @@
653 653  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
654 654  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.
655 655  
656 +
656 656  == 4.2 Why the uplink JSON format is not standard? ==
657 657  
658 -
659 659  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.
660 660  
661 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
662 +
661 661  [[image:image-20240229233154-1.png]]
662 662  
663 663  
... ... @@ -740,4 +740,3 @@
740 740  [[image:image-20240226111928-1.png]]
741 741  
742 742  
743 -
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0