Machine safety requirements can change as equipment grows from a standalone machine into a more complex line. Modular safety controllers address this challenge by bringing multiple safety functions into a configurable system that can expand with the application. For machine builders and system integrators, the approach can help coordinate safety inputs, outputs, speed monitoring and diagnostics while keeping the architecture aligned with the machine’s needs.
The Modicon MCM system is one example of this modular approach. Its controller can operate independently or connect to expansion modules, with configuration handled in SoSafe Configurable software. Understanding how the system is structured—and where safety-related and standard communications differ—helps engineers assess its fit during machine design.
How modular safety controllers support machine design
A modular controller monitors safety functions intended to reduce the risk of people reaching hazardous moving parts. Typical applications include emergency stops, guard monitoring, perimeter guarding, position monitoring, speed monitoring and enabling movement. Rather than assembling a separate safety module for each function, designers can configure related functions in one system and select hardware to match the required I/O and machine layout.
The MCM controller CPU includes safety digital inputs and safety outputs. It can be used as a standalone device for a smaller application, or expanded with compatible modules. The catalog describes configurations ranging from a CPU with eight safety inputs to systems with up to 128 inputs, 16 dual outputs or 32 single-channel outputs, alongside diagnostic status outputs. Actual capacity depends on the selected CPU and expansion configuration.
This lets the design begin with a smaller hardware arrangement and add capacity when more safety functions or machine sections need to be monitored. A tailored module layout can also help reduce components, cabinet footprint and wiring compared with a collection of separate safety modules. These outcomes depend on the application and the resulting design.
Building a safety architecture from modules
The system includes several types of hardware, each serving a distinct role in the safety architecture:
- Safety controller CPUs execute the configured safety logic and can operate alone or with expansion modules.
- Safe I/O modules provide digital or analog inputs, solid-state outputs and mixed input/output combinations. Inputs and outputs can be configured to suit the application, with options such as line monitoring, filters, delays and diagnostic signals.
- Safety relay output modules provide forcibly guided relay contacts. Some connect directly to selected outputs; others connect through the expansion bus and provide independent safety relay outputs.
- Safe speed monitoring modules monitor conditions such as zero speed, limited speed, speed range and direction. Depending on the module, inputs support proximity sensors or HTL, Sin/Cos and TTL encoders.
- Communication modules support either safety-related communication between distributed safety sections or non-safety-related fieldbus and network communication.
Choosing modules is not simply a matter of counting terminals. Designers need to check compatibility between the CPU and expansion modules, identify the required safety functions, and distinguish safety-related communications from standard diagnostics or network data. The catalog notes that some expansion modules are compatible only with particular controller CPUs.
Distributed safety I/O and communication
When safety devices are spread across a machine, placing all I/O beside the controller may create unnecessary wiring or constrain cabinet locations. MCM safe communication expansion modules can connect remote safety-related islands to a CPU using shielded RS-485 cable. The catalog specifies up to five decentralized islands, with up to 50 m between two safe communication modules and a total network length of up to 250 m.
Remote expansion modules can be arranged in line or tree configurations. The system recognizes the architecture through module addressing, so the order of safe expansion modules on the backplane is not important. These details can help integrators plan cabinet placement and cable routing, but the complete design still needs to account for the specific machine layout and applicable safety requirements.
Safety-related communication should not be confused with the system’s non-safe communication options. Non-safe modules provide connections for machine fieldbuses and networks, including CANopen, Profibus DP, Modbus Serial, EtherCAT, Modbus TCP, Ethernet/IP and PROFINET, depending on the module. These connections support diagnostics and data communication; they do not replace the safety-related communication architecture.
Configuring, validating and maintaining the system
SoSafe Configurable provides a drag-and-drop function-block approach to building a safety configuration. Users define the hardware, assign inputs and outputs, and configure safety and logic functions. The software also supports offline simulation, online visualization and monitoring, configuration validation, hardware scanning, and printable schematics and documentation.
These tools connect design work with commissioning. Offline simulation gives engineers a way to review configuration behavior before deployment, while online visualization and testing support checks during setup. Project documentation can help with wiring and safety calculations. Software tools support the engineering process, but they do not remove the need to validate the complete machine safety design.
Maintenance features are also part of the system. A removable memory card can store configuration data for transfer to a replacement controller without using a PC. The controller also records recent configuration modifications in a log, and diagnostic information can be accessed through communication connections or a PC USB connection. This can help technicians investigate system status and restore a configuration during service.
Certification and application-level responsibility
The MCM system is certified by TÜV SÜD to Category 4, PL e under EN/ISO 13849-1 and SILCL 3 under the standards identified in the catalog. These are system-level certification claims, not a substitute for assessing the complete machine. The safety functions, selected components, wiring, configuration and validation all contribute to the final application’s safety performance.
Machine builders should therefore define hazards and required safety functions first, then select a CPU, I/O and communication arrangement that supports those needs. The chosen design must be checked against relevant standards and validated for the finished machine.
Practical implications for machine builders
Modular safety controllers offer a way to organize multiple machine safety functions in an architecture that can range from standalone control to distributed I/O. The practical value lies in matching the hardware to the application: expanding I/O where needed, adding speed monitoring for relevant axes, separating safe communication from standard networking, and using configuration and diagnostic tools to support commissioning and maintenance.
For engineers and technical decision-makers, the key is to treat modularity as a design option—not as a shortcut around safety engineering. Careful compatibility checks, deliberate network and cabinet planning, and validation of the complete machine remain essential to achieving the intended functional safety.