Blynk.NCP overview
Blynk.NCP is a software 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.
Using Blynk.NCP is recommended if one of these is true:
- You're building a new IoT product with specific requirements for the Primary MCU, so you're adding a separate connectivity module
- You are using Blynk for retrofitting your existing products
- You have included an AT command-based module, but you struggle to make it work right or to achieve your product goals
Blynk.NCP allows to immediately have access to Blynk’s advanced features - such as device provisioning, OTA firmware updates and others - using the hardware of your choice, which reduces integration efforts, time to market, and improves reliability of your products.
- Blynk.Inject: connect your devices easily using Android App, iOS App or Web Dashboard
BLE-assisted device provisioning for the best end-user experienceWiFiAP-based provisioning for devices without BLE support
- Network Manager:
- WiFi (up to 16 saved networks), Ethernet, Cellular (depending on the hardware)
- Advanced network connection troubleshooting
- Secure Blynk.Cloud connection that provides simple API for:
- Data transfer with Virtual Pins, reporting Events, and accessing Metadata
Time,TimezoneandLocation, with an ability to track local time when the device is offline, including DST transitions
- Blynk.Air - Automatic Over The Air firmware updates using Web Dashboard
- Both NCP and the Primary MCU firmware updates
- Direct firmware upgrade using iOS/Android App, before device activation
- Connectivity-related device state indication - requires a monochrome/RGB/addressable LED attached to the NCP
- User button (also used for configuration reset) - requires a momentary push button attached to the NCP
- Factory testing and provisioning
Blynk team is now working on a range of complementary features that will be available with Blynk.NCP, persistent automation scenarios, non-volatile storage for Preferences library, and generic UDP/TCP/TLS socket API being among them.
To enable a seamless connection and advanced Blynk’s functionality, add one of the supported connectivity modules to your hardware as a Network Co-Processor. We’ve prepared an example that includes firmware and will help you set up the communication between your hardware and Blynk with minimal effort.
If you are using one of the following dual-MCU boards: UNO R4 WiFi, Portenta C33, Nano RP2040 Connect, Nano 33 IoT, MKR WiFi 1010, T-PicoC3, or RPi Pico + ESP8266, you can use this Blynk.NCP example to set up communication with the platform within minutes.