diff --git a/docs/API_reference/en/iotlib/sim.md b/docs/API_reference/en/iotlib/sim.md index 650a094a5d5aa3926958b607d85e4cf0ac2467f6..a6705a2b1ad67d6df6f4c8401183f6e11c459fa2 100644 --- a/docs/API_reference/en/iotlib/sim.md +++ b/docs/API_reference/en/iotlib/sim.md @@ -1,8 +1,8 @@ # sim - SIM Card Related Features -This feature provides you with the SIM Card APIs, such as the methods of getting SIM card status, ICCID, IMSI and the phone number. +This feature provides you with the SIM Card APIs, such as the methods of getting SIM card status, ICCID, IMSI and the phone number, etc. -> The IMSI, ICCID, and phone number can be gotten only when the SIM card status is 1. You can call *sim.getstatus()* to get the current SIM card status. +> To obtain the SIM card ICCID and IMSI, the SIM card status needs to be in the ready state (which can be queried through sim. getStatus()).The PIN code, PUK code, and other related passwords involved in this module should be obtained based on the information provided by the network operator. If you are unsure of the password, please confirm with the network operator first @@ -29,7 +29,7 @@ A tuple `(len,data)` - Successful execution `data` - String type. The data content returned. -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -59,9 +59,9 @@ Gets the IMSI number of the SIM card. **Return Value** -`IMSI` - Successful execution +`IMSI` -Successful execution,String type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -83,9 +83,9 @@ Gets the ICCID number of the SIM card. **Return Value** -`ICCID` - Successful execution +`ICCID` - Successful execution,String type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -107,9 +107,9 @@ Gets the phone number of the SIM card. The phone number of the SIM card must be **Return Value** -`Phone number` - Successful execution +`Phone number` - Successful execution,String type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. >BC25 series module does not support this method. @@ -137,7 +137,7 @@ Gets the current SIM card status. **Return Value** -String type. SIM card status codes, as described in details below. +Integer type. SIM card status codes, as described in details below. | Code | Description | | ---- | ------------------------------------------------------------ | @@ -182,9 +182,9 @@ Enables PIN verification. Once this method is called to enable the PIN verificat **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -209,9 +209,9 @@ Disables PIN code verification. **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -237,9 +237,9 @@ Verifies PIN code. After the PIN code verification is enabled, if you need to us **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -266,9 +266,9 @@ Changes the PIN code **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -297,9 +297,9 @@ Unblocks the SIM card. When you enter incorrect PIN codes three times, you need **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -361,7 +361,7 @@ The parameters are described below. | `username` | String | Username of the phone number. | | `phone_number` | String | Phone number. | -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -405,9 +405,9 @@ Writes phone book, that is, write a phone record to the specified storage locati **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1`- Failed execution +`-1`- Failed execution,Integer type. @@ -447,9 +447,9 @@ Sets the hot-swap-related features of the SIM card. **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -496,7 +496,7 @@ The parameters are described below. | `detenable` | Integer | Enable or disable the hot swap feature of the SIM card. 0 - Disable; 1 - Enable. | | `insertlevel` | Integer | High level or low level (0/1). | -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -538,11 +538,11 @@ Gets the SIM card slot ID of the current SIM card. `simId` - Successful execution -`0` - `SIM1` +`0` - `SIM1`,Integer type. -`1` - `SIM2` +`1` - `SIM2,Integer ` type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -568,7 +568,7 @@ Gets the SIM card slot ID of the current SIM card. sim.switchCard(simId) ``` -Switches the SIM card. +This method is used to switch SIM cards between SIM cards. **Parameter** @@ -580,9 +580,9 @@ Switches the SIM card. **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -631,9 +631,9 @@ def usrFun(args): **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -688,8 +688,8 @@ def usrFun(args): **Return Value** -`0` - Successful execution -`-1` - Failed execution +`0` - Successful execution,Integer type. +`-1` - Failed execution,Integer type. > The modules that support this method are as follows: > diff --git a/docs/API_reference/en/iotlib/sms.md b/docs/API_reference/en/iotlib/sms.md index e06b1efb3851d6f7936bb1478a55408f36cb72cd..ccf6076172a1d650e050c2100a47ecd7e80ab7c7 100644 --- a/docs/API_reference/en/iotlib/sms.md +++ b/docs/API_reference/en/iotlib/sms.md @@ -2,9 +2,17 @@ This feature provides methods of reading, sending and deleting SMS. - - -> BC25/EC600M series module does not support this feature. +> The BC25/EC600M/EC600K/EC800K/EC800M/EG810M/EC600G/EC800G/EG700G series does not support this feature. +> +> For special instructions that do not support series: +> +> For the EC600M series: EC600MCN_ LA_ VOLTE/EC600MCN_ LE_ VOLTE supports this module function. +> +> For the EG810M series: EG810MCN_ GA_ VOLTE supports this module function. +> +> For the EC600G series: EC600GCN_ LA supports this module function. +> +> For the EC800G series: EC800GCN_GA supports this module function. @@ -31,17 +39,19 @@ Sends a text message (Empty messages are not supported). **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. > Only the following series modules support long messages. > -> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC800M/EG810M/EC200A series module supports six normal messages. +> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC600M/EC200A series SMS content UCS2 encoding supports up to 420 bytes, and GSM encoding supports up to 960 bytes in length. +> +> The EC200U/EC600U/EG912U/EG915U series SMS content supports UCS2 encoding up to 280 bytes, while GSM encoding supports a maximum SMS length of 640 bytes. > -> EC200U/EC600U/EG912U/EG915/EC600G/EC800G series module supports four normal messages. +> The UCS2 encoding of other series of SMS content supports a maximum of 70 bytes, while the GSM encoding supports a maximum of 160 bytes of SMS length. @@ -87,9 +97,13 @@ Sends an SMS message in PDU mode (Empty messages are not supported). > Only the following series modules support long messages. > -> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC600M/EC800M/EG810M/EC200A series module supports six normal messages. +> > EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC600M/EC200A series SMS content UCS2 encoding supports up to 420 bytes, and GSM encoding supports up to 960 bytes in length. +> > +> > The EC200U/EC600U/EG912U/EG915U series SMS content supports UCS2 encoding up to 280 bytes, while GSM encoding supports a maximum SMS length of 640 bytes. +> > +> > The UCS2 encoding of other series of SMS content supports a maximum of 70 bytes, while the GSM encoding supports a maximum of 160 bytes of SMS length. > -> EC200U/EC600U/EG912U/EG915/EC600G/EC800G series module supports four normal messages. +> @@ -128,13 +142,13 @@ Deletes the message for the specified index. **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. -> BC25/EC800G series module does not support `delmode`. +> The EC600G/EC800G series only supports SMS. deleteMsg (index) method calls and does not support SMS. deleteMsg (index, delmode) method calls. @@ -176,9 +190,9 @@ Sets SMS message storage location. **Return Value** -`0` - Successful execution +`0` - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. @@ -220,7 +234,7 @@ A tuple`([loc1, current_nums, max_nums],[loc2, current_nums, max_nums],[loc3, cu | `current_nums` | Integer | Current number of SMS messages. | | `max_nums` | Integer | The maximum number of SMS message storages. | -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -247,9 +261,9 @@ Gets the number of SMS messages. **Return Value** -The number of SMS messages - Successful execution +The number of SMS messages - Successful execution,Integer type. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -277,11 +291,11 @@ Gets an SMS message content in PDU mode. **Return Value** -Message content in PDU mode - Successful execution +Message content in PDU mode - Successful execution,String -The SMS message content includes the time when the SMS message is received. Therefore, the PDU data of the same SMS message content is different. +type. The SMS message content includes the time when the SMS message is received. Therefore, the PDU data of the same SMS message content is different. -`-1` - Failed execution +`-1` - Failed execution,Integer type. **Example** @@ -316,7 +330,7 @@ A tuple`(phoneNumber, msg, msgLen)` - Successful execution | `msg` | String | Message content. | | `msgLen` | Integer | Length of the message content. Unit: byte. | -`-1` - Failed execution +`-1` - Failed execution, Integer type. **Example** @@ -345,9 +359,9 @@ Gets the length of the specified SMS message in PDU mode. **Return Value** -Length of an SMS message in PDU mode - Successful execution +Length of an SMS message in PDU mode - Successful execution, Integer type. -`-1` - Failed execution +`-1` - Failed execution, Integer type. **Example** @@ -386,7 +400,7 @@ A tuple `(phoneNumber, msg, time, msgLen)` - Successful execution | `time` | Integer | Time for receiving the SMS message | | `msgLen` | Integer | Length of the SMS message | -`-1` - Failed execution +`-1` - Failed execution, Integer type. **Example** @@ -411,9 +425,9 @@ Gets the SMS center number. **Return Value** -SMS center number - Successful execution +SMS center number - Successful execution,String type. -`-1` - Failed execution +`-1` - Failed execution, Integer type. **Example** @@ -443,9 +457,9 @@ Sets the SMS center number (It is not recommended to change the SMS center numbe **Return Value** -`0` - Successful execution +`0` - Successful execution,String type. -`-1` - Failed execution +`-1` - Failed execution, Integer type. @@ -476,9 +490,9 @@ def usrFun(args): **Return Value** -`0` - Successful execution +`0` - Successful execution, Integer type. -`-1` - Failed execution +`-1` - Failed execution, Integer type. **Example** diff --git a/docs/API_reference/zh/iotlib/sim.md b/docs/API_reference/zh/iotlib/sim.md index 18a33f228b36f9c27ce695001b457c42e73d51ee..73cf6fbd2a73ba59c4388161b78a5b2e02dcde4f 100644 --- a/docs/API_reference/zh/iotlib/sim.md +++ b/docs/API_reference/zh/iotlib/sim.md @@ -1,10 +1,10 @@ # sim - SIM卡功能 -该模块提供sim卡相关功能的接口,如查询sim卡状态、iccid、imsi、电话号码等。 +该模块提供sim卡相关功能的接口,如查询sim卡状态、ICCID、IMSI、电话号码等。 -> 能成功获取IMSI、ICCID、电话号码的前提是SIM卡状态为1,可通过sim.getStatus()查询。 +> 获取SIM卡ICCID,IMSI时需要SIM卡状态为就绪状态(可通过sim.getStatus()查询状态)。此模块涉及到的PIN码、PUK码等一些列密码的获取请以运营商提供的为准,如果有密码不确定,请和运营商先进行确定。 @@ -475,7 +475,7 @@ sim.getSimDet() | `detenable` | 整型 | 开启或者关闭SIM卡热插拔功能,0:关闭 ,1:打开 | | `insertlevel` | 整型 | 高低电平配置(0/1) | -失败: 返回`-1`。 +失败: 返回`-1`,整型。 @@ -517,9 +517,9 @@ sim.getCurSimid() **返回值描述:** -成功: 返回当前`simId`(`0`或`1`,分别表示`SIM1`或者`SIM2`)。 +成功: 返回当前`simId`(`0`或`1`,分别表示`SIM1`或者`SIM2`),整型。 -失败: 返回`-1`。 +失败: 返回`-1`,整型。 diff --git a/docs/API_reference/zh/iotlib/sms.md b/docs/API_reference/zh/iotlib/sms.md index 587d4fa67527f065836e94452a2e0e7b576bf4ad..43a0bb5f394536678e50d0b172e3a9b1993cfcc3 100644 --- a/docs/API_reference/zh/iotlib/sms.md +++ b/docs/API_reference/zh/iotlib/sms.md @@ -2,9 +2,17 @@ 该模块提供短信功能相关方法,包括读取、发送、删除短信等方法。 - - -> BC25/EC600M系列不支持此功能。 +> BC25/EC600M/EC600K/EC800K /EC800M/EG810M/EC600G/EC700G/EC800G系列不支持此功能。 +> +> 对于不支持系列特殊说明: +> +> 对于EC600M系列:EC600MCN_LA_VOLTE/EC600MCN_LE_VOLTE支持此模块功能。 +> +> 对于EG810M系列:EG810MCN_GA_VOLTE支持此模块功能。 +> +> 对于EC600G系列:EC600GCN_LA支持此模块功能。 +> +> 对于EC800G系列:EC800GCN_GA支持此模块功能。 @@ -37,11 +45,11 @@ sms.sendTextMsg(phoneNumber, msg, codeMode) > 仅以下系列支持长短信: > -> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC800M/EG810M/EC200A系列支持6条正常短信长度; +> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC600M/EC200A系列短信内容UCS2编码最多支持420字节,GSM编码最多支持960个字节长度。 > -> EC200U/EC600U/EG912U/EG915/EC600G/EC800G系列支持4条正常短信长度。 - - +> EC200U/EC600U/EG912U/EG915U系列短信内容UCS2编码最多支持280个字节,GSM编码最多支持640个字节的短信长度。 +> +> 其余系列短信内容UCS2编码最多支持70个字节,GSM编码最多支持160个字节的短信长度。 **示例:** @@ -83,9 +91,11 @@ sms.sendPduMsg(phoneNumber, msg, codeMode) > 仅以下系列支持长短信: > -> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC600M/EC800M/EG810M/EC200A系列支持6条正常短信长度; +> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC600M/EC200A系列短信内容UCS2编码最多支持420字节,GSM编码最多支持960个字节长度。 +> +> EC200U/EC600U/EG912U/EG915U系列短信内容UCS2编码最多支持280个字节,GSM编码最多支持640个字节的短信长度。 > -> EC200U/EC600U/EG912U/EG915/EC600G/EC800G系列支持4条正常短信长度。 +> 其余系列短信内容UCS2编码最多支持70个字节,GSM编码最多支持160个字节的短信长度。 @@ -128,7 +138,7 @@ sms.deleteMsg(index [, delmode]) -> BC25/EC800G不支持可选参数的使用 +> EC600G/EC800G系列仅支持sms.deleteMsg(index)方式调用,不支持sms.deleteMsg(index,delmode)方式调用。 @@ -176,7 +186,7 @@ sms.setSaveLoc(mem1, mem2, mem3) > 不同系列短信默认存储空间有差异,用户根据自己的需求进行设置。 > -> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC800M/EG810M/EC200A系列如果要改变接收消息的存储位置,需要同时设定mem2 & mem3;EC200U/EC600U/EG912U/EG915U/EC600G/EC800G系列只需设定mem3即可 +> EC100Y/EC200N/EC600N/EC600S/EC800N/EG912N/EG915N/EC800M/EG810M/EC200A系列如果要改变接收消息的存储位置,需要同时设定mem2 & mem3。EC200U/EC600U/EG912U/EG915U/EC600G/EC800G系列只需设定mem3即可。 diff --git a/docs/Application_guide/en/media/network-comm/esim/8-4.png b/docs/Application_guide/en/media/network-comm/esim/8-4.png index 83518c3f936c64a4d768d4ee41cdf4cb7bbcff9c..f0f63e9136247b7178fc8e05a6f7fb0743b9b719 100644 Binary files a/docs/Application_guide/en/media/network-comm/esim/8-4.png and b/docs/Application_guide/en/media/network-comm/esim/8-4.png differ diff --git "a/docs/Application_guide/en/media/network-comm/sim/QPYcom\346\211\223\345\274\200REPL.png" "b/docs/Application_guide/en/media/network-comm/sim/QPYcom\346\211\223\345\274\200REPL.png" index 245b23d28701d23c3fa4fc9eb7a2b28a3466a768..c77f467746480d42c75756f53c806d40a8475bb2 100644 Binary files "a/docs/Application_guide/en/media/network-comm/sim/QPYcom\346\211\223\345\274\200REPL.png" and "b/docs/Application_guide/en/media/network-comm/sim/QPYcom\346\211\223\345\274\200REPL.png" differ diff --git "a/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PIN-PUK\347\240\201\344\275\215\347\275\256.png" "b/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PIN-PUK\347\240\201\344\275\215\347\275\256.png" index 35bf3d1b54758cb01ac19ae5382db09af5da7b69..ab303aabdfbb24118c60872678ddc98eacd96aac 100644 Binary files "a/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PIN-PUK\347\240\201\344\275\215\347\275\256.png" and "b/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PIN-PUK\347\240\201\344\275\215\347\275\256.png" differ diff --git "a/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PUK\347\240\201\344\275\215\347\275\256.png" "b/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PUK\347\240\201\344\275\215\347\275\256.png" index 90981886b28104d58324f021229355aeefdede83..454c5104e57fd21b11a20913863668b65223ae15 100644 Binary files "a/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PUK\347\240\201\344\275\215\347\275\256.png" and "b/docs/Application_guide/en/media/network-comm/sim/SIM\345\215\241PUK\347\240\201\344\275\215\347\275\256.png" differ diff --git a/docs/Application_guide/en/media/system/Timer/2-1.png b/docs/Application_guide/en/media/system/Timer/2-1.png index e7c7cc0398ebae190db35f727e65f7fd5b99d90c..e316145e84a36df0701e7452988f86a1162a217b 100644 Binary files a/docs/Application_guide/en/media/system/Timer/2-1.png and b/docs/Application_guide/en/media/system/Timer/2-1.png differ diff --git a/docs/Application_guide/en/network-comm/esim/README.md b/docs/Application_guide/en/network-comm/esim/README.md index 2c4921bc575cc3bd3a9738de8d6447f9fcfd4fca..6012120ad0710ffbabce1d4308589845144ceb47 100644 --- a/docs/Application_guide/en/network-comm/esim/README.md +++ b/docs/Application_guide/en/network-comm/esim/README.md @@ -130,6 +130,8 @@ The specific models currently supported by QuecPython for eSIM functionality are + + ## eSIM Tool ### Tool Introduction @@ -138,7 +140,7 @@ The QEsimTool software is mainly used to handle the situation of an empty eSIM c The operating mechanism of the QEsimTool software: The user obtains the AccCode from the operator, and passes the AccCode as a parameter to QEsimTool. QEsimTool resolves the operator's server address through the AccCode and sends a request to the operator's server to download profile data. After QEsimTool completes the download of profile data, it will send the data to the device through AT commands, and then write the profile into the eSIM card. -How to obtain the QEsimTool software: Please go to the [Quectel Official Website](https://www.quectel.com/) and contact customer service to obtain it. +How to obtain the QEsimTool software: Please go to the [Download](https://images.quectel.com/python/2023/11/QEsimTool_V1.0.1.7.zip) and contact customer service to obtain it. ### Interface Introduction diff --git a/docs/Application_guide/en/network-comm/sim/SIM-card-terminology.md b/docs/Application_guide/en/network-comm/sim/SIM-card-terminology.md index eab42dd5437426ea00db94c2956b0cf21e495f7c..1209ff1cd915acd463daf0f73923b359ca886c14 100644 --- a/docs/Application_guide/en/network-comm/sim/SIM-card-terminology.md +++ b/docs/Application_guide/en/network-comm/sim/SIM-card-terminology.md @@ -85,7 +85,7 @@ The SIM card stores the Home PLMN (HPLMN), which is used for the UE to search fo | UPLMN | User-controlled PLMN, a parameter related to PLMN selection stored on the USIM card. | | OPLMN | Operator-controlled PLMN, a parameter related to PLMN selection stored on the USIM card. | | FPLMN | Forbidden PLMN, when a terminal is denied access to a certain PLMN, it will add it to the FPLMN list. | -| VPLMN | Visited PLMN, when the terminal is not within the coverage of its corresponding operator network, the terminal may choose the network of another operator, which is the VPLMN. Currently, the premise is that the terminal and its USIM card support roaming. | +| VPLMN | Visited PLMN, when the terminal is not within the coverage of its corresponding operator network, the terminal may choose the network of another operator, which is the VPLMN. Of course, the premise is that the terminal and its USIM card support roaming. | diff --git a/docs/Application_guide/en/network-comm/sms.md b/docs/Application_guide/en/network-comm/sms.md index cf732de022d1232daa433795d593bdfac819c075..b7d06cc3e2c42efa83b8171fef7280b8daf05609 100644 --- a/docs/Application_guide/en/network-comm/sms.md +++ b/docs/Application_guide/en/network-comm/sms.md @@ -101,7 +101,7 @@ SMS can be divided into TEXT SMS, PDU SMS, and block SMS. TEXT SMS is simple and #### TEXT SMS -When sending a TEXT SMS using the QuecPython interface, there is no need to split and combine the TEXT SMS content for sending. You only need to write the content directly. If the SMS content exceeds 140 bytes, the QuecPython module will automatically convert it into multiple SMS messages and send them (Table 3-1 indicates that the maximum number of supported SMS messages is greater than 1). +When sending a TEXT SMS using the QuecPython interface, there is no need to split and combine the TEXT SMS content for sending. You only need to write the content directly. If the SMS content exceeds 140 bytes, the QuecPython module will automatically convert it into multiple SMS messages and send them (When the supported SMS content is marked as larger than 140 bytes in Table 3-1). When sending SMS messages, the entered data are all ASCII codes, and ASCII codes are 8-bit character data. GSM encoding is 7-bit character data. In TEXT mode, GSM encoding data needs to ensure that the 7-bit data values are exactly the same as the values in the ASCII code table in order to send a message data through the TEXT, otherwise it will cause inconsistency between the received and transmitted data. @@ -732,7 +732,7 @@ sms.setSaveLoc(save_info[0][0],save_info[1][0],save_info[2][0]) ### Send SMS -The QuecPython SMS sending interface is convenient to use. You only need to input the recipient's phone number, SMS content, and select the encoding method, and then call the interface directly. This feature is divided into two interfaces: sending TEXT messages and sending PDU messages. The interface style and parameters are the same. If the SMS content exceeds 140 bytes, the QuecPython underlying system will automatically convert it into a long SMS and send it in multiple messages (when the maximum number of supported SMS is greater than 1 in Table 3-1). The receiving end needs to read it in PDU format and parse the sequence number of each sub-message of this long SMS in order to merge them into one message and display it normally. Otherwise, this long SMS will be split into multiple messages on the receiving end. +The QuecPython SMS sending interface is convenient to use. You only need to input the recipient's phone number, SMS content, and select the encoding method, and then call the interface directly. This feature is divided into two interfaces: sending TEXT messages and sending PDU messages. The interface style and parameters are the same. If the SMS content exceeds 140 bytes, the QuecPython underlying system will automatically convert it into a long SMS and send it in multiple messages (When the supported SMS content is marked as larger than 140 bytes in Table 3-1). The receiving end needs to read it in PDU format and parse the sequence number of each sub-message of this long SMS in order to merge them into one message and display it normally. Otherwise, this long SMS will be split into multiple messages on the receiving end. #### Send TEXT Message @@ -761,7 +761,7 @@ sms.sendTextMsg('18158626517', data , 'GSM') #### Send PDU Message -When sending a PDU message, if the SMS content length exceeds 140 bytes, it will be automatically split into multiple messages and sent as a long SMS (when the maximum number of supported SMS is greater than 1 in Table 3-1). +When sending a PDU message, if the SMS content length exceeds 140 bytes, it will be automatically split into multiple messages and sent as a long SMS (When the supported SMS content is marked as larger than 140 bytes in Table 3-1). The interface is as follows: diff --git a/docs/Application_guide/en/system/Timer.md b/docs/Application_guide/en/system/Timer.md index dec43fb63775c488a90b5ab174215f91ffc594db..c260bd87d4e6c05c2956744d0951d0f1d620a182 100644 --- a/docs/Application_guide/en/system/Timer.md +++ b/docs/Application_guide/en/system/Timer.md @@ -377,7 +377,7 @@ if __name__ == "__main__": QuecPython module provides an application-level timer interface. When the timer expires, the callback function bound to the timer will be triggered. It is not recommended to perform blocking or time-consuming operations in the callback function, as it will affect overall performance. It is recommended to only send messages in the callback function and process the business logic in other tasks. The time precision is shown in Table 3-1. The general timer only supports the creation of up to four timers. It can be used in single mode or cyclic mode. - Table 3-2 +