Comparison of Different Wireless Network Card Solutions

[中文]

Note

This document is automatically translated using AI. Please excuse any detailed errors. The official English version is still in progress.

Most Espressif SoCs can serve as Wireless Network Interface Controllers (WNICs), enabling other IoT devices and MCUs to access the internet. The ESP-WNIC solution provides just such functionality. Users can choose the Espressif SoC that best suits their application scenario, thereby benefiting from the low development cost, easy maintenance, and highly scalable features offered by Espressif SoCs. Through the ESP-WNIC solution, users can quickly join a wireless network, connect to the cloud platform, transmit data, and achieve remote control.

Common Espressif wireless network card solution SDKs include:

Below is a comparison table of different Espressif wireless network card solutions:

WNIC Solution Comparison

Network Card Solution

ESP-AT

ESP-Hosted

ESP-IoT-Bridge

USB-Dongle

MCU Adaptation Difficulty

Easy

Medium

Medium

Easy 1

MCU Workload in Complete Solution

Light

Medium

Medium

Medium

MCU Resource Requirements

Ability to parse strings

Ability to run TCP/IP network stack

Ability to run TCP/IP network stack

Ability to support USB host and TCP/IP network protocol stack

Recommended MCU System

Linux, RTOS, Non-OS

Linux, RTOS

Linux, RTOS

Linux, MacOS, Windows

Hardware Communication Interface

UART, SDIO, SPI, USB

SDIO, SPI

USB, ETH, SPI, SDIO

USB

Recommended Throughput Range

0～10 Mbps

0～20+ Mbps

0～25 Mbps

0～6 Mbps

Typical Application Scenarios

Smart home, consumer electronics, POS machines, advertising screens, remote data collection, LBS positioning, low power scenarios requiring MCU sleep, etc.

Robots, set-top boxes, remote video, etc.

Smart home, consumer electronics, IPC, low power scenarios requiring MCU sleep, etc.

Robots, set-top boxes, etc.

Resource Links

esp-at

esp-hosted

esp-iot-bridge 2

usb dongle

Note

  • 1 : The MCU adaptation difficulty of the USB-Dongle is easy, but please note that the MCU needs to support systems with standard USB ECM/NCM protocol stacks such as Linux, MacOS, or Windows.

  • 2 : If access to esp-iot-bridge Github is difficult, you can alternatively visit esp-iot-bridge component for further understanding.

The complete explanation of the advantages and disadvantages of various Espressif wireless gateway solutions is as follows.

ESP-AT

Advantages:

  • No development required on the ESP side

  • Low MCU resource requirements

  • Suitable for various MCU systems, such as Linux, RTOS, non-operating systems

Disadvantages:

  • Lower data throughput (0~10 Mbps)

Reference materials:

ESP-Hosted

Advantages:

  • Suitable for various MCU systems, such as Linux, RTOS

  • High data throughput, up to 25 Mbps with ESP32-C6 and SDIO interface, for specific throughput test results, refer to Throughput performance

Disadvantages:

  • The MCU needs to have the ability to run the TCP/IP network stack

  • High MCU adaptation difficulty and workload

  • ESP as a peripheral of the MCU, cannot work independently and completely

Reference materials:

ESP-IOT-BRIDGE

Advantages:

  • Supports multiple peripherals such as ETH, SPI, SDIO, USB, and can be extended to support ESP Mesh Lite Solution

  • High data throughput, using ESP32 and SDIO interface can reach 25 Mbps

  • Low development cost for ESP and main MCU

  • Can independently run some application functions, providing conditions for low power scenarios such as MCU sleep

Disadvantages:

  • MCU needs to have the ability to run TCP/IP network stack

References:

USB-Dongle

Advantages:

  • Low adaptation difficulty on MCUs supporting USB host ECM/NCM Class (such as Linux, Windows, MacOS)

  • High data transmission stability (using USB interface)

Disadvantages:

  • Relatively low data throughput (0~6 Mbps)

  • Limited application scenarios (such as robots, set-top boxes, etc.)

  • ESP as a peripheral of MCU, cannot work independently and completely

References: