| Related Links |
 |
|
|
WITE32™
Version 2.31
8/2/99
Introduction
The 2.31 release introduces new features,
and fixes bugs found, in the WITE32
2.30 release. (This document uses the WITE32 2.30 release notes
as a base line for comparison.)
New Features
- For RWA-16xx systems only:
The WEEPROM Viewer can now display the system capabilities
of RWA-16xx machines. These options are:
- Dual PG
- 360 MFL
- RWA Fast Optimization
- AB Fast Optimization
- The Sector Amplitude Stability Test has been modified in the following manner:
- You are provided with a new combo box titled Excitations in the Sector Amplitude Stability configuration window. In previous versions of WITE32, the same pattern is used in both initial writing and the Write Excitations. With this new combo box, you can select a pattern for the initial writing in the Pattern combo box, and a second pattern for the subsequent Write Excitations in the Excitations combo box.
- The Amplitude Asymmetry parameter value can now be negative – absolute value is no longer applied to the result of the subtraction of SAA (negative) from SAA (positive). Previous versions of WITE32 apply absolute value to the subtraction.
- The definition of the Amplitude Asymmetry Range parameter has been changed from 1 – (Minimum Asymmetry/Average Asymmetry) to Maximum Asymmetry – Minimum Asymmetry to improve the accuracy of the calculation.
- The Amplitude Asymmetry Average is provided as a new result item in the Results Processor window, providing you with this additional information in the results.
- Two grading options are added into the Grading System – Grades dialogue box:
1. Always Do Final Grading
2. Context Grading
- Always Do Final Grading Option
The Always Do Final Grading checkbox, if enabled, always performs the final grading, regardless of whether the runtime grade has succeeded or failed.
- Context Grading Option
Two conditions are needed to enable the Context Grading option:
1. In the Configure | Test Options window, the Enabled checkbox in the Test Context frame is checked
2. In the Grading System - Grades window, a grade, regardless of whether it is enabled or not, is selected from the combo box Context.
Please note that the Context Grading is independent of all other grading options. For example, as long as the Context Grading is enabled, failing the runtime grade, or disabling the Always Do Final Grading option, or disabling the grade, will not prevent WITE32 from performing the Context Grading.
The purpose of adding the new feature of Context Grading is to solve the following problem:
When the very first production test is performed using a bad head, and when the Test Context is enabled as a test option, then all subsequent production tests are performed based on the wrong test context.
(The test context is a collection of "essential" parameters that remain the same from run to run. For example, the hardware gain is a typical example of context parameters. By enabling the test context, these essential parameters are measured once, then saved to the memory, and applied to all subsequent tests without measuring again.)
In previous versions of WITE32, the only way to avoid the wrong test context is to press the Clear button, which is next to the Enabled checkbox in the Test Context frame under Configure | Test Options. This clears the bad context from the memory, after the first production test has failed. However, the operator of a Production Test cannot perform this workaround because the operator has no accessibility to this Clear button through the Operator Panel.
By enabling this Context Grading feature, WITE32 uses the selected grade to decide whether to keep the test context, as a result of passing the grade, or to clear the test context, as a result of failing the grade.
Once the Production Test has passed the selected context grade, WITE32 uses the same test context for all subsequent Production Test runs, and disables the context grading internally from that time onwards. The initial test context is used until WITE32 is shut down and re-started. If the context grading is enabled, and has passed the grading once, changing the context grading selection does not cause WITE32 to perform the new test context measurement--shut down and re-start WITE32 again to change the context grading selection.
You access the Grading System - Grades dialogue box by pressing the Config button in the Grading/Normalization tab inside the Production Test configuration window.
To disable Context Grading option, select "(none)" from the combo box.
Fixed Bugs
The following bugs have been fixed:
- The Normalization options of "Standards run Warnings" and "Runs limit to Warn" do not work during production test runs.
NOW: The options of "Standards run Warnings" and "Runs limit to Warn" work properly. If "Standards run Warnings" is enabled, WITE32 issues warning after running the production test n times without running a new standard test, where n is specified in "Runs limit to Warn".
- Wrong results are reported in the WGMA's Envelope Analysis Test. The data points rather than the sector numbers are reported under the "Sector Number" column.
NOW: The "Sector Number" column is reporting the correct data.
- Mulitple Monitor Production menu items are created when multiple Production tests are created.
NOW: Only one Monitor Production menu item is on the menu to monitor the default Production test.
- Starting from an empty grading definition, if user defines a grade and runs production test with a blank in the "Runtime Grade" comboboxes, grading always passes no matter what the test results are.
NOW: Final grade is performed properly although blanks are put into the "Runtime Grade" comboboxes.
- If the "Auto Show Failure" option is enabled, and if there are failed results in the last test of a production sequence, then the failed results are not shown automatically on the "List of Failures" window.
NOW: All failed results are shown properly on the "List of Failures" window whether "Auto Show Failure" option is enabled or not.
Known Bugs
If you encounter a problem that is not on this list, please report it to Guzik customer support at Support@Guzik.com.
- Importing a product to replace a "Protected reference" product will cause this (originally protected) product to be unprotected.
The workaround is to check the "Protected Reference" checkbox again. (found in 2.21)
- Installing a module twice will disconnect the module completely (found in 2.22).
The workaround is to shutdown and restart WITE32. If it is possible, never install a module twice. In particular, never install WNorm.exe, WGrade.exe, WResult.exe, and WControl.exe—these modules are installed automatically by WITE32.
- When user specifies an output file name with a different extension other than WEX, the common dialog box will append WEX as the file extension to it.
The workaround is to choose "All (*.*)" to be the filter ("Save as type").
- Creating a product using multiple words for product directory name, e.g. "C:\WITE32\Product One", causes the following error when running "Run Alignment Program" under "Configure | Device" (found in 2.25),
WDCP: Path not found
Workaround: Use underscore "_" to replace any blanks between words, e.g. "C:\WITE32\Product_One".
- Intermittent problem arises when creating new zone. The following error message may pop up (found in 2.25),
WITE: Couldn’t save; currently locked by user ‘username’ on machine ‘machine name’. Abort/Retry/Ignore.
Workaround: Press Ignore, exit WITE32, and try again.
- If a second WITE32 is started shortly after the first WITE32 is completely closed, the following error message may pop up (found in 2.25),
…duplicate instance: Invalid procedure call or argument. Abort/Retry/Ignore.
Workaround: Press Abort. Wait approximately 15 seconds between two WITE32 sessions.
|
|
|
