The EQSP32 is programmed in C/C++ with the tools millions of developers already use. The EQSP32 library handles the industrial plumbing, EQ-AI writes hardware-aware code from your description, and you build in the Arduino IDE or VS Code with PlatformIO. USB-C or OTA to flash. That is the whole chain.
Every PLC runtime has a ceiling: the day your application needs a custom protocol, a REST API, a cloud service, or on-device intelligence, the runtime cannot express it. C/C++ has no such ceiling. It is the language operating systems and flight controllers are written in, and on the EQSP32 it comes without the embedded learning curve, because the library does the hard parts and the AI writes the code with you, or for you.
C/C++ also opens the door to the ESP32’s open-source ecosystem. Every name below is a real runtime, platform, protocol, device driver, or tool that runs on the EQSP32 today, free and open source. And they are only a small sample of a massive resource: an ecosystem no PLC vendor can match.
EQ-AI bridges automation logic and embedded code. Describe your logic in the terms you already know, ladder rungs, sequential steps, or plain English, and EQ-AI generates hardware-aware EQSP32 code using the correct pins, modes, and library functions.
Tell EQ-AI what you need in plain English. “Read pressure on analog input 3, open valve 5 when it exceeds 4.5 bar, and log every event via MQTT.”
EQ-AI produces optimized, hardware-aware code that correctly addresses every pin, register, and library call. You stay in control: read it, adjust it, or ask for changes.
Compile in the Arduino IDE or VS Code and upload via USB-C or OTA. Your automation is live in minutes, not weeks.
Opens in ChatGPT. A free account is all you need.
Want the AI to do all of it? With Agentic Hardware-in-the-Loop, an AI agent writes, flashes, and validates the entire application on the real controller, unattended. See how Agentic HIL works →
Wi-Fi, MQTT, time sync, OTA updates, and all 16 I/O channels are handled before you write your first line of code.
A typical MicroPLC has no Wi-Fi, no MQTT, no time sync, and no smartphone interface. A generic dev board has all the hardware but ships with zero software. The EQSP32 library fills both gaps.
The EQSP32 library is a complete industrial firmware stack. It handles Wi-Fi with automatic reconnection, a BLE provisioning interface, an MQTT client with authentication and Home Assistant auto-discovery, NTP time sync with DST-aware timezone rules, I/O abstraction across all 16 ADIO channels and any connected expansion modules, RS232/RS485/CAN bus, and OTA firmware updates. Everything runs in the background. The developer writes machine logic: read a sensor, drive an output, make a decision. The library takes care of the rest.
In the field, the EQConnect app supplies the parameters the library cannot know at compile time: network credentials, MQTT broker address, timezone, and static IP for each installation. The same firmware binary runs on every site.
The result: a controller that connects to the network, syncs time, publishes to MQTT, and exposes every I/O channel and expansion module to Home Assistant or any MQTT client, from a single call to eqsp32.begin(). No MicroPLC offers this. No dev board includes it.
What the library gives you
Single call to eqsp32.begin() initialises the full stack. Power supply supervision. OTA firmware updates over Wi-Fi. Buzzer output.
Digital in/out, PWM, analog input (mV), NTC temperature, 4–20 mA, debounced switch, relay with soft-start, pulse counter. All 16 channels, one API.
NTP-synced local time with full DST support. Read hour, minute, weekday, month, or day-of-year directly. Built-in non-blocking timers. No RTC chip required.
Wi-Fi and Ethernet with automatic reconnection. MQTT client with authentication. Home Assistant auto-discovery. Built-in web server. BLE serial interface.
RS232 and RS485 (switchable). CAN bus to 1 Mbps with ID filtering. Modbus over RS485 and TCP/IP.
Daisy-chained expansion modules are auto-detected and initialised at startup. Managed with the same I/O API as local channels.
A simple, complete, end-to-end development toolchain, totally free of charge. And it is the same chain an AI agent drives autonomously in Agentic HIL.
Plain English into EQ-AI, or write the code yourself
Compile in the Arduino IDE or VS Code with PlatformIO
USB-C on the bench, OTA anywhere in the world
Wi-Fi, MQTT, and timezone set on site with EQConnect
Live I/O on your phone with EQMonitor, or any MQTT client
EQSP32 projects build identically in both environments. Pick the one that matches how you work today; switching later costs nothing, because the sketch and the library do not change.
Install the EQSP32 library from the built-in Library Manager, open a sketch, press upload. The environment millions of developers already know, with zero project configuration.
A full engineering IDE: multi-file projects, IntelliSense, integrated Git, and per-project dependency management. Your project file pins the exact library versions, so every teammate and every build server compiles the same firmware.
The library is free, the AI assistant is free, and both IDEs are free. The only thing you need is an EQSP32.