Changes for page General Manual for -CB , -CS models

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1011,9 +1011,26 @@
1011	1011
1012	1012	[[image:1750039871468-460.png||height="299" width="600"]]
1013	1013
1014		-(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1015		-=== MQTT: ===
	1014	+=== **MQTT Protocol:** ===
1016	1016
	1016	+Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
	1017	+
	1018	+//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
	1019	+
	1020	+* HEX format: **01000384**  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
	1021	+* JSON format: **{AT+TDC=900}       **~/~/ The correct format is **{AT Command}**. No extra characters other than valid AT commands can be added within {}.
	1022	+
	1023	+**Note:**
	1024	+
	1025	+**~1. Only when the correct and valid download command is used and the format is correct can the device be configured through the download command. Invalid download content cannot be processed by the device and will be automatically restarted.**
	1026	+
	1027	+**2. Devices designed with downlink commands can utilize different downlink formats (e.g., JSON or HEX) for configuration. However, regardless of the format, the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**
	1028	+
	1029	+**For example, the HEX-format downlink command corresponding to AT+TDC can only be used to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalent to AT+TDC=? , so querying TDC via downlink is not supported.**
	1030	+
	1031	+
	1032	+
	1033	+
1017	1017	Json：
1018	1018
1019	1019	The Json format in MQTT mode needs to be configured with all commands.