Simplify the charging process with newest Qi RX solution based on the PIC16F15313 and STM32F410RB
Wireless power transfer solution
Published Oct 08, 2024
Click board™
Qi RX Click
Dev Board
Nucleo 64 with STM32F410RB MCU
Compiler
NECTO Studio
MCU
STM32F410RB
Choose Qi RX for a smarter, wireless power solution that transforms the way you charge, streamlining your energy supply with unprecedented accuracy.
A
A
Hardware Overview
How does it work?
Qi RX Click is based on the PIC16F15313, a general-purpose 8-bit MCU that makes a flexible, low-cost alternative to wireless charging solutions based on ASICs from Microchip. The Qi RX Click allows users to quickly add wireless charging functionality to their projects without dealing with complex specific protocols or state machines. It is implemented using a general-purpose 8-bit MCU compatible with the Qi 1.1 (5W) standard. It can be used with any Qi 1.1 compatible wireless charging transmitter with the added functionality of a fully-featured Li-Ion charging controller. Wireless charging uses the principle of magnetic induction to transfer power, similar to a conventional AC transformer, where the receiver and the transmitter coils represent the transformer windings. The high-frequency signal of the Receiver Coil is rectified by a simple full-bridge rectifier implemented with four Schottky diodes (D1-D4), which output voltage is then monitored by the PIC16F15313 through a simple resistive divider R4 and R5. The communication with the
base transmitter is implemented using Amplitude Shift Keying (ASK), as recommended by the Qi 1.1 standard, with two low-power MOSFETs (Q1 and Q2) and two capacitors (C4 and C5) used to modulate the absorbed power. The rectified voltage is also applied at the input of the MCP1755, a low drop-out voltage regulator from Microchip that supplies the 5V voltage for the battery charger and the PIC16F15313 up to 300mA. This LDO is associated with the charge LED indicator labeled CHG, which will indicate the charging progress and turn off once the battery charging is finished. The battery charging functionality is provided by the MCP73830, a single-cell Li-Ion/Li-Polymer battery charge management controller from Microchip. The input current is measured by the PIC16F15313 using a shunt resistor R2 and the MCP6001, a single general-purpose OpAmp offering rail-to-rail input and output up to 6V from Microchip. The gain of this amplifier is set to 10. Measurement of the input current is necessary to accurately calculate input power and implement
the Foreign Object Detection (FOD) function using the power loss method. Qi RX Click communicates with MCU using the MCP3221, a successive approximation A/D converter with a 12-bit resolution from Microchip. This device provides one single-ended input with very low power consumption, a low maximum conversion current, and a Standby current of 250 μA and 1 μA. Data can be transferred at rates of up to 100 kbit/s in the Standard and 400 kbit/s in the Fast Mode. Also, maximum sample rates of 22.3 kSPS with the MCP3221 are possible in a Continuous-Conversion Mode with a clock rate of 400 kHz. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32F410RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32F410RB MCU as your development board.
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for Qi RX Click driver.
Key functions:
qirx_read_data- Read data function.qirx_read_voltage- Read voltage function.
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief QiRX Click example
*
* # Description
* This is an example that demonstrates the use of the Qi RX Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes I2C driver and makes an initial log.
*
* ## Application Task
* This example shows the capabilities of the Qi RX click by measuring voltage of the connected
* battery. In order to get correct calculations user should change "v_ref" value
* to his own power supply voltage.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "qirx.h"
static qirx_t qirx;
static log_t logger;
uint16_t voltage;
uint16_t v_ref = 5058;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
qirx_cfg_t qirx_cfg; /**< Click config object. */
/**
* 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.
qirx_cfg_setup( &qirx_cfg );
QIRX_MAP_MIKROBUS( qirx_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == qirx_init( &qirx, &qirx_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_printf( &logger, "----------------------- \r\n" );
log_printf( &logger, " Qi RX click \r\n" );
log_printf( &logger, "----------------------- \r\n" );
log_info( &logger, " Application Task " );
log_printf( &logger, "----------------------- \r\n" );
}
void application_task ( void )
{
voltage = qirx_read_voltage( &qirx, v_ref );
log_printf( &logger, " Battery voltage: %d mV \r\n", voltage );
log_printf( &logger, "----------------------- \r\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* @file main.c
* @brief QiRX Click example
*
* # Description
* This is an example that demonstrates the use of the Qi RX Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes I2C driver and makes an initial log.
*
* ## Application Task
* This example shows the capabilities of the Qi RX click by measuring voltage of the connected
* battery. In order to get correct calculations user should change "v_ref" value
* to his own power supply voltage.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "qirx.h"
static qirx_t qirx;
static log_t logger;
uint16_t voltage;
uint16_t v_ref = 5058;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
qirx_cfg_t qirx_cfg; /**< Click config object. */
/**
* 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.
qirx_cfg_setup( &qirx_cfg );
QIRX_MAP_MIKROBUS( qirx_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == qirx_init( &qirx, &qirx_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_printf( &logger, "----------------------- \r\n" );
log_printf( &logger, " Qi RX click \r\n" );
log_printf( &logger, "----------------------- \r\n" );
log_info( &logger, " Application Task " );
log_printf( &logger, "----------------------- \r\n" );
}
void application_task ( void )
{
voltage = qirx_read_voltage( &qirx, v_ref );
log_printf( &logger, " Battery voltage: %d mV \r\n", voltage );
log_printf( &logger, "----------------------- \r\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
