Any error reports to CODESYS should contain the following information:
- The versions used within the Project,
- a clear error description of what exactly occurs and when,
- the exact 'Steps to repeat' to reproduce the error,
- if possible, a simplified/reduced example project(as a project archive) with the necessary scope/extent to be able to reproduce the error in it.
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.
Check the FAQ's and the FORGE page before reporting bugs.
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?
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:
- send a full project archive, with with associated Callstack and a Coredump:
- When an Exception error occurs from one of the CODESYS visualization elements, please set the compiler-define VISU_NO_EXCEPTION_HANDLING and send a full project archive (with an Callstack and a Coredump):
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....
- Our Codesys Online Help (OLH) Website
- Basic information to the Codesys Development System (Codesys Homepage)
- OLH: The Online-help introduction for the Codesys Development System (IDE)
- OLH: To set or find the used ‘Compiler Version’ within a Codesys Project
- OLH: To set or find the used ‘Visualization Profile’ within a Codesys Project
- OLH: The use-case and possibilities of implicit monitoring functions - 'Implicit Checks'
- OLH: How to 'Analyzing Errors with Core Dump' and how to 'Create a Core Dump' in the first place
- OLH: Visualization: a system overview, mechanism and display variants
There is no content with the specified labels