Please check if the occurring errors have already been covered in the FAQs 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). |
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 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.
To be able to detect problems which may only be related with the used version(s), or to be able to exclude known issues,
|
We always need accurate information and data to recreate the error profile:
See also Why accurate 'steps for reproducing a problem' are important for any Technical Support |
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):
|
By any exception in the runtime, first check if it is caused by an application structure in a POU, FB or library. |
See also our OLH on how to 'Create a Core Dump', and how to 'Creating a Core Dump of the running application manually'. |
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. |
|
More detailed information can be found under debugging a Visu Exception FAQ. |
See also....