WITETM Revision 1.4Release NotesIntroductionThis document contains the release notes for WITE revision 1.4 from Guzik Technical Enterprises. The highlights of revision 1.4 include:
All discussion of features and bugs in this document uses WITE version 1.31 as a baseline for comparison. For information about features and modifications prior to 1.31, please refer to the WITE user's manual and to the release notes for previous revisions of WITE. New Features in WITE 1.4Enhancements to the track profile test[Top of this page]Track profile test algorithm The track profile test has been enhanced to measure the write width, read width and read-to-write offset. The test also optionally measures bitshift and comparator error rate as a function of the offset from the track center. The following algorithm is used to perform width and offset calculations:
To configure the track profile test, select "Tests | Composite Tests | Track Profile" from the dashboard. You will see the following track profile test configuration dialog box:
The "Iterations" box specifies the number of iterations. TAA measurements will be performed iterations times at each offset position. The "Filter" box allows selection of the filter to read the signal through. Please note that if the overwrite option is selected, the overwrite filter specified for the current zone in "Control|Filters" will be used. The "microInch Range" frame specifies the starting and ending offset and increment between measurements in microinches. The device step shows the minimum step size of the current device in microinches. The "Write" frame controls the write operation, allowing selection of the pattern or flux to be written. The "Interpolation" frame allows enabling and disabling of slope interpolation. When interpolation is enabled, the interpolation lines will be built between upper and lower thresholds specified and the write width, read width and read-to-write offset will be measured and saved to the database. To apply the measured read-to-write offset value to subsequent tests, select the "Program WROffset" option. Note that the "Program WROffset" option can be used only when both the "Write" and "Interpolation" options are enabled. "Write width threshold" specifies the level at which the write width is to be measured. The "Attenuator control" frame allows manual adjustment of the attenuator and freezing of its automatic adjustment during the test. The "Test Selection" frame allows enabling and disabling of bitshift and comparator error rate measurements. Use of the fast offset operation for TAA measurements is also controlled within this frame. Note that the fast offset operation can not be used if the bitshift or comparator error rate tests are enabled. Enabling the "Backward TAA" option will cause track profile measurements to be taken both forward and backward. The "Average forward and backward TAA" option enables reporting of the average TAA. This option is available only when "Backward TAA" is enabled. The "Table Data" frame specifies whether the track profile should be plotted and/or written to the database. Conversion program for new database format[Top of this page]To avoid frequent changes to the RWA.MDB database, the PRML read channel parameters have been separated into their own database, ERA.MDB. When WITE 1.4 is run for the first time on a product created using WITE 1.31 or earlier, this database file will be created automatically. A standalone conversion utility is provided to convert products without using WITE. This is useful, for example, for converting files stored on a central server and distributed to multiple machines where they are actually used. In normal operation, running the conversion program will be unnecessary as updates will be made transparently. This section covers how to manually convert database files. The conversion program is called ERA_TRAN.EXE. When run, the WITE directory found in WITE.INI and all products in this directory are selected by default. You can select or deselect WITE directories and products in them before starting transfer.
Support for new head amplifiers[Top of this page]The following new head amplifiers are supported:
The following new head stack is supported:
Other new features[Top of this page]The spectral SNR test has been made simpler to use. The options have been changed from "background" and "after erasing" to "without erasing" and "with erasing." It is no longer necessary to calculate the harmonic frequencies for an arbitrary selected pattern. Instead, a flux with known harmonics is always written, allowing simple entry of any desired flux rate. The Track Width parameter in the track profile test is now normalizable. The spectrum analyzer self-calibration procedure features more descriptive error messages. Support for the new TSA cartridge with on-board head amplifier was improved. It is no longer necessary to recalibrate TAA after changing the cartridge. |
Bugs Fixed in WITE 1.4[Top of this page]If an analog box equipped with an equalizer was replaced by an analog box without an equalizer, the nonexistent equalizer could still be selected, which would result in no signal passing through. In WITE 1.4, an additional diagnostic procedure was introduced to validate the hardware configuration. A "Failure to communicate with spinstand" error often occurred due to errors in module initialization. WITE 1.40 will automatically reinitialize the appropriate module(s). Previous revisions of WITE did not detect short circuits in the UP6 +5V power line. WITE 1.4 checks for shorts and presents the error message "UP power off" when one is detected. The following errors were corrected in the track profile test:
When the "Control Head Amplifier" menu was opened, the head amplifier type was always displayed in blue, implying that its value from different from the value in the database. In WITE 1.4, the color of the combo box depends on whether it has the same value as stored in database or not. For some HSAs, the chip name was not displayed under the "Configure|Preamp" menu. WITE 1.4 correctly displays the chip name. The "Save all Iterations Data" option in the Production setup did not retain its value between WITE sessions. Now this option is saved in database. A "Product not found" error message appeared after deleting any product in the product list. Now this message pops up only on deletion of the last product in the list. The Spectral SNR test changed the selected overwrite filter value in the "Control|Filter" menu to the value specified for slot 1. In version 1.4, the spectral SNR test does not alter the default zone parameters. The popcorn test crashed if write time, read time, or delay were too small. In release 1.4, additional validation procedures were added to verify user input. A "Subscript out of Range" error message appeared during the execution of production tests with partially populated head stacks. WITE 1.4 operates correctly with partially populated head stacks. The following errors were corrected in the scanning test:
Write current and read bias could not be set correctly for TLS24506 and TLS24S508 head amplifiers. WITE 1.4 allows these parameters to be set correctly. Head selection did not work correctly for MR04B0C0 head amplifier. In WITE 1.4, head selection functions correctly. Known bugs in WITE 1.4[Top of this page]Some bugs were found too late to be fixed for the 1.4 release and will be fixed in a later release. This section contains all known bugs that you are likely to encounter. A bug’s presence here means that we are aware of the problem and actively working to solve it. If you encounter a problem not on this list, please report it to Guzik customer support. The "retest with next setup" option in the "Production | Grd/Norm" menu does not register results to the database after the first setup. It should not be used. Some DOS applications interfere with communication with Guzik hardware and can result in unstable test results. Please exit all DOS applications before running WITE. WITE hangs up if a head amplifier different than the one actually present is selected in the "Control|Head Amplifier" menu. Immediately after running a production sequence which includes scanning, an attempt to delete a zone may result in an "Operation not supported in transactions" error message. Retrying the zone deletion will work correctly. A "Cannot sort zones" error message appears intermittently when zone execution order is changed in the production test. Retrying the operation will succeed. [Top of this page] |