Tip | ||
---|---|---|
| ||
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: Anchor Top Top
- The versions used within the Project (IDE, PLC Runtime, Add-on Versions, SoftMotion or Visualization Profile, etc.),
- a A clear error description of what exactly occurs and when,
- the 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 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-> see also which additional data is helpful and why:
- All used version information
- How to reproduce the problem
- Additional related specifics
- Reporting a runtime exception
- Reporting an exception in the Codesys Visualization
Info |
---|
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.
Info | ||
---|---|---|
| ||
|
Tip | ||
---|---|---|
| ||
Please check if the occurring errors have already been covered in the FAQs |
Which additional data is helpful and why? Anchor 0 0
0 | |
0 |
...
Anchor 1 1
Expand | |
---|---|
|
...
| |
To be able to detect problems which may only be related with the used version(s), or to be able to exclude known issues,
|
...
...
Anchor 2 2
...
Expand | ||
---|---|---|
| ||
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 |
Anchor 3 3
Expand | |
---|---|
|
...
| |
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):
|
...
Reporting a runtime exception Anchor 4 4
4 | |
4 |
...
Warning |
---|
Info |
By any exception in the runtime, first check if it is caused by an applicative application structure in a POU, FB or library. |
...
Exception Example:
Info |
---|
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.
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):
...
Note |
---|
If you need technical support, please purchase a a Support Ticket in in the CODESYS Store. Note that certain products in the CODESYS Store already include a Support Ticket. To report report software bugs or 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: Anchor 5 5
5 | |
5 |
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
More detailed information can be found under debugging a Visu Exception FAQ. |
...
See also....
- Our Codesys CODESYS Online Help (OLH) WebsiteBasic information to the Codesys Development System (Codesys Homepage)
- OLH: The Online-help introduction for the Codesys Development System (IDE)OLH: To To set or find the used ‘Compiler Version’ within a Codesys Project
- OLH: To 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 to 'Analyzing Errors with Core Dump' and and how to to 'Create a Core Dump' in in the first place
- Working with an Incomplete CoreDump (core file incomplete)
- 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
...