TYX
Home

Company Profile

Products

Support

News

Partners

PUG

Guestbook

Release Notes

Application Notes

Papers and Info

Problem Report

Y2K

FAQ


Release Notes

TYX TRD
Version 2.0.1
8 November 2002

1. Overview

This is the first full release of the redesigned TRD product.

2. Detailed Description

2.1. Critical items

2.1.1. Interaction with anti-virus software

Some anti-virus programs automatically scan downloaded HTML pages, blocking the executions of scripts that are considered potentially dangerous. Because the TRD Editor is an HTML application and some of its pages interact with files in the local file system, these anti-virus programs may block the execution of scripts, thus compromising the operation of the TRD Editor. To avoid this behavior, you should configure your anti-virus software, disabling script blocking.

In Norton SystemWorks the above configuration may be performed as follows:

  • open Norton SystemWorks
  • go to Options | Norton AntiVirus
  • select "Script blocking" in the tree area and uncheck "Enable Script Blocking" (see screen capture below)

Note: In some cases Norton AntiVirus keeps interfering with the TRD Editor, even if "Script blocking" was disabled. It appears that a configuration or a LiveUpdate operation re-enables the "Script blocking" option. If during the operation of the TRD Editor you receive a warning regarding a script, select the option "allow this activity once". Afterwards, check the "Script blocking" option, as indicated before.

2.1.2. Operating system compatibility

The product works properly with Windows NT 4.0 SP 6, Windows 2000 SP 2 and Windows XP.

2.1.3. Internet Explorer compatibility

The product works properly with Microsoft Internet Explorer 5.5 and 6.0. It does not work with Internet Explorer 5.0.

2.1.4. Microsoft Office compatibility

The generation of Word documents and the display of Excel reports works properly with Microsoft Office 2000 Service Release 1 and Microsoft Office XP.

2.1.5. Microsoft Visio compatibility

The generation of flowcharts works properly with Microsoft Visio 2000. The current version of the product is not compatible with Visio 2002.

2.2. Known Limitations

2.2.1. Functionality

The following categories of functionality, available in TRD 1.x versions, are not implemented in this release:

  • ATLAS-to-TRD conversion

The following categories of functionality are partially implemented in the release:

  • TRD formats
    • MIL-STD-1519 is the only format supported directly in the distribution; however, support for additional standardized or custom formats may be added by users

DiagML Import not supported in this release, due to changes in DiagML specification.

2.3 Enhancements

The enhancements indicated below were implemented since the 2.0.0 Release.

2.3.1. Multiple Connector-Pin References in DTI Sheet

Multiple Connector-Pin References in DTI Sheet are now accepted by Validation and Pin Analysis. The following separators may be used:

  • ‘;’ (semicolon)
  • ‘,’ (comma)
  • ‘ ‘ (white space)
  • <> (Carriage Return)

2.3.2. Duplicate references eliminated in Pin Analysis and Component Analysis results

If a Pin or Component is referenced more than once from a Test, it was listed multiple times in the Pin/Component vs. Test list. It is listed now only once.

2.3.3. Installation Manual

The Installation Manual describes Network Installation.

2.4 Problem Reports

2.4.1. 2018 - Design2Sheet Field Size

The fields in the Design2Sheet are too small (12 Characters). For example for the text 10 to 1000 Hz.

Field length increased to 20 characters.

2.4.2. 2020 - missing connectors

The validation is wrong because of missing connectors but these connectors are defined in interface2sheet (see attached pictures).

This behavior occurred because the connectors were defined on separate lines. This situation is now correctly handled. See Enhancement 2.3.1.

2.4.3. 2010 - validation concatenates

The validation concatenates the warnings/errors of the current validation run and the validation run before in the amount of errors/warnings line. It should be always the same amount of errors/warnings independent how often the TRD validation runs.

The number of errors and warnings were added up for subsequent Validate operations. Now they are correctly calculated.

2.4.4. 2028 - Test number references are not displayed for the STIMULI pin.

During the activation of Pin Analysis the TRD produce a excel sheet which has only the test number references of measurement pin. For the STIMULI pin the test number references are not displayed (see attached excel reflist and test with STIMULI pins).

Pin Analysis takes now into account the pins referenced in the fields CONN and RETURN of the INPUT COND section of the DTI Sheet.

2.4.5. 2029 - The ADJUST fields are too small for a complete text.

The ADJUST field in the DTI sheet is too small to insert a complete text (see attached picture of the DTI part).

Field length increased to 29 characters.

2.4.6. 2030 - Warning message during validation.

In INPUT POWER I define two power signals. In the CONN. and RETURN field I entered two pins for each power signal. The generated ATLAS file is correct but during the validation the following warning occurs:WARNING: Connector & Pin PAC1-1PDC1-1 referenced in 'DtiSheet' for Test 1000 for 'Input Power Conn.' is not defined in 'Interface2Sheet'.WARNING: Connector & Pin PAC1-2PDC1-2 referenced in 'DtiSheet' for Test 1000 for 'Input Power Return' is not defined in 'Interface2Sheet'.0 Error(s); 2 Warning(s)See attached Interface2Sheet and DTI sheet.

This behavior occurred because the connectors were defined without separators. You may use now any of the separators described in Enhancement 2.3.1.

2.4.7. 2085 - Misspelling

On General Design Data Sheet in the TRDReport.dot, the word ‘REQUIRED’ is misspelled. On the UUT General Design Data sheet the word UNIQUE is misspelled

Corrected

2.4.8. 2086 - Pin Analysis Limitation

The Pin Analysis function requires that the pins on the DTI sheet are on the first line of the Conn or Return fields of the DTI sheet. The TRD to ATLAS function requires that the pins be listed on the last line of the signal description. This makes it impossible to have a TRD that will correctly generate a pin analysis and correctly generate ATLAS code.

This behavior occurred because <Carriage Return> separators were not supported in pins lists. You may use now any of the separators described in Enhancement 2.3.1. This allows pin names to be placed on any line.

2.4.9. 2087 - Component Analysis Limitation

Component cross-reference list Test vs. Component lists multiple instances of component when same component is listed in the OUT HI/REPLACE/ and OUT LO/REPLACE fields. Further, components listed in the IN TOLERANCE/REPLACE and OTHER/REPACE fields are not shown.

Duplicates are now eliminated. See Enhancement 2.3.2.

2.4.10. 2088 - Missing Instruction in Developer's Manual

In the document TrdDevMaster1.pdf, the instructions for modifying the document template in step 4 on page 89 should also specify changing the dimensions of the array SheetMap to be increased by the number of pages added.

- Dim SheetMap(1 To 17, 1 To 2) As Variant (was originally 16, one page added)

Missing information added as Step 1.

 




| Home | Company Profile | Products | Support | News | Partners | User Groups | Guestbook |