diff --git a/docs/API_reference/en/gnsslib/wifiScan.md b/docs/API_reference/en/gnsslib/wifiScan.md index 90069436dc87fe48a97c04a86baa882f9c2f15f4..6435a790251be8ea3cff1e37f7525001799351a5 100644 --- a/docs/API_reference/en/gnsslib/wifiScan.md +++ b/docs/API_reference/en/gnsslib/wifiScan.md @@ -8,11 +8,17 @@ > > EC100Y/EC200N/EC600N/EC600S/EC600M/EC800M/EC800N/EG912N/EG915N/EG810M/EC600G/EC800G/EC200U/EC600U/EG912U/EG915U series module. > -> In EC600M series module, EC600MCN_LC/EC600MCN_LF module does not support the `wifiScan` feature. +> In EC600M series module: EC600MCN_LA/EC600MCN_LE/EC600MEU_LA support the `wifiScan` feature. > -> In EC800M series module, EC800MCN_GC/EC800MCN_LC/EC800MCN_LF does not support the `wifiScan` feature. +> In EC800M series module: EC800MCN_GA/EC800MCN_LA/EC800MCN_LE/EC800MCN_LF/EG810MCN_GA support the `wifiScan` feature. > -> In EC600U series module, EC600UEC_AC does not support the `wifiScan` feature. +> In EC600U series module: EC600UCN_LB/EC600UEU_AB support the `wifiScan` feature. +> +> In E200U series module: EC200UAU_AA/EC200UAU_AB/EC200UCN_AA/EC200UCN_LA/EC200UCN_LB/EC200UEU_AA/EC200UEU_AB support the `wifiScan` feature. +> +> In EG912U series module: EG912UGL_AA support the `wifiScan` feature. +> +> In EG915U series module: EG915UEU_AB/EG915ULA_AB support the `wifiScan` feature. diff --git a/docs/API_reference/zh/gnsslib/wifiScan.md b/docs/API_reference/zh/gnsslib/wifiScan.md index fa2daecce24fd2e686030831789d61861b89c055..20845700aec981680207f55f3336a8a4c8d638ba 100644 --- a/docs/API_reference/zh/gnsslib/wifiScan.md +++ b/docs/API_reference/zh/gnsslib/wifiScan.md @@ -6,13 +6,19 @@ > 支持`wifiScan`功能的模组： > -> EC100Y/EC200N/EC600N/EC600S/EC600M部分系列/EC800M部分系列/EC800N/EG912N/EG915N/EG810M/EC600G/EC800G/EC200U/EC600U部分系列/EG912U/EG915U系列模组。 +> EC100Y/EC200N/EC600N/EC600S/EC600M部分系列/EC800M部分系列/EC800N/EG912N/EG915N/EG810M/EC600G/EC800G/EC200U/EC600U部分系列/EG912U部分系列/EG915U部分系列模组。 > -> EC600M系列模组中，EC600MCN_LC/EC600MCN_LF不支持`wifiScan`； +> EC600M系列模组中，支持的型号有：EC600MCN_LA/EC600MCN_LE/EC600MEU_LA； > -> EC800M系列模组中，EC800MCN_GC/EC800MCN_LC不支持`wifiScan`； +> EC800M系列模组中，支持的型号有：EC800MCN_GA/EC800MCN_LA/EC800MCN_LE/EC800MCN_LF/EG810MCN_GA； > -> EC600U系列模组中，EC600UEC_AC不支持`wifiScan`。 +> EC600U系列模组中，支持的型号有：EC600UCN_LB/EC600UEU_AB； +> +> EC200U系列模组中，支持的型号有：EC200UAU_AA/EC200UAU_AB/EC200UCN_AA/EC200UCN_LA/EC200UCN_LB/EC200UEU_AA/EC200UEU_AB； +> +> EG912U系列模组中，支持的型号有：EG912UGL_AA； +> +> EG915U系列模组中，支持的型号有：EG915UEU_AB/EG915ULA_AB。 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 ed3ef17acf5ea1b3c662ea4cf9928c7ea66e966d..fb6495dcace2c2bcf29f119570ba902d5e6ac3b3 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 @@ -64,13 +64,13 @@ You can call the above functions to get and set the parameters of the NIC in the For how to configure APN, please refer to the following sections in the *Scenario Instructions* chapter, which provide detailed APN configuration examples: -* [Automatically Activate One NIC at Startup and Configure APN](./application.html#Automatically Activate One NIC at Startup and Configure APN) +* [Automatically Activate One NIC at Startup and Configure APN](./application.html#Automatically-Activate-One-NIC-at-Startup-and-Configure-APN) -* [Automatically Activate Multiple NICs at Startup and Configure APN](./application.html#Automatically Activate Multiple NICs at Startup and Configure APN) +* [Automatically Activate Multiple NICs at Startup and Configure APN](./application.html#Automatically-Activate-Multiple-NICs-at-Startup-and-Configure-APN) -* [Manually Activate One NIC](./application.html#Manually Activate One NIC) +* [Manually Activate One NIC](./application.html#Manually-Activate-One-NIC) -* [Manually Activate Multiple NICs](./application.html#Manually Activate Multiple NICs) +* [Manually Activate Multiple NICs](./application.html#Manually-Activate-Multiple-NICs) @@ -98,8 +98,8 @@ If you disable the automatic activation of cellular NICs at startup and set a pr For how to manually activate NICs, please refer to the following sections in the *Scenario Instructions* chapter, which provide detailed APN configuration examples: -* [Manually Activate One NIC](./application.html#Manually Activate One NIC) -* [Manually Activate Multiple NICs](./application.html#Manually Activate Multiple NICs) +* [Manually Activate One NIC](./application.html#Manually-Activate-One-NIC) +* [Manually Activate Multiple NICs](./application.html#Manually-Activate-Multiple-NICs) @@ -210,13 +210,13 @@ In practical use, due to various reasons (such as network exception, environment For how to use network event listening to handle network exceptions, please refer to the following section in the *Handle Network Exceptions* chapter: -* [Example of Handling Network Exception Events](./exception-handling.html#Example of Handling Network Exception Events) +* [Example of Handling Network Exception Events](./exception-handling.html#Example-of-Handling-Network-Exception-Events) ## Get Signal Strength -QuecPython provides APIs to obtain parameters such as signal strength and signal quality. These parameters can help you determine the signal strength and signal quality of the current device's environment. The commonly used parameters include CSQ, RSSI, SINR, RSRP, and RSRQ. It is recommended to read the [Signal Quality](./common-concepts.html#Signal Quality) section in the *Basic Concepts of Cellular Network* chapter together. Please refer to [Get Signal Strength](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Signal-Strength) and [Get Detailed Signal Strength](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) in the wiki on the QuecPython official website for details. +QuecPython provides APIs to obtain parameters such as signal strength and signal quality. These parameters can help you determine the signal strength and signal quality of the current device's environment. The commonly used parameters include CSQ, RSSI, SINR, RSRP, and RSRQ. It is recommended to read the [Signal Quality](./common-concepts.html#Signal-Quality) section in the *Basic Concepts of Cellular Network* chapter together. Please refer to [Get Signal Strength](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Signal-Strength) and [Get Detailed Signal Strength](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) in the wiki on the QuecPython official website for details. ### Query Signal Strength and Quality 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 dc0b3df4b1750c8b397deca48b84bf84073f63f8..e8a49c3ad73f7f6c9075273250c03ecb35306103 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/application.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/application.md @@ -6,11 +6,11 @@ Users can refer to the following table to choose and view the configuration meth | Corresponding scenario | Reference section | | ------------------------------------------------------------ | ------------------------------------------------------------ | -| The SIM card can access the Internet without configuring an APN. Users only need to determine that the module has successfully connected to the Internet and directly use socket/mqtt/http to directly access the public network. | [Automatically Activate One NIC at Startup Without Configuring APN](./application.html#Automatically Activate One NIC at Startup Without Configuring APN) | -| The SIM card needs to be configured with APN before it can access the Internet. Users only need to determine that the module is successfully connected to the Internet and directly use socket/mqtt/http to directly access the public network or a private network. | [Automatically Activate One NIC at Startup and Configure APN](./application.html#Automatically Activate One NIC at Startup and Configure APN) | -| The SIM card needs to be configured with APN before it can access the Internet. For user business, it is necessary to automatically activate multiple network cards after the module is powered on. For example, one network card is used to access a public network, and another network card is used to access a private network. | [Automatically Activate Multiple NICs at Startup and Configure APN](./application.html#Automatically Activate Multiple NICs at Startup and Configure APN) | -| The SIM card needs to be configured with an APN before it can access the Internet. Users do not want the module to automatically activate the network card when it is powered on. Instead, they want the user to actively activate a certain network card when needed, and then deactivate the network card after the network service is completed. | [Manually Activate One NIC](./application.html#Manually Activate One NIC) | -| The SIM card needs to be configured with APN before it can access the Internet. For user business, the module needs to activate multiple network cards. For example, one network card is used to access a public network, and another network card is used to access a private network. And users hope that they can control the activation of multiple network cards when needed, instead of having the module automatically complete it when it is powered on. | [Manually Activate Multiple NICs](./application.html#Manually Activate Multiple NICs) | +| The SIM card can access the Internet without configuring an APN. Users only need to determine that the module has successfully connected to the Internet and directly use socket/mqtt/http to directly access the public network. | [Automatically Activate One NIC at Startup Without Configuring APN](./application.html#Automatically-Activate-One-NIC-at-Startup-Without-Configuring-APN) | +| The SIM card needs to be configured with APN before it can access the Internet. Users only need to determine that the module is successfully connected to the Internet and directly use socket/mqtt/http to directly access the public network or a private network. | [Automatically Activate One NIC at Startup and Configure APN](./application.html#Automatically-Activate-One-NIC-at-Startup-and-Configure-APN) | +| The SIM card needs to be configured with APN before it can access the Internet. For user business, it is necessary to automatically activate multiple network cards after the module is powered on. For example, one network card is used to access a public network, and another network card is used to access a private network. | [Automatically Activate Multiple NICs at Startup and Configure APN](./application.html#Automatically-Activate-Multiple-NICs-at-Startup-and-Configure-APN) | +| The SIM card needs to be configured with an APN before it can access the Internet. Users do not want the module to automatically activate the network card when it is powered on. Instead, they want the user to actively activate a certain network card when needed, and then deactivate the network card after the network service is completed. | [Manually Activate One NIC](./application.html#Manually-Activate-One-NIC) | +| The SIM card needs to be configured with APN before it can access the Internet. For user business, the module needs to activate multiple network cards. For example, one network card is used to access a public network, and another network card is used to access a private network. And users hope that they can control the activation of multiple network cards when needed, instead of having the module automatically complete it when it is powered on. | [Manually Activate Multiple NICs](./application.html#Manually-Activate-Multiple-NICs) | 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 4d0a45ac85c52c07571fdc8d079b83738feada98..4121b87964545e590ce6ee983c8e8f13747ecaa0 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 @@ -32,7 +32,7 @@ All operators have their own APNs. Generally, for regular SIM cards (also known ## CFUN -CFUN (Cellular Functionality) refers to the functional mode of a mobile terminal. When talking about CFUN, we generally refer to the APIs of `net` feature or the AT command `AT+CFUN` to set or get the functional mode of the mobile terminal. For how to get and set CFUN, please refer to [Get/Set Module Work Mode](./api-instruction.html#Get/Set Module Work Mode) section in the *Cellular Network API* chapter. Mobile terminals usually have the following functional modes: +CFUN (Cellular Functionality) refers to the functional mode of a mobile terminal. When talking about CFUN, we generally refer to the APIs of `net` feature or the AT command `AT+CFUN` to set or get the functional mode of the mobile terminal. For how to get and set CFUN, please refer to [Get/Set Module Work Mode](./api-instruction.html#Get/Set-Module-Work-Mode) section in the *Cellular Network API* chapter. Mobile terminals usually have the following functional modes: * Minimum functionality mode: In this mode, the entire radio frequency network protocol stack is turned off, and the SIM card is powered off. In this mode, the power consumption of the terminal device is the lowest when it is not turned off. diff --git a/docs/Application_guide/en/network-comm/nic/cellular/hardware-arch.md b/docs/Application_guide/en/network-comm/nic/cellular/hardware-arch.md index b2d81e8b97f19b5ad5b285817c258d4cbe7df33f..0ea14a4982f241aadda9a0be4530389b018dff06 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/hardware-arch.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/hardware-arch.md @@ -52,7 +52,7 @@ In actual network communication, C-Plane and U-Plane communication usually occur The following diagram shows the layered structure of the C-Plane protocol stack in the LTE network architecture. -![](../../../media/network-comm/nic/cellular/layered structure of the C-Plane.png) +![](../../../media/network-comm/nic/cellular/lte-control-plane.png) Because C-Plane is intangible for you and is not directly controlled by you, it will not be further described here. If you want to know more details, please refer to the "Control Plane" section of the [3GPP TS 23401](https://www.3gpp.org/ftp/Specs/archive/23_series/23.401) protocol document. @@ -62,7 +62,7 @@ The following diagram shows the layered structure of the U-Plane protocol stack The application layer only exists in terminal devices and application servers and is based on IP transmission. Your data first goes through layers of processing in the cellular NIC, then is sent to the base station through the wireless interface after passing through the PDN GW for routing, and finally reaches the destination. -![](../../../media/network-comm/nic/cellular/layered structure of the U-Plane.png) +![](../../../media/network-comm/nic/cellular/lte-user-plane.png) From the layered structure diagrams of C-Plane and U-Plane, you can see that they both include the following layers: @@ -84,10 +84,10 @@ The above introduces the layered structure of cellular wireless networks. So how The following diagram shows the data flow based on the hardware structure of the cellular NIC. You can see that your data passes through the TCP/UDP layer, IP layer, PDCP layer, RLC layer and MAC layer in software, and finally reaches the physical layer (i.e., the cellular NIC). When the data reaches the baseband, it is encoded and modulated, and then processed by the RF transceiver to convert it into electromagnetic waves, which are analog signals. Finally, after being processed by the power amplifier, the RF signals are sent out through the RF antenna and reach the base station. Together with the data flow diagram based on the layered structure of cellular wireless networks, you can clearly understand the process of how data reaches the destination from the UE. -![](../../../media/network-comm/nic/cellular/Data flow in hardware structure.png) +![](../../../media/network-comm/nic/cellular/hardware-data-stream.png) #### Data Flow Based on Layered Structure The following diagram shows the data and signaling flow based on the layered structure of cellular wireless networks. -![](../../../media/network-comm/nic/cellular/Data flow.png) \ No newline at end of file +![](../../../media/network-comm/nic/cellular/data-stream.png) \ No newline at end of file diff --git a/docs/Application_guide/en/network-comm/nic/cellular/initialization.md b/docs/Application_guide/en/network-comm/nic/cellular/initialization.md index 9fb2c3f9079a3b8107ce0d2fb72b788080aa0053..2747ab1e24a9d7405672f2baf05561b06291f04f 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/initialization.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/initialization.md @@ -24,7 +24,9 @@ You can send the following AT command to query the network registration status o ``` AT+CREG? -# If the network registration is successful, the return value will be as follows, with the second parameter value being 1 or 5; if it is any other value, it indicates that the network registration failed. +# If the network registration is successful, the return value will be as follows, +# with the second parameter value being 1 or 5; if it is any other value, +# it indicates that the network registration failed. +CREG: 0,1 OK ``` @@ -62,7 +64,7 @@ When the parameter indicated by the red box in the figure in the return value of > If the module fails to register on a network, please refer to the following section in the "*Handle Network Exceptions*" chapter for troubleshooting: > -> * [Module Network Registration Failure](./exception-handling.html#Module Network Registration Failure) +> * [Module Network Registration Failure](./exception-handling.html#Module-Network-Registration-Failure) ## NIC Activation @@ -84,4 +86,4 @@ When the return value of the `dataCall.getInfo()` method indicates that the NIC > If the module fails to activate the NIC, please refer to the following section in the "*Handle Network Exceptions*" chapter for troubleshooting: > -> * [Handle Network Exceptions at Startup](./exception-handling.html#Handle Network Exceptions at Startup) \ No newline at end of file +> * [Handle Network Exceptions at Startup](./exception-handling.html#Handle-Network-Exceptions-at-Startup) \ No newline at end of file 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 4ff614b8920ef2851df8228528e6b53429752d7a..51f168c35497877821f542cb16ce22c34fd9ed19 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/mechanism.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/mechanism.md @@ -224,7 +224,7 @@ if __name__ == '__main__': main() ``` -The above example aims to give you an intuitive understanding of QuecPython's network event listening feature. If you need to use this feature in actual projects, please refer to the "*Example of Handling Network Exception Events*" section of the "*Handle Network Exceptions*" chapter. +The above example aims to give you an intuitive understanding of QuecPython's network event listening feature. If you need to use this feature in actual projects, please refer to the [*Example of Handling Network Exception Events*](./exception-handling.html#Example-of-Handling-Network-Exception-Events).