Release Notes
WITE32TM
Version 2.30
7/14/99
Introduction
The 2.30 release introduces a new feature and fixes
bugs found in the WITE32 2.25 release. (This document
uses the WITE32 2.25 revision as a base line for comparison.)
New Features
- New type of disk (1 inch disk) is implemented in Product Parameters menu inside the Spinstand Alignment program. To get there, press Configure | Device, then press the "Run Alignment Program" button, and then press the "Set Product Parameters" button.
- A new feature, "Operation" tests, is added into production test. These
tests are simple operations and can be inserted into a production test
sequence as if they were normal tests. The differences are:
- They can be inserted many times into multiple points in a test
sequence.
- They do not generate any test result.
- The configurations are zone-independent and setup-independent (vs.
the dependence of zone/setup of the normal tests configurations). However,
one can recycle the same configuration using the identifier "Confn".
When a user clicks the Insert button in production configure
menu, the available test list is shown underneath the insertion point.
Now, the tests in the list are grouped into three categories:
- [Clb] - calibration tests.
- [Opr] - operation tests.
- [Tst] - normal tests.
- A new Dashboard menu Info is added to the main menu. Currently
only one menu item under Info is implemented—Hardware features...
It shows whether WITE32 has detected any of the five hardware components
after initialization. When the checkbox of the hardware component is
checked, the component is detected.
Fixed Bugs
The following bugs have been fixed:
- In Production Test normalization, when all the parameters in a zone are not normalizable and therefore no coefficients are generated, WITE32 still complains with the following confusing message,
Missing coefficient for all results
NOW: This unnecessary error message has been removed.
- If no external module is selected in a product, starting WITE32 gives the following confusing error message,
No current record
NOW: This unnecessary error message has been removed.
- Any spinstand error message causes GPF (General Protection Fault) and WITE32 crashes (found in 2.25).
NOW: WITE32 does not crash in the case that spinstand error occurs.
- A product created by versions before 2.20 of WITE32 may result in the following error message when initialized (found in 2.25),
WITE Normalization System: Failed to add a new record in StdResult table
NOW: This unnecessary error message has been removed when updating older WITE32 products.
- When more than 10 curves are plotted in the 747’s Comparator Error Test and Error Rate Test, this error message pops up (found in 2.25),
W747>Error:Subscript out of range
NOW: No more error message regardless of the number of curves being plotted.
- Monitor Production does not use the path and file name specified by users (found in 2.25).
NOW: The path and file name are applied properly.
- Unable to generate normalization coefficients when one of the zones contains only non-normalizable parameters.
NOW: Non-normalizable parameters only in a zone are allowed to generate normalization coefficients.
- The Production scanning causes an error message,
WResult >Automation error
NOW: No more Automation error running Production Scanning test.
Known Bugs
Guzik Technical Enterprises is actively working to solve 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 ‘admin’ 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 around 15 seconds between two WITE32 sessions.
|
