Skip to content

Logic · Signals · Equipment

ProgrammingPLC systems

The PLC program is the brain of the machine.

I develop the logic that connects sensors, drives, mechanisms and HMI into one functioning system. From new software to extending and modernizing an existing installation.

Siemens is my core expertise. Other industrial controllers are considered according to the task and the available project.

Control cabinet of the packaging line in Izhevsk, with controller, signals and drives
Izhevsk · Case 003Behind every program is a real installation.
Clear structure
Defined sequences
Documentation and handover

01 / The task

New logic. Existing systems, developed further.

  1. New software

    Developing the PLC architecture, operating algorithms and interaction between units from the task specification and electrical drawings.

  2. Project extensions

    New functions, extra signals, operating modes and interfaces — taking the current behavior of the equipment into account.

  3. Migration and modernization

    From Siemens S5 / STEP 5 or STEP 7 Classic to a new system: reviewing functions and hardware, and reworking the program where needed.

02 / Why control logic matters

Good mechanics cannot compensate for poor software.

Quality sensors, modern drives and a well-built control cabinet do not guarantee stable operation on their own. The program determines when mechanisms start, which conditions must be met and how the machine responds to deviations.

For me, PLC programming is more than writing code. It is developing the logic of the entire installation.

The PLC at the center

HMI / SCADAOperator commands · states
SensorsDigital and analog signals
PLCSignals → decision → command
DrivesCommands · mechanisms
InterlocksConditions · permissives · responses
AlgorithmModes · sequences · PID
EquipmentCoordinated operation of the installation

Signals. Conditions. Decisions. Actions.

A conceptual interaction diagram, not an electrical wiring diagram. HMI and SCADA exchange data with the PLC. Sensors send signals to the PLC, which sends commands to drives. The program processes process interlocks and algorithms that determine how the equipment operates.

What well-structured software supports

  • Stable equipment operation
  • Clear fault diagnostics
  • Straightforward operation
  • A foundation for modernization
  • Faster fault-finding
  • Defined process interlocks
  • Less time spent on later service

Process interlocks in a PLC do not replace dedicated safety functions. Their requirements and implementation must be defined for the specific installation.

03 / Platforms and integration

Siemens at the core. The task goes beyond one brand.

My deepest experience is with Siemens. Additional platforms are shown through real projects; other systems are assessed after reviewing the equipment, software and project information.

Core expertise

Siemens SIMATIC

Development, extensions and modernization of Siemens programs: from existing S5 / S7 systems to current controllers in TIA Portal.

  • STEP 5
  • STEP 7 Classic
  • TIA Portal
  • S5
  • S7-300
  • S7-400
  • S7-1200
  • S7-1500
  • ET 200

Additional project experience

CODESYS and Schneider

OWEN PLC210 · CODESYS V3.5

A programmable Modbus RTU / TCP gateway between TPEM and Siemens S7-1500.

Case 006

Schneider Electric · PacDrive

Project work and diagnostics in SoMachine Motion Logic Builder.

Case 008

System integration

Beyond the controller

Connecting the program to HMI / SCADA, WinCC, operator panels and IPC-based visualization. Device communication through the interfaces specified for the project.

  • HMI / SCADA
  • WinCC
  • Panels
  • IPC
  • PROFINET
  • PROFIBUS
  • Modbus RTU
  • Modbus TCP
  • CAN
  • OPC

Unity Pro / Control Expert and other systems: considered project by project after reviewing the controller, software versions and access.

04 / Scope of work

From individual signals to coordinated operation.

Modes, commands and transitions should be understandable not only to the programmer, but also to the specialist who will maintain the equipment.

  1. Program architecture

    Structure by machine unit, clear interfaces, names and comments. A basis for maintenance and future extensions.

  2. Signals and mechanisms

    Digital and analog inputs, state processing and control of motors, valves and actuators.

  3. Modes and sequences

    Manual and automatic operation, step sequences, permissives, interlocks and responses when conditions are not met.

  4. Drives and control loops

    Frequency converters, servo drives, setpoints and feedback. Control loops and PID according to the process requirements.

  5. HMI, communication and diagnostics

    Visualization data, industrial communication, alarms and messages that make the equipment state understandable.

  6. Testing and handover

    Checking algorithms before start-up and on the equipment. Current project files, explanations, drawings and documentation within the agreed scope.

Roller conveyors and chipboard packages on the automatic packaging line in Izhevsk

05 / Real software — real production

Packaging line in Izhevsk.

Case 003 included PLC development in TIA Portal, a Siemens HMI and PROFINET communication. The logic connects conveyors, a turntable and signal exchange with another production line.

The line was commissioned, its operating modes were tested, and documentation and an operator manual were handed over.

SIMATIC · TIA Portal · HMI · PROFINET

06 / Before we start

Questions about PLC programming.

Do you only program Siemens?

Siemens is my main focus. I also have a project using OWEN PLC210 in CODESYS V3.5 and experience with Schneider PacDrive in SoMachine Motion. Unity Pro / Control Expert and other platforms are considered after reviewing the task, controller, software and access.

Can an existing program be extended without replacing all the hardware?

I first review the project, electrical drawings and equipment functions. If the software and hardware remain suitable, we can make targeted changes. For S5 / STEP 5 or STEP 7 Classic migrations, compatibility and necessary changes to the logic are assessed separately.

What information helps you assess a project?

A brief description of the equipment and the required result. Drawings, an I/O list, the PLC type, the existing PLC/HMI project and drive information are useful. We can still discuss the task even if some documents are missing.

Can programming and support be provided remotely?

Yes, where suitable access to the project and equipment is available. On-site checks and physical work are carried out by qualified personnel at the installation. We agree the remote-work and commissioning arrangements beforehand.

What does the customer receive at completion?

The current project version and the agreed documentation: logic and parameter descriptions, drawings, backups and operating information. Commissioning, operator training and further support depend on the scope of the project.

How should your equipment work?

Describe the equipment, the current task and the required outcome. I will review the available information and propose an approach to developing or extending the program.

Wladimir Poljakov · Poljakov Automation