Codesys Hardware Configuration

[Dallas Querry]

RequirementYou have a standard project in whose device tree the hardware environment is shown with a PLC and a parameterizable device. On the controller there is a file IoConfig.par, in which the device parameters were previously saved with the current values.

Observe the Variable column with the display of the device input channels and device output channels , which can still be sorted by organizational nodes , depending on the device. We assume that there is a device input of the type BYTE. It is displayed with its individual bit addresses (bit channels) below the BYTE node.

Note: When mapping structured variables, the editor prevents you from entering both the structure variable (example: %QB0) and individual structure elements (example: %QB0.1 and QB0.2). Therefore, if there is a main entry with a subtree of bit channel entries in the mapping table, then the following applies: Then you can specify a variable either into the line of the main entry, or into the lines of the subelements (bit channels), but not into both.

You can now occupy either the entire channel with a variable of a suitable type OR its individual bit-channel addresses with suitable variables of the type BOOL or BIT. First of all, double-click a bit input channel in the Variables column.

In order to place an existing variable on the channel, you must enter the desired project variable with the complete path. Press FPNG72/_cds_icon_three_dots.png to open the Input Assistant. Select, for example, the variable Application.PLC_PRG.xBool4 declared in PLC_PRG.

Note: For compiler version V3.5 SP11 and later, the initialization value of the variables is used automatically as the default value when mapping to an existing variable. You can edit the Default value field only if you map to a new created variable or if no mapping is specified. In older versions, users had to specify explicitly that the default value and initialization value were identical.

Requirement: A device that supports an I/O mapping configuration in CODESYS is inserted in the device tree of your project. On the I/O Mapping tab in the device editor you will thus see a tabular display of the input and output channels of the device with specification of the addresses and data types.

A device with a digital output that supports FB mapping is linked in the project. There is a function block Scale_Output_Int with the following implementation. The attributes of the function block itself and before the output parameter with which the channel output is processed are important.

These variables are available in the input assistant in the category Variables / IoConfig_Globals_Force_Variables. You can use them in CODESYS in programming objects, in visualizations, in the symbol configuration, etc.

Scanning is started with the command Scan for Devices. It refers to the controller that is currently selected in the device tree and linked to the project. For example, you can select an inserted PROFINET IO controller and use the command to determine the I/O devices and I/O modules assigned to it.

You create an implicit application with the command Online configuration mode in the context menu of the PLC object in the device tree. CODESYS automatically loads the application to the PLC and, via the application, automatically initializes all I/Os once. The application is called HiddenOnlineConfigModeApp. It is displayed in the device editor of the PLC in the Applications tab. You can use it to operate the I/Os with the following functions as in normal online mode:

Requirement: you have created a standard project with a device configuration in which you have configured an I/O mapping. In a program block you make read or write accesses to inputs or outputs of the hardware in order to check their wiring. The connection to the PLC of the hardware is configured in the communication settings. The PLC is running.

Requirement: there are already one or more applications on the target device. The target device supports the advanced online configuration mode. You have opened the project containing these applications. You wish to look at the device parameters without having to log in to the controller. The connection to the PLC of the hardware is configured in the communication settings. The PLC is running.

Start the search by actuating the button Scan for Devices. In the list of the devices found, select the device whose configuration settings are to overwrite those existing in the project. Click on the button Copy to project.

I have a Beckhoff CX5130 which I want to run Codesys 3.5 runtime on. I got a bunch of DI/DO/AI/AO modules as well. I know from WAGO PLC that I need to use the WAGO configuration tool on the I/O modules before loading the codesys runtime intot he WAGO PLC, but what is the sequence of work needed for a Beckhoff PLC?

Looking at the First Steps for RTE PDF the backplane communication for the CX is Ethercat. You need to install some drivers and do some things, definately read the PDF. From reading just that PDF to me it looks like you use the device tree to add an internal Ethercat Master and then you add your IO devices to that.

Thanks for the pointers on how to attack this the easiest way, I can confirm that it was indeed just to install the RTE from the package downloaded to the CX controller, cx5000 driver installed automatically and configuration was easy.

I currently use CodeSys SPRTE in our substations. It runs on a Schweitzer 3351. We are trying to figure out a reliable way for backing up these systems. We have finally found what seems to be a simple reliable way except for one problem. The 3351 Schweitzers hard drive is an 8 Gig Compact Flash drive. We use an imaging software to create an exact image of the drive to be put into another 3351 in the event of a failure. Everything copies perfectly except CodeSys reverts back to Demo mode and will not let us access the 3s license manager. Instead it gives us an error stating that " The unique system ID does not match with LMAPI database. This might be the case if your hardware configuration has changed." Has anyone else encountered this problem or does any use this same type of set up with a better means of back-up

Your license file is hardware dependent and cannot be transferred. For a backup system you would probably need another license, but you could also consider a hardware lock (USB plug with license) which can easily be transferred.

I have exactly the same problem, after replacing hard disk with another one for improve capacity.

I done an image of the old hard disk.

Codesys is working, but only in demo mode.

I tried to reinstall, also after cleaned all codeys files, but nothing..

Wago codesys is free.

There is no active licenses with it.

I can install the wago codeys in more than one machine.

I tried to install my codesys in another machine and it work fine.

The problem is located in MY machine, I think after the hard disk replacement.

I tried also to uninstall codesys totally, by edeleting all files after, and also to remove some 3S registry keys (related to licensing manager)

I don't need hardware key, because the wago installation don't require special licensing.

The problem is that codesys try to open licensing manager, and it don't run cause the wrong LMAPI

Consequently, codesys haven't informations about licensing, and is impossible to compile importing some free wago libraries

Research on the security of technologies used by automation system developers that can potentially be applied at industrial facilities across the globe is a high-priority area of work for the Kaspersky Industrial Systems Emergency Response Team (Kaspersky ICS CERT).

This article continues the discussion of research on popular OEM technologies that are implemented in the products of a large number of vendors. Vulnerabilities in such technologies are highly likely to affect the security of many, if not all, products that use them. In some cases, this means hundreds of products that are used in industrial environments and in critical infrastructure facilities. This is the case with CODESYS Runtime, a framework by CODESYS designed for developing and executing industrial control system software.

The situation with the CODESYS framework is different: vendors of CODESYS-based PLCs adapt the framework for their hardware and, if necessary, develop additional modules using services provided by CODESYS. PLC end-users (i.e., engineers) use the CODESYS development environment to develop the code of industrial process automation programs. And the execution flow of the additional modules developed and the industrial process automation program is controlled on PLCs by the versions of CODESYS Runtime adapted for those PLCs.

This paper is devoted to research on the security of CODESYS Runtime. In it, we address the first two of the above questions: what happens inside the framework and how it works. We also demonstrate a technique for identifying vulnerabilities without being able to analyze the source code.

The two products work together. The CODESYS Development System is an IDE used to develop software for controlling devices on which CODESYS Runtime runs. The development environment includes numerous tools designed to simplify the development and testing process.

In the context of our research, it is important that the CODESYS Development System is a customizable development environment. Solutions based on it include IDE SoMachine by Schneider Electric, TwinCAT by Beckhoff Automation, IdraWorks by Bosch, Wagilo Pro by WAGO, IDEs under the name of CODESYS Development System by Owen, STW Technic, and prolog-plc, as well as other IDEs.

To program a controller using the CODESYS Development System IDE, CODESYS Runtime should be running on the controller. For CODESYS Runtime to run correctly on a specific device, it has to be adapted to the operating system and hardware selected. According to information on the CODESYS official website, CODESYS developers themselves have only adapted CODESYS Runtime for 15 devices. However, distributors have adapted CODESYS Runtime for over 350 devices.

3a8082e126