Every safety function must be explicit. Every path from sensor to output must be traceable. The software doesn’t just let you build; it watches you. Mismatched data types? It will tell you. A feedback loop that bypasses a safety condition? It will refuse to compile. In this way, the tool becomes a silent second pair of eyes—a co-pilot who has memorized EN ISO 13849-1 and won’t let you cheat. Under the hood, Flexi Soft is a modular system: a head unit (CPU) plus expansion modules for inputs, outputs, relays, and communication (EtherNet/IP, PROFINET, PROFIBUS, etc.). Flexi Soft Designer manages this hardware puzzle effortlessly. You define your module arrangement in a rack view, and the software automatically assigns addresses, checks power budgets, and validates cross-module wiring.
At first glance, it is a piece of configuration software—unassuming, icon-driven, and structured. But spend an afternoon with it, and you realize it is less a utility and more a translator. It sits in the gap between the chaos of a production line and the rigid, unforgiving logic of a safety-rated controller. Opening Flexi Soft Designer feels like stepping into a clean, well-lit drafting room. The main workspace is a grid of possibility. On the left, a library of function blocks waits: emergency stop monitoring, safety mats, light curtains, two-hand controls, muting, bypass, OSSD outputs. These aren’t just symbols. They are hardened, certified pieces of logic (up to SIL 3 / PL e) that you drag and drop like a child playing with building blocks—except these blocks, if arranged incorrectly, could stop a 10-ton press at the wrong moment. flexi soft designer
from SICK is that tool.
For the controls engineer standing inside a dusty panel, laptop balanced on a toolbox, debugging a muting error at 2 AM, Flexi Soft Designer is not software. It is a lifeline. Every safety function must be explicit