Achieve a seamless and fast internet experience, and ensure uninterrupted connectivity and smooth communication across all your devices
A
A
Hardware Overview
How does it work?
WiFi 11 Click is based on the BW16, a low-power dual-band Wireless LAN (WLAN) and Bluetooth Low Energy SoC module from Ai-Thinker. The BW16 module represents a highly integrated WiFi and Bluetooth SOC based on the RTL8720DN, a highly integrated Single-Chip with a low power dual bands (2.4GHz and 5GHz), Wireless LAN (WLAN), and Bluetooth Low Energy (v5.0). It consists of a high-performance MCU (ARM V8M, Cortex-M4F instruction compatible) named KM4, a low-power MCU (ARM V8M, Cortex-M0 instruction compatible) named KM0, WLAN (802.11 a/b/g/n) MAC, a 1T1R capable WLAN baseband, RF, Bluetooth, and other peripherals. The BW16 integrates internal memories for complete WIFI and BLE 5.0 protocol functions. The
embedded memory configuration also provides simple application developments. WiFi 11 Click communicates with MCU using the UART interface at 57600 bps as its default communication protocol. Still, it also allows the user to use other interfaces, such as SPI and I2C if he wants to configure the module and write the library himself. A jumper JP1 on this Click board™ also enables the necessary pull-up resistors on the SCL and SDA lines of I2C communication. After initializing the primary module and before any program uploading, the user should write network and TCP server parameters. Additional functionality, such as the Chip Enable button labeled as RST, used to Enable or put the module in Shut-Down mode, is provided and routed at the
EN pin of the mikroBUS™ socket. Alongside this pin, this Click board™ has one general purpose pin GP1 routed at the INT pin of the mikroBUS™ socket, which can be used in various cases like interrupt or other purposes. WiFi 11 Click also has an additional header with UART RX0 and TX0 module pins on itself and a button labeled as LOG_TX, which can be used for Firmware Updates or as a low-power mode Wake-Up function. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Flip&Click PIC32MZ is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller, the PIC32MZ2048EFH100 from Microchip, four mikroBUS™ sockets for Click board™ connectivity, two USB connectors, LED indicators, buttons, debugger/programmer connectors, and two headers compatible with Arduino-UNO pinout. Thanks to innovative manufacturing technology,
it allows you to build gadgets with unique functionalities and features quickly. Each part of the Flip&Click PIC32MZ development kit contains the components necessary for the most efficient operation of the same board. In addition, there is the possibility of choosing the Flip&Click PIC32MZ programming method, using the chipKIT bootloader (Arduino-style development environment) or our USB HID bootloader using mikroC, mikroBasic, and mikroPascal for PIC32. This kit includes a clean and regulated power supply block through the USB Type-C (USB-C) connector. All communication
methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, user-configurable buttons, and LED indicators. Flip&Click PIC32MZ development kit allows you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU

Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for WiFi 11 Click driver.
Key functions:
wifi11_send_cmd
- Send command functionwifi11_create_tcp_udp_server
- Create TCP/UDP server functionwifi11_connect_to_ap
- Connect to AP function
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* \file
* \brief Wifi11 Click example
*
* # Description
* This example reads and processes data from WiFi 11 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and powers up the module, then connects to the desired AP
* and creates TCP and UDP servers on the desired local port.
*
* ## Application Task
* Logs all the received data and module's responses on the USB UART.
*
* ## Additional Function
* - static void wifi11_clear_app_buf ( void )
* - static void wifi11_error_check( err_t error_flag )
* - static void wifi11_log_app_buf ( void )
* - static err_t wifi11_rsp_check ( void )
* - static err_t wifi11_process ( void )
*
* @note
* In order for the example to work, user needs to set the AP SSID, password, and Local port
* on which the TCP and UDP servers will be created.
* Enter valid data for the following macros: AP_SSID, AP_PASSWORD and LOCAL_PORT.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "wifi11.h"
#include "string.h"
#define APP_OK 0
#define APP_ERROR_DRIVER -1
#define APP_ERROR_OVERFLOW -2
#define APP_ERROR_TIMEOUT -3
#define RSP_OK "OK"
#define RSP_ERROR "ERROR"
#define AP_SSID "" // Set AP SSID
#define AP_PASSWORD "" // Set AP password - if the AP is OPEN remain this NULL
#define LOCAL_PORT 1 // Set Local port on which the TCP and UDP servers will be created.
#define PROCESS_BUFFER_SIZE 500
static wifi11_t wifi11;
static log_t logger;
static char app_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;
static int32_t app_buf_cnt = 0;
static err_t app_error_flag;
/**
* @brief WiFi 11 clearing application buffer.
* @details This function clears memory of application buffer and reset its length and counter.
* @note None.
*/
static void wifi11_clear_app_buf ( void );
/**
* @brief WiFi 11 data reading function.
* @details This function reads data from device and appends data to application buffer.
*
* @return @li @c 0 - Read some data.
* @li @c -1 - Nothing is read.
* @li @c -2 - Application buffer overflow.
*
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t wifi11_process ( void );
/**
* @brief WiFi 11 check for errors.
* @details This function checks for different types of errors and logs them on UART.
* @note None.
*/
static void wifi11_error_check( err_t error_flag );
/**
* @brief WiFi 11 logs application buffer.
* @details This function logs data from application buffer.
* @note None.
*/
static void wifi11_log_app_buf ( void );
/**
* @brief WiFi 11 response check.
* @details This function checks for response and returns the status of response.
*
* @return application status.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t wifi11_rsp_check ( void );
void application_init ( void )
{
log_cfg_t log_cfg;
wifi11_cfg_t cfg;
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, "---- Application Init ----" );
// Click initialization.
wifi11_cfg_setup( &cfg );
WIFI11_MAP_MIKROBUS( cfg, MIKROBUS_1 );
wifi11_init( &wifi11, &cfg );
Delay_ms( 100 );
wifi11_reset_device( &wifi11 );
Delay_ms( 2000 );
// dummy read
wifi11_process( );
wifi11_clear_app_buf( );
log_printf( &logger, "\r\n ---- Common commands ---- \r\n" );
Delay_ms( 500 );
// Test AT command ready
wifi11_send_cmd( &wifi11, WIFI11_CMD_AT );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
// Query version info
wifi11_send_cmd( &wifi11, WIFI11_CMD_ATSV );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
log_printf( &logger, "\r\n ---- WiFi commands ---- \r\n" );
Delay_ms( 500 );
// Set WiFi mode - Station
wifi11_send_cmd_with_parameter( &wifi11, WIFI11_CMD_ATPW, "1" );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
// Connect to AP
wifi11_connect_to_ap( &wifi11, AP_SSID, AP_PASSWORD );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
// Wifi information
wifi11_send_cmd( &wifi11, WIFI11_CMD_ATW );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
log_printf( &logger, "\r\n ---- TCP/IP commands ---- \r\n" );
Delay_ms( 500 );
// Create TCP Server
wifi11_create_tcp_udp_server( &wifi11, WIFI11_TCP_MODE, LOCAL_PORT );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
// Create UDP Server
wifi11_create_tcp_udp_server( &wifi11, WIFI11_UDP_MODE, LOCAL_PORT );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
// Enable auto receive data mode
wifi11_send_cmd_with_parameter( &wifi11, WIFI11_CMD_ATPK, "1" );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
// Check network connection status
wifi11_send_cmd( &wifi11, WIFI11_CMD_ATPI );
app_error_flag = wifi11_rsp_check( );
wifi11_error_check( app_error_flag );
Delay_ms( 500 );
log_printf( &logger, "\r\n ---- Please connect to the TCP/UDP server listed above via" );
log_printf( &logger, " a TCP/UDP client ---- \r\n" );
}
void application_task ( void )
{
wifi11_process( );
wifi11_log_app_buf( );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static void wifi11_clear_app_buf ( void )
{
memset( app_buf, 0, app_buf_len );
app_buf_len = 0;
app_buf_cnt = 0;
}
static err_t wifi11_process ( void )
{
err_t return_flag = APP_ERROR_DRIVER;
int32_t rx_size;
char rx_buff[ PROCESS_BUFFER_SIZE ] = { 0 };
rx_size = wifi11_generic_read( &wifi11, rx_buff, PROCESS_BUFFER_SIZE );
if ( rx_size > 0 )
{
int32_t buf_cnt = 0;
return_flag = APP_OK;
if ( app_buf_len + rx_size >= PROCESS_BUFFER_SIZE )
{
wifi11_clear_app_buf( );
return_flag = APP_ERROR_OVERFLOW;
}
else
{
buf_cnt = app_buf_len;
app_buf_len += rx_size;
}
for ( int32_t rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ )
{
if ( rx_buff[ rx_cnt ] != 0 )
{
app_buf[ ( buf_cnt + rx_cnt ) ] = rx_buff[ rx_cnt ];
}
else
{
app_buf_len--;
buf_cnt--;
}
}
}
return return_flag;
}
static err_t wifi11_rsp_check ( void )
{
uint16_t timeout_cnt = 0;
uint16_t timeout = 10000;
err_t error_flag = wifi11_process( );
if ( ( error_flag != 0 ) && ( error_flag != -1 ) )
{
return error_flag;
}
while ( ( strstr( app_buf, RSP_OK ) == 0 ) && ( strstr( app_buf, RSP_ERROR ) == 0 ) )
{
error_flag = wifi11_process( );
if ( ( error_flag != 0 ) && ( error_flag != -1 ) )
{
return error_flag;
}
timeout_cnt++;
if ( timeout_cnt > timeout )
{
while ( ( strstr( app_buf, RSP_OK ) == 0 ) && ( strstr( app_buf, RSP_ERROR ) == 0 ) )
{
wifi11_send_cmd( &wifi11, WIFI11_CMD_AT );
wifi11_process( );
Delay_ms( 100 );
}
wifi11_clear_app_buf( );
return APP_ERROR_TIMEOUT;
}
Delay_ms( 1 );
}
wifi11_log_app_buf();
return APP_OK;
}
static void wifi11_error_check( err_t error_flag )
{
if ( ( error_flag != 0 ) && ( error_flag != -1 ) )
{
switch ( error_flag )
{
case -2:
log_error( &logger, " Overflow!" );
break;
case -3:
log_error( &logger, " Timeout!" );
break;
default:
break;
}
}
}
static void wifi11_log_app_buf ( void )
{
for ( int32_t buf_cnt = 0; buf_cnt < app_buf_len; buf_cnt++ )
{
log_printf( &logger, "%c", app_buf[ buf_cnt ] );
}
wifi11_clear_app_buf( );
}
// ------------------------------------------------------------------------ END