Engineering
All six IEC 61131-3 languages in one project tree. Library management, version comparison and online debugging run from the same interface.
ExploreEMEA Technology CODESYS
Let the control of your machine be independent of the hardware brand.
CODESYS ties machine control to the IEC 61131-3 standard, so your application code is never locked into one manufacturer’s catalogue. EMEA Technology engineers that platform across Türkiye: we design the architecture, develop the application, supply the licences and commission the machine on site.
Standard
IEC 61131-3
Programming languages
6
Motion cycle time
250 µs
Fieldbus
EtherCAT +
Engineering centre
Türkiye
CODESYS Platform
CODESYS is not one program but a system of six layers
Working out which of these layers your project actually needs is the first job. Buying a package you will not use costs money; standing still in the field because one is missing costs more.
Control Runtime
The layer that executes your application on an industrial PC, an embedded board or a third-party controller. Change the hardware and the application code stays the same.
ExploreSoftMotion, CNC & Robotics
From single-axis positioning to cam synchronisation, from G-code interpretation to delta and SCARA kinematics — motion in the same cycle as the logic task.
Explore
Fieldbus & Communication
EtherCAT, PROFINET, EtherNet/IP, CANopen and Modbus stacks are set up in the configurator, and OPC UA carries data to the layer above.
ExploreVisualization
The operator screen is designed inside the control project and published from one source to panel, browser and mobile. There is no separate tag table to maintain.
ExploreLicensing
A licence plan broken down item by item according to runtime class, motion level and client count — delivered as a dongle or a software container.
Explore
Why this approach
Hardware independence proves itself in the field, not on paper
In the classic approach the hardware and the software are bought in the same box. When supply dries up or capacity grows, it is not only the box that changes — part of the program is rewritten too. Tie the control logic to a standard and that dependency breaks.
- Supply flexibility When the controller brand changes, it is the device configuration that is rebuilt — not the application code.
- One cycle, one system Because logic, motion and visualization live in one project, the data-exchange layer between systems and the timing gap that comes with it both disappear.
- Scalable capacity When the axis count grows, raising the processor class is usually enough — you rarely need to move up a hardware model.
- Code you can hand over The library structure and the source stay with the machine owner, so maintenance never depends on a single supplier.
None of this means every machine needs PC-based control. On a line that only does logic, a leaner configuration is often the right answer. The axis list and the cycle-time target decide.
Architecture
Logic, motion and measurement on one controller
Field devices update on the same line and the same clock. The data-exchange layer between systems, and the timing gap it brings, both disappear.
Quick configuration
Which package does your machine need?
Three questions. The result is not a firm quote — it is a starting frame that shows where the conversation begins.
How we work
Four steps, driven by measurement not guesswork
Every step has a concrete deliverable. What will work, and how, is written down before anyone goes to site.
Technical discovery
We establish axis count, motion type, fieldbus and what is expected of the operator interface.
Architecture and licence plan
Runtime class, motion package and visualization licence are sized for the machine.
Application development
Control logic, motion profiles and screen flow are built on a versioned library structure.
Field commissioning
Tuning is done from trace recordings, then operator training and handover documentation are completed.
Frequently asked
What people ask before starting a project
Is CODESYS a PLC brand?
No. CODESYS is a software platform for developing control applications to the IEC 61131-3 standard. The same project can run on controllers from different manufacturers that support the runtime, so your hardware choice does not lock in your software.
Where does EMEA Technology fit in?
Across the whole chain: licence supply, architecture design, application development and field commissioning. We put down in writing what the machine has to do, build the leanest CODESYS configuration that achieves it, and hand the machine over running.
Can I migrate an existing machine to CODESYS?
The logic structure can be carried over; vendor-specific function blocks and the hardware configuration are rebuilt. We start by producing a functional analysis of the existing program, map the library equivalents and make the risks visible before any work starts.
How is the licence cost determined?
It is driven by the runtime class, the motion control level and the number of visualization clients. Send us your axis list and we will set out in writing which items you need and why — we do not propose packages you will not use.
Which controller hardware does it run on?
Industrial PCs, embedded boards and third-party controllers that support the runtime. What decides the hardware is not the brand but the processor class, real-time kernel support and the fieldbus interface. Your axis list and target cycle time drive that choice directly.
Do we keep the source code at the end of the project?
Yes. The project file, library structure and documentation are handed over to the machine owner. The point is that maintenance should not depend on a single supplier — and if your own team wants to take it forward, we run the handover training as well.
How long does commissioning take?
From a few days on a logic-heavy line to a few weeks on a multi-axis synchronised machine. What sets the duration is not the amount of code but the number of variables in the field: mechanical tolerances, drive tuning and material behaviour. That is why we work from measurements.
How are software updates applied in the field?
The application is downloaded to the runtime over the network; there is no need to open the cabinet. Versions are tagged in the library structure, so you always know which release is running on which machine and rolling back takes minutes.
Are remote access and data collection possible?
Yes. The operator screen can be opened in a browser and production data can be pushed upstream over OPC UA. Access control and network segmentation are planned at the start of the project; we do not recommend leaving the machine directly exposed to the internet.
Do you train our team?
Yes. We run a training programme covering everything from IEC 61131-3 fundamentals to motion control and visualization, either in our training room in Bursa or at your own site. See the Training Request page for details and pre-registration.