Ever wondered about connecting to a PLC and downloading an application? How does monitoring or file transfers work? Download this conceptual documentation (PDF) about the Online Manager to find answers to these and numerous other questions.

This article describes the prerequisites and limitations for compatibility handling along with the two necessary packages CODESYS Package Manager and CODESYS Compatibility Package.

For future architecture changes in the Automation Platform (AP), we have created the option of moving interfaces that have already been released to other interface components without impairing compatibility. This document explains the technical basics and the new aspects of building and deploying plug-ins and packages.

With screen resolutions increasing more and more these days, computer users need to set higher pixel densities in order to increase the size of text elements. In the past, Windows operated in 96 dpi, but now 120 dpi (or higher) is quickly taking over.

Customers who are developing their own Automation Platform plug-ins typically have the ambition to provide a seamless experience for their users. In other words, the integration into the existing CODESYS infrastructure should be as good as possible.

Starting in SDK 3.5 SP7, "Dependency Injection" (DI) reverses the direction of instance creation. While traditionally a Component Manager call would create an instance during runtime on demand, in the DI architecture a plugin declares a member variable into which an instance creation function will be injected from the framework. 

To get a better picture of the compiler frontend, we have put up this conceptual documentation for the system instance Language Model Manager.

Ever wondered about the project structure events vs. object manager events? How does copy and paste of IObjects work? Download this conceptual documentation (PDF) about the Object Manager to find answers to these and numerous other questions.

CODESYS plugins can reference both interface assemblies and GAC assemblies. During plugin installation (whether through IPM.exe, IPMCLI.exe, the PackageManager or the component manager APIs), those dependencies need to be resolved and handled appropriately.

CODESYS stores its preference settings at various places in the file system. This article gives an overview of the various files and locations.