Why PicoLC Exists
PicoLC grew out of years of working with control systems and repeatedly seeing the same gap. Traditional PLCs are reliable, but often expensive and restrictive. Maker boards are flexible and affordable, but usually need additional hardware before they are ready for real control work.
I wanted something in between: a controller I would actually choose for my own small automation projects. It needed to be approachable, open, and programmable in familiar ways, while still being designed for real wiring, real loads, and dependable operation.
PicoLC is my attempt to build that missing middle—a practical controller that is easy to start with, capable enough to keep using, and designed to grow with the project.
Where PicoLC Is Going
PicoLC is intended to grow beyond a single controller into a flexible family of compatible devices. Different projects need different combinations of digital I/O, analog signals, networking, and local interfaces, but they should not require starting over each time those needs change.
The long-term vision is a modular platform built around a common programming model and an expandable field bus. A small project might begin with one controller, then add remote I/O, analog capability, Ethernet, wireless connectivity, or a dedicated interface as the system grows.
The goal is not to make one board that does everything. It is to create a practical set of building blocks that work together, remain understandable, and let users expand a project without discarding what they already have.
