When a machine refuses to start because a door is open, waits for a clamping confirmation, or indexes the tool magazine, a PLC is usually controlling the sequence. The programmable logic controller connects the CNC system to sensors, pushbuttons, valves, contactors, and the machine's auxiliary mechanisms.
The PLC executes a program written by the machine builder. That program defines which actions are allowed, their order, and the expected response to each input. Two machines equipped with the same CNC control can therefore behave differently during a tool change, hydraulic startup, or recovery from a fault.
The PLC scan cycle
A PLC communicates with digital and analog inputs and outputs, remote I/O stations, and devices on industrial networks. Inputs report the state of limit switches, pressure sensors, panel buttons, and relays. Outputs operate solenoid valves, contactors, indicator lamps, pumps, and other equipment.
A typical scan has three basic stages: read the inputs, execute the control logic, and update the outputs. The controller repeats this process continuously. Scan time affects response speed, but the PLC does not replace the servo control loops. Motor position, velocity, and current are handled elsewhere in the control and drive system.
Even a simple command may require several checks. After the operator requests a hydraulic pump start, the PLC program can verify the emergency circuit, operating permission, fluid level, and contactor state. It then activates the output and waits for pressure to rise within a specified time. If confirmation does not arrive, the controller cancels the command and generates an operator message.
Sequencing machine mechanisms
Many mechanisms cannot be controlled with a single output. A machining-center tool change may require spindle orientation, stopping at a defined position, magazine indexing, tool unclamping, arm movement, clamping the new tool, and confirmation of every final position. The PLC advances through these steps and waits for the required feedback before continuing.
A lathe turret uses similar logic. The controller releases the clamp, starts indexing, monitors the position code, stops the mechanism, and clamps it again. The ready signal returns to the CNC only after the sequence is complete. One failed sensor can stop the whole operation even when the axes and spindle are healthy.
Other functions commonly handled by the PLC include:
- hydraulic and pneumatic systems;
- chip conveyors and coolant delivery;
- automatic lubrication;
- chucks, tailstocks, and steady rests;
- doors, guards, and stack lights;
- part loaders, robots, and peripheral equipment.
The machine builder decides how responsibilities are divided. A tool magazine, for example, may use a conventional motor controlled by the PLC, a separate positioning drive, or an axis integrated with the CNC.
How the PLC works with the NCK
The NCK, or numerical control kernel, interprets the part program, calculates the path, and coordinates the axes. The PLC handles machine logic. An interface between them carries commands, status information, and acknowledgements.
When an M03 block is executed, the numerical control recognizes the spindle-start command. What happens next depends on the machine architecture. The PLC may check operating permissions, guard status, and equipment readiness before passing the required signals. For M06, the CNC initiates the tool-change request, while the PLC runs the machine sequence and reports its completion.
SINUMERIK documentation describes this exchange through the PLC–NCK interface. Standard blocks cover functions such as machine control panel signals, messages, auxiliary functions, tool data, and high-speed data exchange. The machine builder adds the logic required by the specific machine model.
Interlocks and readiness conditions
The PLC continuously generates permissions for operating modes and mechanisms. A spindle cannot start until the necessary conditions are satisfied. Axis motion may be inhibited when an assembly is unclamped, a door is in the wrong state, or auxiliary equipment is not ready. The exact set of interlocks follows the machine design and its risk assessment.
These permissions are usually built from chains of conditions. Cycle-start permission may depend on drive readiness, hydraulic pressure, a completed tool change, and the absence of an active fault. The operator sees one resulting status, while the PLC may be evaluating dozens of individual signals.
Effective troubleshooting identifies the first missing condition. Forcing an output or overriding an input can hide the original fault and create a hazardous state. Checks should follow the electrical drawings, signal list, PLC diagnostics, and the machine builder's procedures.
Standard control logic and functional safety
Not every interlock is a safety function. Standard PLC logic may prevent an incorrect machine sequence or protect a workpiece. Functions that control risk to people require a certified safety architecture with suitable inputs and outputs, a safety PLC, safe drive functions, and an appropriate engineering process.
SINUMERIK ONE integrates a SIMATIC S7-1500F. Siemens states that PLC and Safety engineering are performed in TIA Portal, with a failsafe program used to implement safety logic. This does not make every bit in a standard PLC program safety-rated. Emergency stops, guard monitoring, and functions such as Safe Torque Off must comply with the machine's safety design and applicable requirements.
Changes to a safety program require the appropriate competence, verification, and documentation. Bypassing a protective function to keep production running is unacceptable. Even a temporary jumper changes machine behavior and may defeat the intended level of protection.
Why the same command behaves differently
G- and M-codes provide a common basis for machining programs, but machine builders define the implementation of many auxiliary functions. M08 normally requests coolant, yet one machine may select a pump, open a valve, check tank level, and wait for flow confirmation. Another may simply energize one output.
User-defined M functions depend even more heavily on the PLC program. They may operate a clamp, air blast, bar feeder, or measuring device. The command number alone does not describe the sequence, so its purpose must be checked in the documentation for that specific machine.
For the same reason, copying a PLC program between similar machines is risky. I/O addresses, sensor types, timers, valve logic, and the CNC interface structure may differ. Even a small hardware variation requires the program to be reviewed and tested.
Troubleshooting PLC logic methodically
The first useful clue is the message displayed on the HMI. PLC-generated messages often identify the missing condition directly: pressure not reached, magazine away from its home position, or guard not locked. The next step is to check the physical mechanism and the corresponding input signal.
With online diagnostics, a qualified technician can trace the logic from a command to its output and from a sensor to the internal condition that uses it. Symbol tables, cross-references, PLC–NCK interface status, and event logs are especially useful. Looking only at an output is insufficient because the output may correctly remain off when an enabling input is missing.
A backup should be made and the project version confirmed before editing the program. Changing a timer or contact without checking every reference can affect another operating mode. Machine-builder blocks may also be protected, and access to the safety program is normally controlled separately.
The PLC turns CNC commands and operator actions into coordinated machine behavior. It reads signals, runs sequences, creates interlocks, and exchanges status with the NCK and HMI. When a machine waits for confirmation or refuses to start a device, understanding the PLC logic helps locate the missing condition instead of changing motion parameters at random.