Blynk.NCP is a solution that off-loads connectivity to a Network Co-Processor (NCP) while your application logic resides on the Primary MCU. This implies a dual-Microcontroller Unit (MCU) architecture.

Read more about Blynk.NCP

This example project is compatible with a set of ready-to-use Dual-MCU boards:

🔄 Over-the-Air Updates, 🌐 Connectivity, ⚙️ Provisioning, 🗃️ File System

You can also add one of the supported connectivity modules to your custom board.

1. This is a PlatformIO project. Please install the VSCode plugin or PlatformIO CLI.

2. Clone this repository using git or download it as a ZIP file.

3. Flash the Blynk.NCP firmware (replace nano33iot with your board type):

   pio run -e nano33iot -t upload_ncp

4. Open src/main.cpp and fill in information from your Blynk Template:

   #define BLYNK_TEMPLATE_ID           "TMPxxxxxx"
   #define BLYNK_TEMPLATE_NAME         "MyDevice"

5. Upload the example project and run the serial monitor:

   pio run -e nano33iot -t upload -t monitor

6. Use the Blynk iOS/Android app to configure your new device.
   Ensure that the Blynk App is installed on your smartphone.
   Open the Blynk App -> click Add New Device -> select Find Devices Nearby

If something doesn't work, try some of these solutions:

• If your board is based on a Raspberry Pi RP2040 chip, it may fail to work on Windows. Please apply this fix
• On TTGO T-Pico C3, you may need to connect IO9 pin to GND to flash the NCP firmware
• Upgrade PlatformIO to the latest version. Run: pio upgrade
• Upgrade packages to the latest version. Run: pio pkg update --no-save

Issues are maintained in the Blynk NCP Driver repository.

The community edition of Blynk.NCP is available for personal use and evaluation.
If you're interested in using Blynk.NCP for commercial applications, feel free to contact Blynk. Thank you!