The IEC1131 TOOLSET Application Validators are a suit of four programs that enable the applications
developer to validate and verify application programs generated by the IEC1131 TOOLSET. The
Validators process various database files produced by the IEC1131 TOOLSET to identify
dependencies between programs within an application, and the differences between versions of an
application
Features
• Windows applications
• On screen and printed reports available
• Results presented in ‘easy to use’ format
Issue 7 Oct 05 PD-T8015 1
Trusted
ssue
I
Number Date Revised by Technical CheckAuthorised by Modification
1.3.1. Using Validator #3........................................................................................................................8
1.4. Validator #4 – TIC Version Checker ............................................................................................9
1.4.1. Using Validator #4........................................................................................................................9
1.5. Program Dependency Tree .......................................................................................................10
1.6. Errors and Warning....................................................................................................................11
Issue 7 Oct 05 PD-T8015 4
Trusted
TM
Application Validators T8015
Notice
The content of this document is confidential to ICS Triplex Technology Ltd. companies and their
partners. It may not be given away, lent, resold, hired out or made available to a third party for any
purpose without the written consent of ICS Triplex Technology Ltd.
his document contains proprietary information that is protected by copyright. All rights are reserved.
T
Microsoft, Windows, Windows 95, Windows NT, Windows 2000, and Windows XP are registered
trademarks of Microsoft Corporation.
The information contained in this document is subject to change without notice. The reader should, in
all cases, consult ICS Triplex Technology Ltd. to determine whether any such changes have been
made. From time to time, amendments to this document will be made as necessary and will be
distributed by ICS Triplex Technology Ltd.
Information in this documentation set may be subject to change without notice and does not represent
a commitment on the part of ICS Triplex Technology Ltd.
The contents of this document, which may also include the loan of software tools, are subject to the
confidentiality and other clause(s) within the Integrator Agreement and Software License Agreement.
No part of this documentation may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying and recording, for any purpose, without the express
written permission of ICS Triplex Technology Ltd.
Disclaimer
The illustrations, figures, charts, and layout examples in this manual are intended solely to illustrate the
text of this manual.
The user of, and those responsible for applying this equipment, must satisfy themselves as to the
acceptability of each application and use of this equipment.
This document is based on information available at the time of its publication. While efforts have been
made to be accurate, the information contained herein does not purport to cover all details or variations
in hardware or software, nor to provide for every possible contingency in connection with installation,
operation, or maintenance. Features may be described herein which are present in all hardware or
software systems. ICS Triplex Technology Ltd. assumes no obligation of notice to holders of this
document with respect to changes subsequently made.
ICS Triplex Technology Ltd. makes no representation or warranty, expressed, implied, or statutory with
respect to, and assumes no responsibility for the accuracy, completeness, sufficiency, or usefulness of
the information contained herein. No warranties of merchantability or fitness for purpose shall apply.
Issue 7 Oct 05 PD-T8015 5
Trusted
TM
Application Validators T8015
Revision and Updating Policy
All new and revised information pertinent to this document shall be issued by ICS Triplex Technology
Ltd. and shall be incorporated into this document in accordance with the enclosed instructions. The
change is to be recorded on the Amendment Record of this document.
Precautionary Information
WARNING
Warning notices call attention to the use of materials, processes, methods, procedures or limits which
must be followed precisely to avoid personal injury or death.
CAUTION
Caution notices call attention to methods and procedures which must be followed to avoid damage to
the equipment.
Notes:
Notes highlight procedures and contain information to assist the user in the understanding of the
information contained in this document
Warning
RADIO FREQUENCY INTERFERENCE
Most electronic equipment is influenced by Radio Frequency Interference (RFI). Caution should be
exercised with regard to the use of portable communications equipment around such equipment.
Signs should be posted in the vicinity of the equipment cautioning against the use of portable
communications equipment.
MAINTENANCE
Maintenance must be performed only by qualified personnel, otherwise personal injury or death, or
damage to the system may be caused.
Caution
HANDLING
Under no circumstances should the module housing be removed.
Associated Documents
Product Descriptions (PD) provide product specific information.
The Safety Manual contains the recommended safety requirements for the safety system design.
The PD8082B – Toolset Suite provides specific guidance on system configuration and application
generation.
The Operator and Maintenance Manual contains general guidelines on maintenance and diagnostic
procedures.
For technical support email: support@icstriplex.com
Issue 7 Oct 05 PD-T8015 6
Trusted
TM
Application Validators T8015
1. Description
1.1. Validator #1 – Cross Reference Checker
his Validator processes the cross reference file that is output as a result of using the IEC1131
T
TOOLSET 'Cross Reference' tool. The Validator processes this file then presents the user with a
graphical display of variable usage. This enables the user to easily identify variables that are shared
between programs within an application.
Programs that share one or more variables are dependent on each other, i.e. changes to one program
can affect the behaviour of its dependent. These dependencies must be checked during the
development of such an application if the target integrity for the application is to be SIL3 (AK6). The
cross reference checker aids this task by identifying program dependencies and thus enables the
applications developer to perform adequate re-test of affect programs.
The Validator can be run as a stand alone application, or by selecting 'Cross Ref. Validator' from the
IEC1131 TOOLSET 'Tools' menu. Before running the Validator, the cross reference file must be
generated. It is recommended that the file is given the same name as the project with an '.xrf'
extension, and is located in the application directory as the Validator looks for this file by default when it
is run from the IEC1131 TOOLSET 'Tools' menu. For example, if the project name is 'projxyz' then
enter the filename 'c:\isawin\apl\projxyz\prjxyz.xrf' when generating the cross reference file. Note that
the complete path name must be entered.
1.1.1. Using Validator #1
The Cross Reference Checker (Validator #1) can be run as a stand alone application or by selecting
'Cross Ref. Validator' from the IEC1131 TOOLSET 'Tools' menu.
1.1.2. Generating a Cross Reference File
To generate the cross reference file for an application follow these steps:
1. Start the IEC1131 TOOLSET 'Projects' manager.
2. Select and double-click on the project containing the required application.
3. Select the 'Cross References' item from the 'Tools' menu.
4. Ensure that the Object type selection is set to '(all)' then select the 'Export (text file)' option
from the 'File' menu.
This Validator performs the same task as Validator #1 to produce a graphical display of variable usage
and program dependencies that the applications developer can use to aid program verification and retest. The Validator differs from Validator #1 in that it derives the dependency information from the
downloadable TIC code and application symbols database files generated by the IEC1131 TOOLSET
hen an application is successfully compiled. By deriving the information from a different source, the
w
applications developer is able to perform an additional consistency check on the IEC1131 TOOLSET
and Validators themselves by comparing the results of each.
1.2.1. Using Validator #2
The TIC Code Cross Reference Checker (Validator #2) can be run as a stand alone application or by
selecting TIC Dependency Checker' from the IEC1131 TOOLSET 'Tools' menu.
1.3. Validator #3 – TIC Code Processor
This Validator is used to compare the compiled TIC code produced by the IEC1131 TOOLSET
compiler for two different application databases. Its intended use is to identify differences between
versions of the same application.
The output from the Validator enables the applications programmer to identify programs that have
changed as a result of amending an application, and to also identify any unexpected changes to
programs that may have been introduced by the IEC1131 TOOLSET itself.
To use this Validator it is recommended that the IEC1131 TOOLSET 'Projects' manager is used to
copy the project to be amended to a new project before any changes are applied to it. The required
changes can be then be applied to the existing project. Both the modified and copied projects can then
be compiled to produce the database files required by the Validator.
Run the validator by either selecting the 'TIC Difference Checker’ option from the IEC1131 TOOLSET
'Tools' menu, or as a stand alone application. Select the copied and modified application directories
for comparison, if all the required database files are available then programs from each application are
compared.
1.3.1. Using Validator #3
The TIC Code Processor (Validator #3) can be run as a stand alone application or by selecting 'TIC
Difference Checker’ from the IEC1131 TOOLSET 'Tools' menu.
Issue 7 Oct 05 PD-T8015 8
Trusted
TM
Application Validators T8015
1.4. Validator #4 – TIC Version Checker
This Validator is used to compare the compiled TIC code produced by the IEC1131 TOOLSET
compiler with the application loaded into the Trusted
validator is to confirm that the application being executed in a Trusted
TM
Main Processor. The intended use of this
TM
system matches the toolset
copy of the TIC code.
The output from the Validator enables the applications programmer to identify programs that have
changed either as a result of amending an application, or due to any unexpected changes to programs
that may have been introduced by the Toolset itself.
1.4.1. Using Validator #4
To use this Validator it is recommended that the IEC1131 TOOLSET, 'Projects' manager is used to
copy the project to be executed on the Trusted
subsequent amendments to the project can result in a change to the compiled TIC code.
Run the validator by either selecting the 'TIC Version Checker' option from IEC1131 TOOLSET 'Tools'
menu, or as a stand alone application. Select the application directory for comparison, interrogate the
Trusted
M
T
Main processor for the run time application and then compare the applications.
TM
Main Processor as a comparison copy. Any
Issue 7 Oct 05 PD-T8015 9
Trusted
TM
Application Validators T8015
1.5. Program Dependency Tree
The program dependency tree produced by Validators #1 and #2 shows program and variable
dependencies by displaying them in a tree hierarchy. The top level nodes in the tree give the programs
from the application. These expand to list the variables used by a program, and these in turn expand
to list the programs that use a variable. The icons are used for the tree nodes are assigned unique
colours and shapes, and have the following meanings as detailed below.
Green Round Icon
This node represents a program that has no shared variables, and expands to display only variables
that are not shared.
Red Round Icon
This node represents a program that has one or more shared variables, and expands to display both
shared and non-shared variable node types.
Green Square Icon
The node represents a variable that is not shared and expands to display only one program name.
Red Square Icon
The node represents a variable that is shared, and expands to display the names of the programs that
share it.
Issue 7 Oct 05 PD-T8015 10
Trusted
TM
Application Validators T8015
1.6. Errors and Warning
The following ‘Errors’ and ‘Warnings’ by the Application Validators as they are detected.
'Not all dependency information has been examined'
This warning is displayed if an attempt is made to exit the program, or print a dependency report,
before all the dependency information has been viewed. The dependency information is considered
viewed when all the top level program nodes in the view tree have been expanded. These can be
expanded individually, or all at once by clicking on the 'Expand All' button. Note that the dependency
information is still considered viewed if the nodes are collapsed again.
'Abort, name too long!'
This message is displayed if a variable or program name read from the application symbols file, or the
cross reference, is too long. The maximum identifier length supported by IEC1131 TOOLSET version
3.23 is 16.
'Aborted, unknown block type header'
This message is displayed by Validator #1 if it encounters an unknown header type while reading
through the cross reference file. Check that the correct file has been selected, or try re-generating it.
'Aborting, input file is not a valid cross reference file'
This message is displayed by Validator #1 if it detects a syntax or format error while reading through
the cross reference file. Check that the correct file has been selected, or try re-generating it.
'Aborting, input file is not a valid symbols file'
This message is displayed if a Validator encounters a syntax or format error while it is reading the
application symbols file. Try re-compiling the application to re-generate the symbols file.
'Applications directory : <name> does not exist'
This message is displayed when a Validator cannot locate the specified Application Directory.
'Cannot find application symbols file Appli.tst for application <name>'
This message is displayed if a Validator cannot locate the application symbols file for an application.
Check that the application has been compiled successfully.
'Cannot find TIC code file Appli.x6m for application <name>'
This message is displayed if a Validator cannot locate the download data base file for the application.
Check that the application has been compiled successfully, and that the compiler options have been
set to generate code for a Motorola target (ISA68M).
'Cannot produce report, printer fault'
This message is displayed if a printer fault occurs while a Validator is attempting to output a report to
the printer.
'Download database not in Motorola format'
The applications download database file is not in the correct format. Ensure that the compiler options
are set to generate code for a Motorola target (ISA68M) and re-compile the application.
Issue 7 Oct 05 PD-T8015 11
Trusted
'Error accessing application history file !'
This message is displayed when a file I/O error occurs when accessing the application history file.
These messages are displayed when an error occurs while reading from the download database file.
Try re-compiling the application to re-generate the database file.
'Error reading from formatted file!'
'Error accessing file <file>'
These messages are displayed when a file I/O error occurs while reading from a formatted text file, i.e.
the cross reference file, or the application symbols, files which are text.
'Program count mis-match in application directory <name> database files in-compatible'
This message is output when the download database file and application symbols file are found to
contain different numbers of programs. Try re-compiling the application.
'Project name mis-match in application directory <name> database files in-compatible'
This message is output when the download database file and application symbols file are found to be
in-compatible because they contain different project names. Try re-compiling the application.
This message is output when the download database file and application symbols file are found to be
in-compatible because the application symbols CRCs do not match. Try re-compiling the application.
'Unable to produce report file'
This message is displayed if a file I/O error occurs while a Validator is attempting to output a report to a
text file.
Issue 7 Oct 05 PD-T8015 12
Trusted
TM
Application Validators T8015
This page is intentionally blank
Issue 7 Oct 05 PD-T8015 13
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.