You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/2025/09/esp-wifi-remote/index.md
+26-23Lines changed: 26 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,29 +29,32 @@ Before diving into the details, let's establish the key terminology used through
29
29
30
30
Let's examine the traditional WiFi experience, then see how esp-wifi-remote enables the same experience with external WiFi hardware:
31
31
32
-
**1) Traditional WiFi Experience:** The standard approach where users call `esp_wifi_...()` API to control the local WiFi.
33
-
34
-
{{< figure
35
-
default=true
36
-
src="wifi_experience_1.webp"
37
-
>}}
38
-
39
-
**2A) esp-wifi-remote with non WiFi Chips:** The Same experience, users call `esp_wifi_...()` API to control the external hardware -- Remote Wifi.
40
-
41
-
{{< figure
42
-
default=true
43
-
src="wifi_experience_2A.webp"
44
-
>}}
45
-
46
-
**2B) esp-wifi-remote with WiFi-capable Chips:** This scenario enables dual WiFi interfaces for applications that need multiple wireless connections.
47
-
- Users call `esp_wifi_...()` API to control the local WiFi.
48
-
- Users call `esp_wifi_remote_...()` API to control the remote WiFi.
49
-
- This scenario is also useful for initial exploring of `esp-wifi-remote` functionality with just two "common" ESP32 chips -- For basic setup, you just need two evaluation boards.
50
-
51
-
{{< figure
52
-
default=true
53
-
src="wifi_experience_2B.webp"
54
-
>}}
32
+
### Traditional WiFi scenario
33
+
34
+
- Users call `esp_wifi_...()` API to control the local WiFi
35
+
{{< figure
36
+
default=true
37
+
src="wifi_experience_1.webp"
38
+
>}}
39
+
40
+
### `esp-wifi-remote` with non WiFi Chips
41
+
42
+
- Users call `esp_wifi_...()` API to control the remote WiFi
43
+
{{< figure
44
+
default=true
45
+
src="wifi_experience_2A.webp"
46
+
>}}
47
+
48
+
### `esp-wifi-remote` with WiFi-capable Chips
49
+
50
+
- Users call `esp_wifi_...()` API to control the local WiFi
51
+
- Users call `esp_wifi_remote_...()` API to control the remote WiFi
52
+
{{< figure
53
+
default=true
54
+
src="wifi_experience_2B.webp"
55
+
>}}
56
+
57
+
This dual WiFi scenario is useful for applications that need multiple wireless connections. It is also useful for initial exploring of `esp-wifi-remote` functionality with just two "common" ESP32 chips. For basic setup, you only need two evaluation boards.
0 commit comments