PLC Programming Software: Which Tool Works with Your Controller?

Hello and welcome,

The term PLC program can refer to two things: the programming software installed on a computer and the control application running inside the controller. The software is where you define when a motor should run, how sensor signals should be evaluated and what the machine should do when a fault occurs. You then transfer that application to the PLC through a supported connection.

Choosing a tool starts with the exact CPU model and the software versions it supports. A PLC programming environment usually handles more than code editing: it also provides hardware configuration, communication settings, online monitoring and debugging. The right package must match both the controller and the project you intend to maintain.

What should you check before choosing software?

Identify the controller's complete model number, CPU family and, where available, its firmware version. One manufacturer may offer several generations of controllers with different engineering tools and project formats. Check the supported operating system, required license edition, connection drivers and compatibility with the installed modules.

For an existing machine, find out which software version created the original project. Installing the newest release does not guarantee that an older project will open without changes. Keep an untouched copy before converting or upgrading a project: the converted file may no longer open in the earlier software version.

Siemens: TIA Portal and STEP 7

TIA Portal is Siemens' integrated engineering environment, with SIMATIC STEP 7 providing PLC programming. S7-1200 and S7-1500 are key controller families used with this environment. Existing S7-300/S7-400 installations may use classic STEP 7 projects; supported CPUs can also be engineered in suitable TIA Portal versions. Choose the tool by the CPU's exact order number and the project's engineering history. For older connection interfaces, see the Siemens PLC cables section.

Allen-Bradley: Studio 5000, RSLogix and Micro800 tools

Studio 5000 Logix Designer is the main programming application for ControlLogix and CompactLogix systems. Older projects may refer to RSLogix 5000. The SLC 500 and MicroLogix families use RSLogix 500. RSLogix 500 and RSLogix 5000 target different controller families.

For Micro800 controllers, Connected Components Workbench is a widely used engineering environment. Rockwell also offers FactoryTalk Design Workbench tools for Micro800 projects. Check the supported controller list, existing project format and firmware compatibility before choosing an environment for a particular Micro800 installation.

Schneider Electric: Distinguish three engineering environments

Modicon M221 uses EcoStruxure Machine Expert Basic; M241, M251 and M262 use EcoStruxure Machine Expert; and M340 and M580 use EcoStruxure Control Expert. Older documentation may use the names SoMachine Basic, SoMachine and Unity Pro. Identify the associated controller family before choosing an installer. Here, Basic identifies a separate environment for particular controllers, rather than simply a reduced license edition of Machine Expert. For the connection hardware, see Schneider PLC cables.

Mitsubishi Electric: GX Works2 and GX Works3

GX Works3 is used with MELSEC iQ-R and iQ-F controllers. GX Works2 is used with MELSEC-Q, L and supported FX models; older installations may also have GX Developer projects. GX Works3 is not a universal programming tool for every earlier Mitsubishi PLC. Verify CPU support and project conversion requirements, and check the Mitsubishi PLC cables section for the physical interface.

Omron: CX-Programmer and Sysmac Studio

CX-Programmer, included in the CX-One suite, is an important tool for CS, CJ and CP controllers. Sysmac Studio is used for NJ/NX controllers and applicable NY control systems. Searching for “Omron PLC software” is therefore only a starting point. Distinguishing the conventional PLC family from the Sysmac controller family helps you choose the correct environment.

Choosing software for ABB and DERELL controllers

Automation Builder is the engineering environment for the ABB AC500 family. It can also provide configuration tools for supported devices within an automation project. Available capabilities depend on the controller generation, software version and license.

For DERELL controllers, use the Derell Logic Editor specified in the relevant series documentation, together with the supported connection method. When working with a DLC-K or DLC-R controller, identify the complete model first. Do not assume that an editor supplied for one series supports every DERELL controller.

Can CODESYS program every PLC brand?

CODESYS is a development platform used by compatible controllers from different manufacturers. It cannot program every PLC. The target needs suitable runtime support, a device description and any required manufacturer packages. Even a controller built around CODESYS technology may require a manufacturer-specific installation. See CODESYS hardware requirements for more on the distinction between the engineering environment and its target device.

The CODESYS Development System is free to use, but that does not make every runtime license or optional engineering tool free. Obtain the software from official sources and select the appropriate packages; our CODESYS download guide explains the starting points.

Is programming software the same as a programming language?

The software is the environment in which you build the project; the language is how you express the control logic. Ladder Diagram (LD) uses contact and coil logic, Function Block Diagram (FBD) connects function blocks, and Structured Text (ST) uses text-based expressions and statements. Sequential Function Chart (SFC) helps organize sequential operations through steps and transitions. Support varies by controller and software package; see our PLC programming languages guide.

The software is installed, but the PLC will not connect

The correct engineering package is only part of the connection. The programming port, cable interface, USB driver, serial settings or Ethernet address must also match the controller. Some PLC programming cables look similar while using different electrical interfaces. A connector that fits does not prove that a cable is compatible. Verify the connection settings and selected CPU before treating a communication failure as evidence of a faulty PLC.

Simulation, online monitoring and debugging

Simulation helps test supported control functions without a physical PLC. Online monitoring shows actual variables in a connected controller. These are different activities. A program that works in a simulator still needs its input and output modules, address mapping, timing and field connections checked on the real system.

During PLC debugging, trace the signal through the application: does the input arrive, are the required conditions satisfied, and is the output command issued? Forcing can cause machine movement or override normal application logic. Do not apply forces casually to a running machine. CODESYS users can also consult our CODESYS debugging guide.

Does reading a program from the PLC create a complete backup?

Not necessarily. What you can retrieve depends on the controller, access protection and whether source files were stored on the device. Even when executable logic can be read, variable names, comments, some libraries or the original project structure may be missing. The most useful backup is the original engineering project, verified against the application actually running in the machine.

In many environments, upload means reading from the PLC to the computer, while download means writing from the computer to the PLC. Confirm the transfer direction in the software interface. Before writing, establish a backup plan for the project, parameters, hardware configuration and required retained values. Also check how the new application behaves when entering RUN and when power returns.

Can the same project be transferred to another PLC brand?

Different PLC brands may share programming concepts, but their projects usually cannot be loaded directly into one another's controllers. Addressing, data types, timer behavior, task execution, libraries and hardware functions can differ. A common programming language does not guarantee project compatibility. Migration involves adapting the control logic and validating it on the target controller.

Can an HMI or SCADA application replace the PLC program?

An HMI provides operator screens, while SCADA supports functions such as supervision, alarms and data collection. Exchanging data with a PLC does not mean these applications share the same project or execution environment. Screen design and machine control logic need separate consideration. Our guide to the relationship between PLCs and SCADA explains how they work together.

What makes a suitable first project?

Choose the environment supported by your controller, then start with a small application in which one input controls one output. Add a timer, counter and alarm condition as your understanding grows. Use meaningful variable names, add short comments and establish good project management habits from the beginning. For a CODESYS learning path, see PLC programming with CODESYS and the available training resources.