Search tips for the COPA-DATA FAQ / Knowledge Base
The COPA-DATA FAQ / Knowledge Base contains frequently asked questions and known issues.
Currently only issues that have been addressed and tested, and which are available through an official build, can be found. Issues that have been addressed in an official release (full version) currently cannot be found. Issues addressed in builds for 6.22 SP1 and lower can also not be found.
What to search for
Make use of the result set filtering
How to interpret the versions in the search results
Version independent changes
Search by Article ID or issue number
How to communicate or forward a specific FAQ or KB entry
Use of acronyms / abbreviations
Tips on wording
Use of wildcards
Multiple words / Boolean operators
What is not in the Knowledge Base
What if you don’t find what you are looking for?
All entries are only available in English.
Keep your search term short and to the point. Instead of phrase “click project tree fonts list” search only for “fonts “, to maximize the results. Then filter the search results, or search within the search results, to narrow down further.
The table with the result set allows sorting via the column headers on any column.
Filtering for e.g. a specific module is possible through the combo boxes at the bottom of each column.
Also you can search all columns in the result set by typing a text in the search field of the result set. The search result is updated while you type the text. This search also includes entries that are not displayed on the current page of the result set.
In the details for KB entries there may be one or two versions listed. The versions listed here are the initial version and build in which the issue is resolved. Installing the build listed should resolve the issue.
There are a few important things to consider here.
An issue that is resolved in e.g. 6.51 SP0 build 6, will in most cases also be resolved in 6.51 SP0 build 7 and later builds for 6.51 SP0.
An issue that is only resolved in e.g. 7.10 build 6571 will normally not be resolved in versions 7.00 or lower. An issue that is resolved in e.g. 7.00 SP0 build 1 will normally not be resolved in versions 6.51 or lower. There is an exception to this rule, see the section “version independent changes”.
An issue that is resolved in e.g. 6.51 SP0 build 6 will in most cases also be resolved in the next major releases, e.g. 7.00 and 7.10. This does depend on the build date for the release of the next major release. An issue that is resolved in e.g. 6.51 SP0 build 21, which was released after the release of version 7.00 SP0 build 1, will only be resolved with a build for version 7.00 SP0 that was created after the fixed date / publish date.
An issue that is resolved in e.g. 6.51 SP0 build 20, does not necessarily need to occur in later releases. It is possible that an issue was first resolved in the beta of 7.00 SP0 and later resolved in 6.51 SP0 build 20.
An issue that is resolved in e.g. 6.51 SP0 build 6, does not necessarily need to occur in 6.51 SP0 build 0. It may be that this issue was introduced with 6.51 SP0 build 5, and is resolved again in 6.51 SP0 build 6.
If you don’t see a second version, it does necessarily not mean that the issue was not addressed in other versions. It only means that at the time the KB entry was created only a build for the version mentioned was available.
Some changes in a newer version are automatically available in the next released build for an older version. Such changes include most changes that are made to PLC drivers or drivers for the process gateway.
The following applies:
Issues addressed in drivers for version 7.00 are normally also resolved in the next released build after this issue was addressed for versions 6.51 and 6.22.
Issues addressed in drivers for version 7.10 are not automatically available in the next released build for versions 7.00, 6.51 or 6.22.
When you have been given the Article ID for an FAQ entry or Knowledge Base entry, simply enter the ID in the search field. It is also possible to search for the “issue number” or “defect ID” that is used internally at COPA-DATA.
When you want to forward a specific entry to someone else or you would like to receive more information regarding a specific entry from your local support, you can reference to a specific entry.
Please locate the Article ID for the entry in the details or the preview, and use the Article ID in your communication. A unique Article ID is automatically generated for each entry, and using the search, the Article ID can be very easily retrieved.
Try and use acronyms when you don’t find what you are looking for. E.g. instead of “alarm”, try “alarming” or “AML” for Alarm Message List
Try searching with words that describe the issue you can observe. Searching for “crash” may not yield many results. Yet searching for “responding”, “close*”, “error” or “exception” will provide more results. When you receive an error message, try searching for the error text.
It is possible to use wildcards in searches. Wildcards cannot be used at the beginning of a word.
The wildcard “?” replaces one character. E.g. “program?ing” will return results for “programming”
The wildcard “*” replaces multiple characters. E.g. program*”
Search only for single keyword, then search in results. The use of Boolean operators or regular expressions is not possible.
The extended search can be used to apply a pre-filter for the search. Users that are associated with a certain partner level can utilize the full extent of the extended search, including differential search and listing all known issues for a specific module.
Please contact your local COPA-DATA sales representative for further information on how to become a partner and what other benefits the different partner levels have to offer.
Some issues that you may encounter cannot be found in the Knowledge Base. In general only those issues that are resolved by installing a build can be found. An issue that is addressed e.g. in the documentation, cannot be found in the Knowledge Base. Also issues that are addressed in the setup cannot be found. Issues that occur only in an OEM version of the COPA-DATA products cannot be found in the Knowledge Base.
In some cases an issue that is addressed and available in a build may not yet be found in the Knowledge Base. This can happen e.g. if an entry takes a shortcut to the documentation department after it has been successfully tested.
Please feel free to contact the friendly staff at your local COPA-DATA support if you don’t find the issue that you are facing.