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.
This example project is compatible with a set of ready-to-use Dual-MCU boards:
Board | 🔄 MCU / NCP | 🌐 | ⚙️ | 🗃️ | |
---|---|---|---|---|---|
UNO R4 WiFi | unoR4wifi |
✅ / ✅ |
WiFi 2.4 | BLE | 4.25 MB |
Portenta C33 | portentaC33 |
⏳ / ✅ |
WiFi 2.4 | BLE | 512 KB |
Nano RP2040 Connect | rp2040connect |
✅ / ❌ |
WiFi 2.4 | BLE | 384 KB |
Nano 33 IoT | nano33iot |
✅ / ❌ |
WiFi 2.4 | BLE | 384 KB |
MKR WiFi 1010 | mkrwifi1010 |
✅ / ❌ |
WiFi 2.4 | BLE | 384 KB |
T-PicoC3 | t_pico_c3 |
✅ / ✅ |
WiFi 2.4 | BLE | 512 KB |
RPi Pico + ESP8266 | pico_esp8266 |
✅ / ✅ |
WiFi 2.4 | WiFiAP | 1000 KB |
Wio Terminal | ⏳ |
✅ / ❔ |
WiFi 2.4/5 | BLE | ❔ |
🔄 Over-the-Air Updates, 🌐 Connectivity, ⚙️ Provisioning, 🗃️ File System
You can also add one of the supported connectivity modules to your custom board.
-
This is a PlatformIO project. Please install the VSCode plugin or PlatformIO CLI.
-
Clone this repository using
git
or download it as aZIP
file. -
Flash the Blynk.NCP firmware (replace
nano33iot
with your board type):pio run -e nano33iot -t upload_ncp
Warning
This overwrites both the Main MCU and the connectivity module firmware.
You can restore the stock firmware easily.
-
Open
src/main.cpp
and fill in information from your Blynk Template:#define BLYNK_TEMPLATE_ID "TMPxxxxxx" #define BLYNK_TEMPLATE_NAME "MyDevice"
-
Upload the example project and run the serial monitor:
pio run -e nano33iot -t upload -t monitor
-
Use the Blynk iOS/Android app to configure your new device.
Ensure that the Blynk App is installed on your smartphone.
Open theBlynk App
-> clickAdd New Device
-> selectFind 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 connectIO9
pin toGND
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!