AN20052 Soft Access Point

1.0 Scope

The scope of this document is an application note to assist users in understanding the capabilities of the Inventek eS-WiFi module when it is configured in Access Point mode. The eS-WiFi family of module products has a powerful built in SoftAP function that allows customers to easily command the eS-WiFi module to join a network for the growing number of machine-to-machine (M2M) and Internet-of-Things (IoT) applications in the home and in the enterprise. The SoftAP function can also be used as well for setting up setup peer-to-peer (P2P) networks and applications such as On-the-Go gaming. The module’s infrastructure mode SoftAP allows both iOS and Android based devices to easily connect to the eS-WiFi Access Point.

1.1 Supported Products

This application is applicable to the eS-WiFi Firmware Release 2.x and 3.x and is currently available on the following eS-WiFi modules:

ISM43362-M3G-L44-U/E  BCM43362 and STM32F205 based module with either etched PCB antenna or U.FL connector for external antenna

ISM4334x-M4G-L44-C/U  BCM4334x and STM32F405 based module with either dual band chip antenna or U.FL connector for external antenna.

2.0 SoftAP Overview

The Inventek eS-WiFi modules are offered with a TCP/IP stack and require only a simple AT command over the UART or SPI interface to communicate with the module. In a typical embedded application, a simple 8/16/32 bit microcontroller is used to send the AT command (“A0”) to initiate a SoftAP. Once the AP is started other devices (users) can join the network and be connected as a client on that network.

Use cases of the SoftAP:

Use Case 1: Joining a Local Area Network using the SoftAP

You have an embedded product and you want to configure that product to join a network (See Figure 1). One way, to make this happen, is to have the eS-WiFi automatically power up as an Access Point. The user can use a PC, tablet or any smartphone to view the AP and type in the SSID and Password. After the user, selects “Join” the Access Point is closed and the eS-WiFi module subsequently turns off the AP and joins the network as a client.

 

Phone Figure 1: Use Case 1 – Connecting eS-WiFi module to a Network Following is the procedure required to implement this use case:

  • Use the “A0” command to activate the SoftAP:
      1. Access Point is activated.
      2. DHCP is activated.
      3. Web server is activated.
      4. DNS is activated.
  • Select ” Join” on the Webpage to connect the eS-WiFi module to the selected network:
      1. Access Point shuts down.
      2. DHCP shuts down.
      3. DNS shuts down.

The module has now joined the selected network as a client/appliance device. SoftAP screen shots:

AP

Note: There is also an AT command for changing the name of the Configuration Access Point to identify a specific customer product name or company name, e.g. change “Inventek” to “ABC Corp.” The user also has the ability to manually enter the information to join a network as well.

 

SoftAP Manual Join screen shots:

PW

WPA

AP name

 

Use Case 2: Direct Connection to the SoftAP

You have embedded the eS-WiFi module into a printer system or interface box and configured it as a SoftAP that allows smartphones/ PC’s and other devices to make a “Direct Connection” via the eS-WiFi SoftAP function (See Figure 2). The SoftAP enables file transfers, file sharing, printing, and information exchange between as many as 8 clients (STAs). This is all accomplished without the use of a fixed AP.One way to facilitate this senario is to have the eS-WiFi automatically power up as a SoftAP that a user can view using a PC or any smartphone and selects “Direct Connect” on the eS-WiFi SoftAP web server. As soon as the user selects “Direct Connect” the Access Point remains running and the client (STA) is connected to the eS-WiFi SoftAP. This allows WLAN devices to easily connect without the need for a fixed AP and supports WiFi M2M communication and ON-The-GO connections for printing and file sharing.

 

Picture1

Figure 2: Use Case 2 – Running eS-WiFi module as SoftAPFollowing is the procedure required to implement this use case:

  • Use the “A0” command to activate the SoftAP:
      1. Access Point is activated.
      2. DHCP is activated.
      3. Web server is activated.
      4. DNS is activated.
  • User selects ” Direct Connect” on the broadcasted Webpage:
      1. Access Point continues to run and manage the SoftAP.
      2. DHCP continues to run.
      3. Web server is shutdown, but SoftAP remains visible.

Multiple clients may now connect to the SoftAP.In summary the “Direct Connection” allows the embedded eS-WiFi to run as a SoftAp with the following capabilities:

  • Supports Client-to-Client (M2M) connections.
  • Supports Client-to-Device/Appliance connections.
  • Supports five Simultaneous Connections.
  • Full interoperability.
2015-06-19T20:22:56+00:00 2018-06-06T23:54:26+00:00