Any error reports to CODESYS should contain the following information: 

Besides the above information, the principle of "more is better" applies here.
In order to be able to answer inquiries efficiently, it is useful to provide all relevant data

-> see also which additional data is helpful and why:

- The more detailed information the support team receives, the faster the problem can be isolated, and a resolution provided.

  • The errors must be reproducible under the Codesys IDE and with a CODESYS SL PLC.
    - For errors that occur only under other IDEs, which were modified via brand labelling, the corresponding manufacturer must be contacted.
    - For errors that occur only with a device manufacturer's PLC, the device manufacturer should be contacted to pursue a resolution for the problem.

    - This is due to the fact that other IDE manufacturers use Codesys as a platform, but can build their own restrictions or extensions that deviate
       from the default interaction, behavior and standards of the Codesys IDE, and therefore can not be pursued by us. 

  • Errors that occur with a library, not developed by CODESYS GmbH
    - For errors that occur with a library which was written by a 'third party', this 'third party' should be contacted for support.

Please check if the occurring errors have already been covered in the FAQs
or if they have already been recorded and answered under our Forge community.


Which additional data is helpful and why? 

1. All used version information 

To be able to detect problems which may only be related with the used version(s), or to be able to exclude known issues,
the following version information should be provided:

2. How to reproduce the problem

We always need accurate information and data to recreate the error profile:

3. Additional related specifics

Depending on the existing problem, different additions to be reported are necessary (or at least helpful in order to correctly understand and comprehend error profiles):


For reporting a runtime exception 

By any exception in the runtime, first check if it is caused by an applicative structure in a POU, FB or library.
To do this, use the Implicit Checks available in the Codesys IDE.  

For any exception in the runtime, we need basic a complete repository/project archive and a Coredump,
in which these exceptions have been marked with to be able to debug the problem:

If you need technical support, please purchase a Support Ticket in the CODESYS Store.
Note that certain products in the CODESYS Store already include a Support Ticket.

To report 
software bugs or if you have a question concerning the products in the CODESYS Store,
click on the "
My Question" button next to the shopping cart in the CODESYS Store.

See also....