A Qi wireless charging reference design can help engineers assess how wireless power reception, battery charging and a managed load fit into one embedded system. Microchip’s Qi Wireless Charging LED Lantern demonstrates this approach with a Qi 1.1 receiver, a rechargeable lithium-ion battery, a bidirectional switching converter and a controllable LED string. Although built as a lantern, the design is also a useful example of coordinated embedded power management for engineers evaluating similar functional building blocks.
Qi wireless charging reference design overview
The board is a Qi 1.1-compatible receiver with a maximum power level of 5 W. It is intended to operate with Qi 1.1-compatible wireless charging transmitters. Rather than relying on a dedicated charging controller for all system functions, it uses a general-purpose 8-bit PIC16F18325 microcontroller to manage Qi communication, converter regulation, battery charging and LED dimming.
The reference design’s purpose is to demonstrate a complete operating concept, not to specify a finished industrial product. Its combination of wireless power input and battery-powered output is relevant when assessing designs that need to transfer energy without a charging connector. The documentation notes that eliminating the connector can make encapsulation easier; it does not claim that the board itself has a dust- or waterproof rating.
How the power path works
Power arrives through the receiver coil, with a specified coil input range of 4.5 V to 28 V. A synchronous bidirectional buck or boost converter then serves two different operating modes. In buck mode, it steps the received power down to charge the battery. In boost mode, it raises the battery voltage to drive the LED string.
This shared power stage reduces the need for separate conversion paths for charging and lighting. The PIC microcontroller controls the converter’s regulation and selects its operating mode. An MCP14628 MOSFET driver drives the power train, while an MCP1804 low-dropout regulator supplies 5 V to the microcontroller, driver and MCP6001 operational amplifier.
The design specifies a 2000 mAh Li-Ion battery, charged at 1 A to 4.2 V. Its lighting load is a string of three LEDs, with a maximum drive current of 200 mA at 9 V. These values describe the reference design; they should not be assumed to apply to a different battery, converter or LED assembly.
Battery charging and measurement
The firmware implements a Li-Ion charging sequence that includes precharge, constant-current and constant-voltage stages. It monitors battery voltage and current, using two PI control loops to regulate those quantities during buck-mode charging. Battery current is measured using the MCP6001 low-power operational amplifier.
Charging termination considers more than a single voltage threshold. The documented conditions include current falling below 200 mA, a current plateau and a timeout condition. The battery is considered charged when it reaches 4.2 V and charging current falls below 200 mA. Together, these controls illustrate how measurement and firmware logic coordinate the charging process; the precise algorithm and thresholds remain part of this design’s implementation.
The board also measures voltage on the receiver coil and current through the LEDs using the microcontroller’s analog-to-digital converter. Accurate power measurement supports the receiver’s Foreign Object Detection function. For engineers reviewing the design, this is a reminder that wireless power reception involves monitoring input and load conditions as well as transferring energy.
LED drive, dimming and firmware control
When the lantern function is enabled, the converter changes to boost mode and supplies the LEDs from the battery. The firmware monitors LED current and limits it to a maximum of 200 mA. A button selects four intensity settings: 25%, 50%, 75% and 100%. The selected level is implemented by changing the current reference.
The PIC16F18325 coordinates charging and discharge modes, reads battery voltage and current, controls LED supply and selects the dimming reference. It also controls the bidirectional converter through the microcontroller’s Numerically Controlled Oscillator operating in pulse-frequency mode. The design uses a fixed 2 μs pulse while varying frequency; the stated maximum possible frequency is 500 kHz, with the actual limit dependent on whether the converter is in buck or boost mode.
Evaluating the reference design
The supplied kit includes the assembled LED board and an important information sheet. To operate it, the documentation calls for a two-pin Li-Ion battery with a capacity around 2000 mAh. The battery must be connected and the board switched on; it powers the circuit so it can communicate with a wireless charging station. To charge, the lantern LEDs should be off before placing the board on the charger. Flashing LEDs indicate that charging is complete. For lighting, the button turns the LEDs on and cycles through the dimming levels.
For electrical evaluation, the documentation recommends using a digital meter and oscilloscope. Coil and battery voltages can be checked directly or at their voltage dividers. Battery current can be measured at the MCP6001 output or battery shunt resistor, while LED current can be measured across its dedicated shunt resistor. These test points help engineers examine how the charging and load-control functions behave on the board.
Practical implications for design teams
The lantern provides a compact example of integrating Qi communication, battery charging, power conversion and load control under microcontroller supervision. Its most useful lesson is architectural: the controller links measurements and operating modes, while one bidirectional converter supports both battery charging and LED operation.
For system integrators and embedded design teams, the board can serve as a starting point for understanding those interactions and identifying which functions need adaptation in another application. Battery characteristics, load requirements, charging thresholds and implementation details must be assessed against the target system rather than copied without review. The reference design demonstrates the building blocks and their coordination; application-specific engineering remains essential.