CODESYS® Classic fieldbuses

Integration of classic fieldbuses in CODESYS

Even though Industrial Ethernet protocols are increasingly being used to implement machines and systems, classic fieldbus protocols are still very important for the implementation of automation tasks. CODESYS supports the most important protocols with integrated product solutions.

In addition to the general advantages of integrated communication options, the fieldbus products in CODESYS have additional application benefits:

 

Open implementation independent of controller manufacturers

Import and configure I/O modules from any manufacturer.

Standardized diagnostic interface

  • Read the diagnostics for all systems equally.
  • If required, you can also access detailed bus-specific information.

Usable library functions

  • Access acyclical and fieldbus-specific services from the PLC logic.
  • Activate and deactivate devices dynamically at runtime.

Lean solution

Achieve high performance in fieldbus communication thanks to the low overhead.

CAN

CANopen

J1939

Profibus

Modbus RTU

IO-Link

BACNET

KNX

DNP3

Reference information

CODESYS CAN

Due to its flexible application possibilities, the asynchronous, serial bus system CAN (Controller Area Network) has a high market significance. CODESYS offers sophisticated CAN support with integrated functions and products at various levels. Technical prerequisite: An implemented CAN mini driver on the target device or use of supported CAN cards/modules, such as PeakCAN®, SocketCAN, netX CAN, CANfox®, Kvaser, or EL6751 EtherCAT-to-CAN terminals. Alternatively under Linux: A driver with socket CAN. In addition to the products described below for communication with CANopen or J1939, you can also address and use CAN natively in your CODESYS application.

 

Available communication mechanisms

CANL2 interface for access to CAN chip

  • Send raw CAN messages directly from your CODESYS application or receive such messages.
  • Diagnose the CAN chip via the program code.

CAN block driver

Use CAN for communication between the CODESYS Development System and your target device.

CODESYS CANopen

Use CANopen in CODESYS in different constellations for the realization of stationary or mobile machines.

Scope of services

  • CANopen configurator fully integrated in the CODESYS Development System
    • You do not need an external tool to configure the bus system or the I/O data used.
    • Import EDS or DCF files from different manufacturers for a manufacturer-independent configuration.
    • Scan for available devices in your CANopen network and automatically add them to the configuration.
      Alternatively: Configure CANopen Manager and CANopen devices manually.
    • Validate your configuration using the online configuration mode.
  • Integrated diagnostic functions
    Find the causes of communication problems quickly and accurately.

 

  • CANopen communication stack in the form of a CODESYS library
    • Compile the stack along with your application code and load the entire code onto the controller at the same time.
    • Use the same protocol stack on different device platforms.
    • Enjoy more available device memory for other tasks whenever you are not using the CANopen stack.
    • Benefit from functional updates with new software versions.
  • Application interface for diagnostics and use of SDO
    Access SDOs from the application and use the extensive functionality without additional software.

Functional scope of the CANopen implementation

  • Error Control: Heartbeat/Node Guarding
  • Display of diagnostic data and emergency messages
  • Sync producing/consuming
  • Many supported PDO transmission types

CANopen Manager

  • Support of multiple SDO channels
  • Auto PDO mapping for modular slaves according to CiA 401 (module-dependent)
  • Configurable stack behavior
  • Insertion of optional devices and support of dynamic configurations
  • Add your own SDOs to the configuration list

CANopen Local Device

  • Static PDO mapping
  • Definition of I/O areas with automatic generation of the PDO mapping
  • Definition of SDO parameter ranges
  • API for influencing the NMT state machine
  • Generation of a CiA 306-compliant EDS file

CANopen Safety

  • Based on CODESYS CANopen Manager / Device
  • Platform-independent CANopen safety protocol libraries (Manager / Device) with integrated CANopen safety configurator
  • Extends CODESYS CANopen with safety layers
  • Certified according to EN 50325-5 for applications according to IEC 61508 SIL2 or EN/ISO 13849 up to PLd
  • Mixed CANopen / CANopen Safety operation possible in one network
  • Typical application: Mobile machines with safety control/ECU according to EN/ISO 13849 PLd, implemented with the help of CODESYS Safety SIL2

 

CODESYS J1939

Use CODESYS J1939 to implement an SAE-J1939-compatible ECU on your device.

Scope of services

CODESYS-J1939 configurator fully integrated in the programming system

  • Define the signals and parameter groups (PG) along with your control application.
  • Use them to create global variables for your project.

Import function for signal and parameter group databases (DBC/PG) including SAE signal documentation

  • Purchase an available database and install it in the configurator.
  • Create your own database and use it in CODESYS.
  • Access the documentation of the signal specifications directly.

SAE-J1939 communication stack in the form of a CODESYS library

  • Compile the stack along with your application code and load the entire code onto the controller at the same time.
  • Use the same protocol stack on different device platforms.
  • Enjoy more free device memory for other tasks whenever you are not using the J1939 stack.

 

CODESYS Profibus

Profibus is a widely used fieldbus system in automation technology. CODESYS supports Profibus DP with components that are fully integrated in the IEC 61131-3 development system CODESYS Development System.

Scope of services

  • Profibus server/client configurator, fully integrated in the CODESYS Development System on the basis of GSD files
    • Configure the bus system including integrated I/O modules without an external tool.
    • Configure Profibus DP devices in addition to the DP client.
  • Driver for fieldbus connections based on netX technology with integrated Profibus communication stack from Hilscher®
    Implement the Profibus interface flexibly on PC-based and embedded devices.
  • Driver for EtherCAT® Profibus gateway modules EL6731/EL6731-0010
    Use Profibus modules also in your EtherCAT network.
  • Diagnostic functions in the programming system and for runtime monitoring via the IEC 61131-3 application
    Diagnose occurring errors occur without additional software.

Functional scope of the Profibus implementation for master and DP devices

  • Network scan
    Automatically transfer detected DP devices to the configuration.
  • Import Profibus GSD configuration files
    Use compatible modules from a wide range of manufacturers.
  • Configuration of Profibus parameters on the I/O slaves, I/O devices and their inputs/outputs
    Set the desired parameters directly in the CODESYS Development System.
  • Convenient variable mapping
    Assign I/Os to existing variables or create I/Os directly in the configurator as new variables and divide them into bit channels.
  • Profibus master implementation supports DP V1 Class 1 Read/Write
    Exchange data acyclically with other devices and use process alarm handling.

System requirements

  • Operating systems: Microsoft Windows, Linux®, VxWorks®, embedded systems, etc.
  • Hilscher EC1 / netX-based Profibus master with integrated protocol stack, EtherCAT with gateway module EL6731/EL6731-0010

Please note: CODESYS Profibus is in the service phase and should only be used for existing projects.

 

CODESYS Modbus RTU

The serial Modbus communication protocol is based on a client/server architecture. CODESYS offers comprehensive and integrated support.

Scope of services

Generic Modbus configurator

Configure I/O channels and arrange them according to your requirements.

Protocol library for client and server application of Modbus RTU (serial communication)

  • Compile the stack along with your application code and load the entire code onto the controller at the same time.
  • Use the same protocol stack on different device platforms.
  • Enjoy more available device memory for other tasks whenever you are not using the Modbus stack.

CODESYS IO-Link

The IO-Link system enables the control and use of intelligent sensors and actuators in automation systems.

Scope of services

Integrated IO-Link configurator

Configure CODESYS-compatible controllers with IO-Link interface directly in the CODESYS Development System (e.g. Festo® mechatronic controller CECC).

Support of fieldbus gateways to IO-Link

such as Beckhoff® EtherCAT® / IO-Link terminal EL/EP6224, EP6228, ifm EtherCAT_IO-Link terminal AL1030, AL133x, AL1930, AL143x, or PROFINET IO-Link Master

You can also use IO-Link and corresponding modules in your existing network.

Network scan

Automatically transfer recognized IO-Link devices to the configuration.

Import of *IODD.xml files

Use compatible modules from different manufacturers.

Configurators for parameterizing IO-Link devices

Save device parameters in your CODESYS project.

CODESYS BACNET

BACnet is a standardized data communication protocol for Building Automation and Control NETworks.

Advantages

Use the manufacturer-independent communication protocol for Building Automation directly in CODESYS applications.

Access BACnet properties directly via the device properties.

Easily integrate BACnet devices and applications into existing networks without further implementation effort.

Scope of services

Integrated configurator

You do not need an external tool to configure the bus system or the I/O data used.

Protocol stack for Ethernet (TCP/IP), implemented as CODESYS library

  • Compile the stack along with your application code and load the entire code onto the controller at the same time.
  • Use the same protocol stack on different device platforms.
  • Enjoy more available device memory for other tasks whenever you are not using the BACnet stack.
  • Benefit from functional updates with new software versions.

Runtime system component

Integrate BACnet support into any device platform with x86/ARM CPU or Windows/Linux.

Device descriptions for BACnet servers, BACnet objects, and BACnet clients

Configure without worrying about the required description files.

Functional scope of the CODESYS-BACnet integration

  • Defined set of BACnet objects, representing physical inputs, outputs, and software objects
    Access BACnet data directly in your control application.
  • Represent the functionality of a real device.
    Combine BACnet objects in CODESYS in a BACnet server.
  • Characterization of objects through BACnet properties
    Use the available mechanisms.

 

  • Orientation of BACnet integration in CODESYS to the AMEV AS-A and AS-B standard:
    • Direct access of an IEC application to the properties of BACnet objects and the configuration parameters of a BACnet server
    • Programming of BACnet clients: Access through BACnet services to BACnet functions in the BACnet network
    • Pre-implemented applicative behavior of BACnet objects, e.g. Property-Access, Calendar-Object, Schedule-Object, Who-Has, I-Am.

Work as usual with BACnet - directly in a freely programmable interface for flexible implementation of your building application.

To view the video, cookies must be enabled in the "Advertising" section!

Further information

  • Online help with instructions for use can be found here.
  • Video series "CODESYS in Building Automation", part 3 "Important communication protocols in Building Automation" on YouTube (in German):
    Time codes for specific information on BACnet: Theory from 00:40 | Practice from 04:31

 

 

CODESYS KNX

As a field bus for building automation, KNX is the successor to the EIB, BatiBus and EHS field buses. Technically, KNX is a compatible further development of the EIB, extended by important configuration mechanisms and transmission media. CODESYS KNX enables any CODESYS-compatible device to be extended so that it functions as a KNX participant and can communicate with KNX I/Os.

Advantages

Connect a freely programmable controller / PLC to the KNX building protocol

and create a unique, flexible building automation solution.

Exchange data with the ETS5® configuration system:

CODESYS users work in CODESYS, ETS users in ETS.

Update and merge the information from CODESYS and ETS.

Engineer building applications from building input and output data

through to visualization via web browsers on tablets and smartphones.

Use CODESYS as a gateway

to exchange building data between KNX and other protocols, e.g. via BACnet®, Modbus or OPC UA.

 

Benefit from new possibilities in building automation

by connecting room and HVAC automation or for networking with SmartFactory or SmartEnergy systems.

CODESYS KNX scope of services

  • Integrated configurator for I/O channels in the CODESYS Development System
    Connect I/O channels from the KNX I/Os to the control application.
  • Integrated I/O driver
    Use common KNX datapoints as I/O channels in CODESYS.
  • KNXnet/IP protocol stack in the form of a runtime system component for CODESYS Control
    Use the KNX solution with any CODESYS-compatible systems.
  • Data exchange function with the ETS configuration system
    Save yourself manual copying from one tool to another.

To view the video, cookies must be enabled in the "Advertising" section!

Further information

  • Online help with instructions for use can be found here.
  • Video series "CODESYS in Building Automation", part 3 "Important communication protocols in Building Automation" on YouTube (in German):
    Time codes for the specific information on KNX: Theory from 13:14 | Practice from 16:12

 

CODESYS DNP3

The DNP3 (Distributed Network Protocol) communication standard is used in telecontrol technology to exchange data between control systems and remote maintenance terminals. CODESYS DNP3 enables this communication in CODESYS applications for compatible control systems with a serial or Ethernet interface.

Advantages

Configure and use a CODESYS-compatible controller as an outstation.

Use the CODESYS Development System to implement a freely programmable, flexible telecontrol solution.

Product features

  • CODESYS library with IEC 61131-3 function blocks for communication via DNP3 protocol
    • Realize control application and telecontrol access in one project and load the entire code onto the controller at the same time.
    • Use the entire application on different device platforms.
    • Enjoy more available device memory for other tasks whenever you are not using DNP3.
    • Benefit from functional updates with new software versions.
  • Example project for the rapid implementation of data transfers on CODESYS controllers
    Achieve quick wins thanks to a simple example function.
  • Configuration and communication by calling function blocks
    Use the available POUs to implement dynamic communication.

 

  • Support of numerous data types defined in the protocol (AnalogInput, AnalogInputDeadband, AnalogOutput, BinaryCounter BinaryInput BinaryOutput DoubleBitInput)
    Configure telecontrol variables specifically for the devices used.
  • Options for data exchange:
    • Reading and writing the supported data types
    • Unsolicited response with specification of the sampling rate
      Use the telecontrol protocol options.
  • Supported transmission media:
    • Serial connection
    • TCP/IP
      Use the available interfaces.
CODESYS Store How to get

How to get

  • Use CODESYS-compatible controllers from device manufacturers that have already implemented the desired communication protocol supported by CODESYS. CODESYS Inside helps you to find suitable suppliers.
    Your benefits:
    • You can immediately develop your application with CODESYS on such devices.
    • There are no additional costs because the required software licenses for CODESYS Control are already included in the device price (unless otherwise specified).
    • You have a central contact person for hardware and software support questions.
  • Alternatively: Use CODESYS-compatible controllers from device manufacturers that have implemented the CODESYS licensing mechanism, and install or license the desired communication protocol on these devices yourself.
    Your advantage:
    • Extend the functionality and benefits of your device yourself.
  • Purchase application-based licenses for all SoftPLC variants or virtual controllers via the CODESYS Store. Many of these licenses already support classic fieldbus systems. You can find an overview here.
    Alternatively: Purchase the required licenses for the desired communication protocol in the CODESYS Store. The table below provides an overview of what is available.
    In any case, the target hardware used must have a corresponding physical interface.
    Your benefits:
    • Be sure to use exactly the right industrial hardware for your control task.
    • Expand the functionality and benefit of your device yourself by using additional licenses.