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.
In addition, it can be helpful to inform you about the use of function blocks, methods and add-ons (provided by Codesys) in the Codesys Online Help (OLH).
Here, the usage, configuration, description and possible applications as well as general problems, that users might expect to encounter, are described.
Any error reports to CODESYS should contain the following information:
- The versions used within the Project (IDE, PLC Runtime, Add-on Versions, SoftMotion or Visualization Profile, etc.),
- A clear error description of what exactly occurs and when,
- The exact 'Steps to repeat' (STR) to reproduce the error (see also, why accurate 'steps for reproducing a problem' are important for any Technical Support),
- If possible, a simplified/reduced example project (as a full 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:
- All used version information
- How to reproduce the problem
- Additional related specifics
- Reporting a runtime exception
- Reporting an exception in the Codesys Visualization
See also the section for 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.
Which additional data is helpful and why?
Reporting a runtime exception
By any exception in the runtime, first check if it is caused by an application structure in a POU, FB or library.
To do this, use the Implicit Checks available in the Codesys IDE.
Exception Example:
See also our OLH on how to 'Create a Core Dump', and how to 'Creating a Core Dump of the running application manually'.
Please provide:
- The Coredump, created at the time the exception occurred.
- Send a full project archive, with the associated Callstack and a Core Dump, created at the time of the crash.
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.
FAQ:
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: the PLC Log and how to Reading the PLC Log
- OLH: Visualization: a system overview, mechanism and display variants
- How to 'Debugging a Visu Exception'
- OLH: Transferring Projects