diff --git a/docs/Application_guide/en/network-comm/nic/cellular/api-instruction.md b/docs/Application_guide/en/network-comm/nic/cellular/api-instruction.md index fb6495dcace2c2bcf29f119570ba902d5e6ac3b3..ba7c1769c82131b344bf02562afd2ed83acbddb0 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/api-instruction.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/api-instruction.md @@ -60,7 +60,7 @@ You can call the above functions to get and set the parameters of the NIC in the * Some special SIM cards require APN configuration before successful network registration. In this case, you need to confirm with the operator what APN, username, and password should be used for this card, and then call *dataCall.setPDPContext()* to configure the APN information for the cellular NIC, and finally reboot the module. -* When you need to activate multiple cellular NICs at the same time and use different NICs to connect to different networks, such as making the first data call to access the public network and the second data call to access a specific network. You need to call `dataCall.setPDPContext` to configure the corresponding APN information for the first and second data calls of NICs. +* When you need to activate multiple cellular NICs at the same time and use different NICs to connect to different networks, for example, the first NIC is used to access the public network, and the second NIC is used to access a private network. You need to call `dataCall.setPDPContext` to configure the corresponding APN information for the first and second NICs. For how to configure APN, please refer to the following sections in the *Scenario Instructions* chapter, which provide detailed APN configuration examples: @@ -94,7 +94,7 @@ dataCall.deactivate(profileID) By default, QuecPython modules automatically activate cellular NICs at startup, so in most cases, you do not need to manually activate or deactivate cellular NICs. However, in some special scenarios or for specific requirements, it is necessary to manually activate or deactivate cellular NICs by using the above functions. -If you disable the automatic activation of cellular NICs at startup and set a program to activate and deactivate NICs based on needs at a certain time, you need to call `dataCall.activate` and `dataCall.deactivate` in the program accordingly. For example, some electricity meters do not need to establish a network connection during normal operation. They only activate the NIC when they need to report meter data and deactivate the NIC after the data is reported to disconnect from the network, thus saving data usage and reducing device power consumption. +If you disable the automatic activation of cellular NICs at startup and set a program to activate and deactivate NICs based on needs at a certain time, you need to call `dataCall.activate` and `dataCall.deactivate` in the program accordingly. For example, some electricity meters do not need to establish a network connection most of the time. Only when the electricity meter data needs to be reported, the NICs will be activated. When the data reporting is completed, the NICs will be deactivated and the network connection will be disconnected. This not only saves SIM card traffic, but also reduces the power consumption of the device. For how to manually activate NICs, please refer to the following sections in the *Scenario Instructions* chapter, which provide detailed APN configuration examples: @@ -131,7 +131,7 @@ dataCall.getInfo(profileID, ipType) ### Application Scenarios -It is necessary for you to get NIC status information. Regardless of the application scenario, as long as you need to perform network-related operations., you must first get the activation status of the NIC to confirm that the cellular NIC has been activated successfully. Specifically, you can call the above function to get the NIC status information in the following scenarios: +It is necessary for you to get NIC status information. Regardless of the application scenario, as long as you need to perform network-related operations, you must first get the activation status of the NIC to confirm that the cellular NIC has been activated successfully. Specifically, you can call the above function to get the NIC status information in the following scenarios: * Confirm whether the cellular NIC has been activated successfully by checking the `state` value in the returned tuple of `dataCall.getInfo`. 1 indicates successful activation. @@ -153,7 +153,7 @@ By default, QuecPython modules automatically activate the first cellular NIC at dataCall.setAutoActivate(profileID, enable) ``` -The parameters are saved automatically and the configuration takes effect after the module is rebooted. +The parameters set by this method are non-volatile and the configuration takes effect after the module is rebooted. ### Application Scenarios @@ -182,21 +182,21 @@ It is recommended not to disable the automatic reconnection of the NIC unless th dataCall.setAutoConnect(profileID, enable) ``` -The parameters are saved automatically and the configuration takes effect after the module is rebooted. +The parameters set by this method are non-volatile and the configuration takes effect after the module is rebooted. ### Application Scenarios You can call the above function to set whether the NIC automatically reconnects to the network in the following scenarios: -When you do not need the NIC to automatically reconnect to the network for some special requirements, call `dataCall.setAutoConnect(profileID, 0)` to disable the feature. +* When you do not need the NIC to automatically reconnect to the network for some special requirements, call `dataCall.setAutoConnect(profileID, 0)` to disable the feature. -After calling `dataCall.setAutoActivate(profileID, 1)` to set the automatic activation of a certain or multiple cellular NICs at startup, you need to determine whether this or these NICs need to automatically reconnect to the network. If the automatic reconnection feature is required, call `dataCall.setAutoConnect(profileID, 1)`, otherwise, call `dataCall.setAutoConnect(profileID, 0)`. +* After calling `dataCall.setAutoActivate(profileID, 1)` to set the automatic activation of a certain or multiple cellular NICs at startup, you need to determine whether this or these NICs need to automatically reconnect to the network. If the automatic reconnection feature is required, call `dataCall.setAutoConnect(profileID, 1)`, otherwise, call `dataCall.setAutoConnect(profileID, 0)`. ## Network Event Listening -QuecPython provides an API for you to listen for network status change events. The specific solution is to enable you to register callback functions. When the connection status between the cellular NIC and the network changes, the system will inform you of the current network connection status through the registered callback function. Please refer to [Register Callback Function](https://python.quectel.com/doc/API_reference/en/iotlib/dataCall.html#Register-Callback-Function) in the wiki on the QuecPython official website for details. +QuecPython provides APIs for users to listen to network state change events. The specific approach is to allow users to register callback functions. When the connection status to the network changes, the system will notify the current network connection status through the user's registered callback function. Please refer to [Register Callback Function](https://python.quectel.com/doc/API_reference/en/iotlib/dataCall.html#Register-Callback-Function) in the wiki on the QuecPython official website for details. ### Register Callback Function @@ -236,11 +236,11 @@ Note: CSQ represents signal strength and is a parameter used to indicate RSSI strength. In other words, CSQ is essentially the same as RSSI. Generally, you can determine signal strength by CSQ value. Range: 0 – 31, with higher values indicating better signal quality. -SINR represents the ratio of the desired signal power to the sum of the power of all other interfering signals (noise and interference), reflecting the link quality of the current channel. Range: 0 – 30, with higher values indicating better signal quality. +SINR represents the ratio of the desired signal power to the sum of the power of all other interfering signals (noise and interference), reflecting the link quality of the current channel. Range: -10 dBm – 40 dBm, with higher values indicating better signal quality. -RSRP represents the path loss intensity of the current channel and is used for measuring cell signal coverage and cell selection/reselection. We can judge the signal coverage of the cell based on this parameter value. Range: -44 to -140 dBm, with higher values indicating better signal quality. +RSRP represents the path loss intensity of the current channel and is used for measuring cell signal coverage and cell selection/reselection. We can judge the signal coverage of the cell based on this parameter value. Range: -140 dBm – -44 dBm, with higher values indicating better signal quality. -RSRQ represents the signal-to-noise ratio and interference level of the current channel quality. RSRQ changes with network load and interference. The larger the network load and interference, the smaller the RSRQ value. Range: -19.5 dB to -3 dB, with higher values indicating better signal quality. +RSRQ represents the signal-to-noise ratio and interference level of the current channel quality. RSRQ changes with network load and interference. The larger the network load and interference, the smaller the RSRQ value. Range: -20 dB – -3 dB, with higher values indicating better signal quality. ### Application Scenarios @@ -268,7 +268,7 @@ When calling this function to get cell information, the module will perform a re You may need to get the cell information in the following scenarios: -* For base station positioning, information about surrounding cells is required. If using QuecPython's base station positioning feature, you do not need to get cell information because this operation is automatically performed by the base station positioning code. If you implementing base station positioning through a third-party platform, you need to call `net.getCellInfo()` to get cell information and upload it to the relevant server. +* For base station positioning, information about surrounding cells is required. If using QuecPython's base station positioning feature, you do not need to get cell information because this operation is automatically performed by the base station positioning code. If you implementing base station positioning through a third-party platform, you need to call `net.getCellInfo()` to get cell information and upload them to the relevant server. * If you want to know which cells are included in the current environment, call `net.getCellInfo()`. @@ -303,9 +303,9 @@ From the return value of `net.getConfig()` in [Network Mode and Roaming Configur You may need to set the network modes of the module in the following scenarios: -- If the module supports multiple network modes, but when you call `net.getConfig()` to get the current network mode and find that the module is currently configured to only support a certain network mode, you can use call `net.setConfig()` to reconfigure the module to support multiple network modes. +- If the module supports multiple network modes, but when you call `net.getConfig()` to get the current network mode and find that the module is currently configured to only support a certain network mode, you can call `net.setConfig()` to reconfigure the module to support multiple network modes. -* If the module supports multiple network modes, the default mode is a combination of the supported network modes. However, if the SIM card used only supports one of the network modes, you can call `net.setConfig` to set the network mode of the module to the one supported by the SIM card. This will speed up the module's network registration process by searching for cells directly on the network mode supported by the SIM card. +* If the module supports multiple network modes, the default mode is a combination of the supported network modes. However, if the SIM card used only supports one of the network modes, you can call `net.setConfig()` to set the network mode of the module to the one supported by the SIM card. This will speed up the module's network registration process by searching for cells directly on the network mode supported by the SIM card. * If the module supports multiple network modes, the default mode is a combination of the supported network modes. However, if the surrounding cells of the module only support one network mode, such as GSM, you can call `net.setConfig()` to set the network mode of the module to the one supported by the surrounding cells. @@ -385,7 +385,7 @@ net.setBand(netRat, gsmBand, bandTuple) You may need to get and set bands in the following scenarios: -* If you want to know which bands the module currently supports, you can call `net.getState()` or refer to the module specification. Please note that module specifications describe the bands theoretically supported by the module, while the `net.getState()` returns the bands actually supported. +* If you want to know which bands the module currently supports, you can call `net.getBand()` or refer to the module specification. Please note that module specifications describe the bands theoretically supported by the module, while the `net.getBand()` returns the bands actually supported. * Some special SIM cards only support specific bands. You can call `net.setBand()` to lock the module band to the specific band supported by the SIM card. diff --git a/docs/Application_guide/en/network-comm/nic/cellular/application.md b/docs/Application_guide/en/network-comm/nic/cellular/application.md index e8a49c3ad73f7f6c9075273250c03ecb35306103..d271ff569a8f85a515c498bf5f34a4e3befa5ff5 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/application.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/application.md @@ -348,7 +348,7 @@ The above sample code download link:[Download](https://github.com/QuecPython/exa ## Manually Activate One NIC -The scenario of manually activating a cellular NIC is relatively rare, mainly because customers have special requirements and do not need to automatically activate the cellular NIC at startup. Instead, they manually activate the NIC when needed through a user application. It should be noted that there is no essential difference between manually activating a NIC and automatically activating a NIC at startup. The main difference lies in the timing of activation. After successful activation, the NIC can be used for network communication, and the two activation methods are exactly the same. +There are generally few scenarios for manually activating cellular NIC. This scenario is mainly used to meet some special needs of users. For example, users do not need to automatically activate the cellular NIC when the device is turned on. Instead, the user application actively performs the NIC activation operation when needed. It should be noted that there is no essential difference between manually activating a NIC and automatically activating a NIC at startup. The main difference lies in the timing of activation. After successful activation, the NIC can be used for network communication, and the two activation methods are exactly the same. In the scenario of manually activating a cellular NIC, you manually activate the cellular NIC and use it for network communication. The diagram is shown below. @@ -670,7 +670,7 @@ The above sample code download link:[Download](https://github.com/QuecPython/exa ## Configure DNS Server Address -Generally, when activating the cellular NIC, as long as the module uses Internet APN, the core network will automatically assign a DNS server address to the module. Under normal circumstances, you do not need to manually configure the DNS server address. However, sometimes the DNS server addresses assigned by the core network may be unavailable, and in this case, you have to manually configure DNS server addresses. +Generally, when activating the cellular NIC, as long as the module uses Internet APN, the core network will automatically assign DNS server address to the module. Under normal circumstances, you do not need to manually configure the DNS server address. However, sometimes the DNS server addresses assigned by the core network may be unavailable, and in this case, you have to manually configure DNS server addresses. You can call the following function to configure the server address of the specified DNS. diff --git a/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md b/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md index 4121b87964545e590ce6ee983c8e8f13747ecaa0..61d08632a27699378a9ff29c1f8add8557f53bda 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md @@ -56,7 +56,7 @@ The combination of MCC and MNC forms a globally unique code used to identify eve ## Cell -In a mobile network, a cell represents a specific geographical area covered by a base station. Each cell is covered by a base station and receives network services from the base station. The size of each cell is not uniform and can be adjusted according to needs and environment. +In a mobile network, a cell represents a specific geographical area covered by a base station. Each cell is covered by a base station and receives network services from the base station. The coverage area of each cell is different and can be adjusted according to needs and environment. For a UE, cells are divided into serving cells and neighboring cells. @@ -128,7 +128,7 @@ RSSI is usually a relative value, and its measurement is highly dependent on the ### CSQ -[CSQ](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#%3Ccode%3Enet.csqQueryPoll%3C/code%3E) (Carrier Signal Quality) refers to the signal strength, used to indicate RSSI level. Range: 0 – 3. Larger values indicate better signal strength. If the CSQ value is less than 6, the terminal may have difficulty establishing network communication. There is a corresponding relationship between CSQ and RSSI: +[CSQ](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#%3Ccode%3Enet.csqQueryPoll%3C/code%3E) (Carrier Signal Quality) refers to the signal strength, used to indicate RSSI level. Range: 0 – 31. Larger values indicate better signal strength. If the CSQ value is less than 6, the terminal may have difficulty establishing network communication. There is a corresponding relationship between CSQ and RSSI: $$ CSQ = (RSSI + 113) / 2 $$ @@ -193,7 +193,7 @@ The following RSCP standards are for reference only: ### SINR -[SINR](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Signal to Interference plus Noise Ratio) refers to the ratio of the received useful signal strength to the received interference signal strength. It is an important parameter for measuring signal quality in mobile network communication. Range: 0 dB to 40 dB. +[SINR](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Signal to Interference plus Noise Ratio) refers to the ratio of the received useful signal strength to the received interference signal strength. It is an important parameter for measuring signal quality in mobile network communication. Range: -10 dB to 40 dB. The following SINR standards are for reference only: diff --git a/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md b/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md index ef57fed8539d7454f58a87555f2ffd88dbbf4211..46d851abbb6d14189633d5d2d13fdd1c4d173746 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md @@ -28,7 +28,7 @@ Check the status of the SIM card using the following method: Step 1: Connect the module to the USB port of the computer with a USB cable. -Step 2: Open *QPYcom* on the computer, open the QuecPython REPL command port (NMEA Port in the figure), and enter interactive mode. +Step 2: Open *QPYcom* on the computer, open the QuecPython REPL command port (NMEA Port in the figure), and enter REPL mode. ![](../../../media/network-comm/nic/cellular/open-REPL-port_en.png) @@ -139,7 +139,7 @@ Network registration failure refers to the scenario where the module has success ![](../../../media/network-comm/nic/cellular/sim-status-is-1-network-register-failed.png) -There are five possible reasons for network registration failure: +There are many reasons for this, common reasons include the following: #### Poor RF performance @@ -185,7 +185,7 @@ QuecPython module automatically activates the first cellular NIC at startup. Tak 0 ``` -The above example is executed in the REPL interface of *QPYcom*. If you want to query and configure APN, run the following QuecPython script. +The above example is executed in the REPL mode of *QPYcom*. If you want to query and configure APN by python script file, you can write it as follows: ```python import checkNet @@ -307,7 +307,7 @@ For more detailed examples of APN configuration, please refer to the *No APN Con #### NIC Automatic Activation at Startup is Disabled -If the APN is configured correctly, you can call `dataCall.setAutoActivate()` to check whether you have previously disabled the automatic activation of the NIC, or configured it to automatically activate the second or third NIC at startup. You can take the following steps to troubleshoot the problem. +If the APN is configured correctly, you can check whether you have previously disabled the automatic activation of the NIC by calling `dataCall.setAutoActivate()` , or configured it to automatically activate the second or third NIC at startup. You can take the following steps to troubleshoot the problem. Step 1: Check whether there is a *`datacall_config.json`* file in the *`usr`* directory in QPYcom. @@ -337,7 +337,7 @@ Reorganize the format of `cfg`. } ``` -At this point, the configuration of each NIC is explicit. If the result you got matches the above configuration, it means you have disabled the automatic activation of the NIC at startup. If the result you got is different from the above configuration, you need to confirm the value of `autoConnect` for the three NICs, because this value determines whether the NIC is automatically activated at startup. If the value is 0, it means the NIC is not activated at startup; if it is 1, it means the NIC will be activated at startup. +At this point, the configuration of each NIC is explicit. If the result you got matches the above configuration, it means you have disabled the automatic activation of the NIC at startup. If the result you got is different from the above configuration, you need to confirm the value of `autoActivate` for the three NICs, because this value determines whether the NIC is automatically activated at startup. If the value is 0, it means the NIC is not activated at startup; if it is 1, it means the NIC will be activated at startup. Step 3: Restore the automatic activation of the NIC at startup. @@ -372,7 +372,7 @@ import checkNet def main(): - stage, state = checkNet.waitNetworkReady(20) + stage, state = checkNet.waitNetworkReady(30) if stage == 3 and state == 1: print('Network connected successfully.') # do something diff --git a/docs/Application_guide/en/network-comm/nic/cellular/mechanism.md b/docs/Application_guide/en/network-comm/nic/cellular/mechanism.md index 51f168c35497877821f542cb16ce22c34fd9ed19..57cea837c244d03404b4d2f9f1b3038a959b420c 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/mechanism.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/mechanism.md @@ -64,7 +64,7 @@ The basic working principle of the automatic reconnection mechanism of the cellu ![](../../../media/network-comm/nic/cellular/auto-connect.png) -The system will monitor the connection status between the device and the NIC. When the network is disconnected and the factors causing the network exception disappear, the device will automatically initiate the attach procedure to re-register on the network. Once the registration is successful, the system will reactivate the NIC based on the parameters configured before. +The system will monitor the connection status between the device and the cellular network. When the network is disconnected and the factors causing the network exception disappear, the device will automatically initiate the attach procedure to re-register on the network. Once the registration is successful, the system will reactivate the NIC based on the parameters configured before. Some common reasons that may cause the device's network disconnection are listed below: @@ -108,13 +108,13 @@ Configure automatic reconnection: dataCall.setAutoConnect(profileID, enable) ``` -By default, the *`datacall_config.json`* file does not exist. Only when you call `dataCall.setAutoActivate` or `dataCall.setAutoConnect` to configure the corresponding feature will the system create the *`datacall_config.json`* file in the *`usr`* directory of the module and save the configuration in it. The configuration will not be saved automatically. +By default, the *`datacall_config.json`* file does not exist. Only when you call `dataCall.setAutoActivate` or `dataCall.setAutoConnect` to configure the corresponding feature will the system create the *`datacall_config.json`* file in the *`usr`* directory of the module and save the configuration in it. This file will not be lost if the device is powered off.
**Saving of Configured APN and Other Parameters** -The configured APN and other parameters for each cellular NIC will be saved in the system's NVM and will not be lost due to power failure. That is, the information configured in the following method will be saved. +The configured APN and other parameters for each cellular NIC will be saved in the system's NVM and will not be lost due to power off. That is, the information configured in the following method will be saved. ```python dataCall.setPDPContext(profileID, ipType, apn, username, password, authType) @@ -128,7 +128,7 @@ dataCall.setPDPContext(profileID, ipType, apn, username, password, authType) **Scenarios for Using `checkNet`** -The process of UE network registration after power-on is a complex process, which requires the terminal device to interact with the base station and the core network to confirm information. This process is affected by many factors, such as the RF performance of the terminal device (hardware design and antenna), surrounding environment, cell signal coverage, and base station load. Therefore, it is common and normal for the cellular NIC to not be activated successfully when the device starts up and your application starts running. +The process of UE network registration after power-on is relatively complicated, which requires the terminal device to interact with the base station and the core network to confirm information. This process is affected by many factors, such as the RF performance of the terminal device (hardware design and antenna), surrounding environment, cell signal coverage, and base station load. Therefore, it is common and normal for the cellular NIC to not be activated successfully when the device starts up and your application starts running. If you perform network-related business operations in your applications from the beginning, the network business will likely fail due to the cellular NIC not being activated. Therefore, you are recommended to check whether the network is ready before performing network-related business operations such as socket, HTTP/HTTPs, and MQTT. You can call the following method to check whether the network is ready: @@ -242,6 +242,6 @@ Therefore, when you want your products to connect to public networks (Internet) ### Description -QuecPython modules on various platforms can create multiple virtual cellular NICs. For platform uniformity, three NICs are available for you to activate and use simultaneously and these NICs do not have any special purposes. At the same time, the VoLTE feature on each platform will occupy one NIC, but the specific NIC occupied by VoLTE varies on different platforms. +QuecPython modules on various platforms can create multiple virtual cellular NICs. For platform uniformity, three NICs are available for you to activate and use simultaneously and these NICs do not have any special purposes. At the same time, the VoLTE feature on each platform will occupy one NIC, but the specific NIC occupied by VoLTE varies on different platforms. But it will not occupy the three NICs open to users. > For BG95 series modules, at most 2 NICs can be activated in NB-IoT networks. \ No newline at end of file diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/api-instruction.md b/docs/Application_guide/zh/network-comm/nic/cellular/api-instruction.md index 1dbda3596a1f136fdba983510053261454e62be2..cf6c56e827f4218633db5d4bc1b82297162df936 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/api-instruction.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/api-instruction.md @@ -385,7 +385,7 @@ net.setBand(netRat, gsmBand, bandTuple) 一般如下场景中，用户会需要查询和设置BAND： -* 用户想了解模组当前支持哪些BAND，此时用户可以通过`net.getState`来查询，也可以查阅模组的《模块产品规格书》。需要注意的是，模组的《模块产品规格书》中描述的是模组理论上支持的BAND；而`net.getState`方法查询的是模组实际配置的支持哪些BAND。 +* 用户想了解模组当前支持哪些BAND，此时用户可以通过`net.getBand`来查询，也可以查阅模组的《模块产品规格书》。需要注意的是，模组的《模块产品规格书》中描述的是模组理论上支持的BAND；而`net.getBand`方法查询的是模组实际配置的支持哪些BAND。 * 一些特殊的SIM卡仅支持特定的BAND，此时可以使用`net.setBand`方法来将模组锁定到特定的BAND。 diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/application.md b/docs/Application_guide/zh/network-comm/nic/cellular/application.md index 39dee54bfebbb6043d235959225d5b5d1016ef00..89dc5d75d166d83845b04d4602332a83f5a3d2db 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/application.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/application.md @@ -349,7 +349,7 @@ if __name__ == '__main__': ## 手动激活一路网卡 -手动激活蜂窝无线网卡的场景一般比较少，主要是客户因为一些特殊的需求，不需要开机时自动激活蜂窝无线网卡，而是在需要的时候，由用户应用程序来主动进行网卡激活操作。需要说明的是，用户手动进行网卡激活和模组开机自动进行网卡激活，两者没有本质上的区别，主要区别在于激活的时间点。在激活成功后，使用网卡进行网络通信上，这两种激活方式是完全一样的。 +手动激活蜂窝无线网卡的场景一般比较少，这种场景主要用于满足用户的一些特殊的需求。比如用户不需要设备开机时自动激活蜂窝无线网卡，而是在需要的时候，由用户应用程序来主动进行网卡激活操作。需要说明的是，用户手动进行网卡激活和模组开机自动进行网卡激活，两者没有本质上的区别，主要区别在于激活的时间点。在激活成功后，使用网卡进行网络通信上，这两种激活方式是完全一样的。 我们先来说一下，手动激活一路网卡的场景。这种场景下，当用户手动激活蜂窝无线网卡后，使用网卡进行网络通信时，其过程示意如下图所示： diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md b/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md index 821df8624348932c97c412771f3cf8754c38a09a..801015dd1010256919fd3e9f6b17b53283c1d5b4 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md @@ -374,7 +374,7 @@ import checkNet def main(): - stage, state = checkNet.waitNetworkReady(20) + stage, state = checkNet.waitNetworkReady(30) if stage == 3 and state == 1: print('Network connected successfully.') # do something diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/mechanism.md b/docs/Application_guide/zh/network-comm/nic/cellular/mechanism.md index 1458b9bb06d08711957cd2230782c7d178b4cbc3..5c4c0d0cab713c2d4579347badcad7a0087627c5 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/mechanism.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/mechanism.md @@ -130,7 +130,7 @@ dataCall.setPDPContext(profileID, ipType, apn, username, password, authType) ## checkNet机制 -`checkNet`是QuecPython提供的一个功能模块。该模块主要用于检查网络是否以及就绪。关于该`checkNet`模块API的使用说明，请参考QuecPython官网API参考手册内[checkNet](https://python.quectel.com/doc/API_reference/zh/iotlib/checkNet.html)部分。 +`checkNet`是QuecPython提供的一个功能模块。该模块主要用于检查网络是否已经就绪。关于该`checkNet`模块API的使用说明，请参考QuecPython官网API参考手册内[checkNet](https://python.quectel.com/doc/API_reference/zh/iotlib/checkNet.html)部分。 **`checkNet`使用场景** @@ -236,7 +236,7 @@ if __name__ == '__main__': main() ``` -上面的示例仅仅是为了让用户直观的感受一下QuecPython的网络事件监控功能。如果用户需要在实际项目中使用，请参考后续《网络异常处理》章节中“网络异常事件处理示例”部分。 +上面的示例仅仅是为了让用户直观的感受一下QuecPython的网络事件监控功能。如果用户需要在实际项目中使用，请参考后续《网络异常处理》章节中[网络异常事件处理示例](./exception-handling.html#网络异常事件处理示例)部分。