Versions Compared

Old Version 12

changes.mady.by.user CODESYS Support

Saved on

compared with

New Version Current

changes.mady.by.user CODESYS Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Tip
titleCheck 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: 

Anchor
Top
Top

  • 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-> see also which additional data is helpful and why:

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.

...

titleWhom to contact for vendor-specific errors?

...

Tip
titleCheck 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?

Anchor
0
0

...

Anchor
1
1

Expand
title

...

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:

  • Version of the CODESYS programming environment (IDE).
  • Version of the operating system, the used runtime and processor of the target system.
  • Version of the used CODESYS Packages (like SoftMotion, Ethernet, Visualization, etc.).
  • Version of the used Visualization Profile for visualization problems within the Visualization Editor and Visu Display Variants.


Anchor
2
2

Expand
title

...

How to reproduce the problem

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

  • Exact 'Steps to repeat' to be able to reproduce the error.
    The more precisely the individual steps are described, the less need there is to ask for error reproductions and the less room there is for interpretation when retesting.
  • A full project archive (not only the CODESYS project!).
    This contains the libraries used, the application structure of used functions, etc.
  • For more complex processes, in addition to the written steps, a short screen recorded video, showing the steps and then the error that occurs, can be very useful.
  • Note that sporadic errors are very difficult to solve.
    In these cases, you should endeavor to determine the conditions under which it occurs, so that the support team has a chance to reproduce it and investigate.

See also Why accurate 'steps for reproducing a problem' are important for any Technical Support


Anchor
3
3

Expand

...

titleAdditional 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):

  • If available, controller logs, with the appropriate log filter settings, should always be given.
  • Screenshots of the error when it occurs in the Codesys IDE.
  • In case of fieldbus related errors (or incorrectly displayed values in the different editors of the fieldbus), recording of the communication via 'Wireshark',
    that ranges from the download/login/start of the controller to after the occurrence of the error behavior, are needed. 


...

Reporting a runtime exception
Anchor
4
4

...

Infowarning

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

...

Exception Example:

Image Added

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.

    Image Added
  • Send a full project archive, with the associated Callstack and a Core Dump, created at the time of the crash.

    Image Added  Image Addedsend a full project archive, with with associated Callstack and a Coredump:
    Image Removed
    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):
    Image Removed
    More detailed information can be found under Debugging a Visu Exception.

...

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

Expand
titleWhom to contact for vendor / 'third party' specific errors?


Info

For vendor (or 'third party') specific errors, it must distinguish where the error occurs:

  • 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 library manufacturer should be contacted for further support.



Expand
titleHow to proceed, when an Exception error occurs from one of the CODESYS Visualization Element?
  • Please set the compiler-define: VISU_NO_EXCEPTION_HANDLING

Image Added

More detailed information can be found under debugging a Visu Exception FAQ.


...

See also....