Lines Matching refs:scan

16 - Support both fast scan and all-channel scan
139 The scan-done event is triggered by :cpp:func:`esp_wifi_scan_start()` and will arise in the followi…
141 …- The scan is completed, e.g., the target AP is found successfully, or all channels have been scan…
142 - The scan is stopped by :cpp:func:`esp_wifi_scan_stop()`.
143 …_wifi_scan_start()` is called before the scan is completed. A new scan will override the current s…
145 The scan-done event will not arise in the following scenarios:
147 - It is a blocked scan.
148 - The scan is caused by :cpp:func:`esp_wifi_connect()`.
150 …he Wi-Fi driver to free the internal memory which is allocated during the scan **(do not forget to…
170 …fails to set up a connection with the AP due to certain reasons, e.g. the scan fails to find the t…
331 …c:`esp_wifi_connect()` is called, the Wi-Fi driver will start the internal scan/connection process.
333 …- s4.2: If the internal scan/connection process is successful, the `WIFI_EVENT_STA_CONNECTED`_ wil…
426 | | The default scan is an active scan. |
435 | Foreground Scan | This scan is applicable when there is no Wi-Fi connection |
440 | Background Scan | This scan is applicable when there is a Wi-Fi connection in |
442 | | Whether it is a foreground scan or background scan depends on|
448 | | to 0, it is an all-channel scan. |
453 | | 1, it is a specific-channel scan. |
457 The scan modes in above table can be combined arbitrarily, so we totally have 8 different scans:
471 The scan type and other per-scan attributes are configured by :cpp:func:`esp_wifi_scan_start`. The …
484 | channel | If "channel" is 0, there will be an all-channel scan; |
485 | | otherwise, there will be a specific-channel scan. |
488 | show_hidden | If "show_hidden" is 0, the scan ignores the AP with a hidden |
489 | | SSID; otherwise, the scan considers the hidden AP a normal |
492 | scan_type | If "scan_type" is WIFI_SCAN_TYPE_ACTIVE, the scan is |
496 | scan_time | This field is used to control how long the scan dwells on |
503 | | in the table below. Here, min is short for scan |
506 | | - min=0, max=0: scan dwells on each channel for 120 ms. |
507 | | - min>0, max=0: scan dwells on each channel for 120 ms. |
508 | | - min=0, max>0: scan dwells on each channel for ``max`` ms. |
509 | | - min>0, max>0: the minimum time the scan dwells on each |
511 | | frame, the scan switches to the next channel. Otherwise, |
512 | | the scan dwells on the channel for ``max`` ms. |
515 | | the scan, you can try to modify these two parameters. |
519 There are also some global scan attributes which are configured by API :cpp:func:`esp_wifi_set_conf…
530 seqdiag foreground-scan-all-channels {
554 …d scan. The foreground scan can only occur in Station mode where the station does not connect to a…
562 …_scan_start()` to configure the scan. To do so, you can refer to `Scan Configuration`_. Since this…
568 …- s2.1: The Wi-Fi driver switches to channel 1, in case the scan type is WIFI_SCAN_TYPE_ACTIVE, an…
576scan. Then, it allocates enough entries and calls :cpp:func:`esp_wifi_scan_get_ap_records()` to ge…
586 seqdiag background-scan-all-channels {
612 …d scan. Compared to `Scan All APs on All Channels (Foreground)`_ , the difference in the all-chann…
622 seqdiag scan-specific-channels {
645 This scan is similar to `Scan All APs on All Channels (Foreground)`_. The differences are:
648 …. If the scan is WIFI_FAST_SCAN scan and the target AP is found, then the scan-done event will ari…
650 …f we happen to scan two APs whose SSID is "ap". If the scan is WIFI_FAST_SCAN, then only the first…
652 You can scan a specific AP, or all of them, in any given channel. These two scenarios are very simi…
657scan the configured AP first. The scan in "Wi-Fi Connect" is the same as `Scan for Specific AP On …
662scan is a blocked one, and the application task will be blocked until the scan is done. The blocke…
666scan-done event. Both scenarios can happen. **However, the Wi-Fi driver does not support multiple …
671 …riority than the scan. If scan fails because of connecting, the recommended strategy is to delay s…
677 … e.g. the console task, call :cpp:func:`esp_wifi_scan_start()` to do scan, the scan always fails i…
678 - When scan fails, the application simply delay sometime and retry the scan.
680 In above scenario the scan will never succeed because the connecting is in process. So if the appli…
685 The application can define its own reconnect strategy to avoid the scan starve to death. Refer to <…
690 This scenario only depicts the case when there is only one target AP are found in scan phase, for t…
741 …- s1.2, If the scan fails to find the target AP, `WIFI_EVENT_STA_DISCONNECTED`_ will arise and the…
1003 | | | | fails to scan the target AP, this reason code will …
1104 | scan_method | For WIFI_FAST_SCAN scan, the scan ends when the first matched|
1105 | | AP is found, for WIFI_ALL_CHANNEL_SCAN, the scan finds all |
1107 | | The default scan is WIFI_FAST_SCAN. |
1130 | | whose ssid is "apxx", the scan finds two AP whose ssid equals|
1138 | | to connect AP whose ssid is "apxx", the scan finds two AP |
1349 …used in different Wi-Fi Mode and different country policy, also describe the impact to active scan.
1358 | | | For scan: …
1361 | | | Use active scan from schan to 11 and use passive scan
1365 | | | Use active scan from schan to schan+nchan-1. …
1368 | | | is set to a passive scan channel, the passive scan will …
1377 | | | For scan, scans channel "schan" to "schan+nchan-1" with …
1378 | | | scan. …