Files Created by Symphony

Some of these files may exist in any directory, while others are required to be in the Symphony folder as indicated. It is up to you to remember where you have saved files you create using the software.  Devise a meaningful directory structure for your work; each user could have his/her own directory, or you may wish to create a new subdirectory for each new device or test program you begin development.

CAL8.DAT Calibration file created when Symphony calibration is complete, and is the calibration file only for ETS800 series systems. Contains all of the constants and values meticulously measured during the automatic calibration process from the "Calibrate" window. These constants are restored each time you Initialize the software, insuring conformance to specs. This file must reside in the "C:\Symphony" folder.

CAL.LOG Calibration log file that contains information about the last calibration. Used only for reference by HiLevel service personnel when trying to evaluate problems.

filename.LOG Some Symphony functions produce a LOG file containing results or other information. The files have a descriptive filename; for example, ACPMU.LOG will contain the results of ACPMU timing tests.  AutoTest.LOG will contain results from an AutoTest run and will appear in the local folder of the ATX file.  Diag.LOG will contain the results of the most recent Diagnostics tests and will appear in "C:\Symphony".

Filename.PLS An ASCII PinList file for your device.

filename.ATX Test Suite information used by the AutoTest windows. You create this file with a "Save Suite" in Build ATX from AutoTest.

filename.VEC This extension is typically used to denote an ASCII input file for the CaeLink translator. Requires that you enter the proper header at the top of the file prior to translation.

filename.PRG The pattern generator program file. This ASCII file contains the loops and jumps that you define in the Vectors window. It may also be generated using the $L command in CaeLink.

filename.SET SET files contain virtually everything you define in the Symphony software to define the setup for a specific device (except vectors and pattern generator programs).  Includes the following parameters:

· Pin names, numbers and tester channels
· Group names and definitions
· Timing and Logic Levels
· Programmable load settings
· AC and DC PMU definitions
· One Shmoo Plot setup
· DUT power settings
· Run Setup info (like test rate)
· Timing-On-the-Fly assignments

filename.TRN Test vectors. The extension TRN traditionally means "translated vectors" but the same extension is used even if you created your vectors by hand. You can quickly download TRN files into vector memory or upload (save) them to disk using the tool buttons:

filename.CMT The comment file pertaining to a TRN file with the same filename. The ASCII comment file is saved/loaded automatically when you save/load the TRN vector file.

filename.OUT The output file created by SentryLink defaults to the same filename as the input file.

SpScript.TXT This file would contain any Special Scripts that you might like invoked automatically on startup.

Symphony Software Files

Most of these files must and already do reside in the folder "C:\Symphony", while some appear only on the installation disk.

Symphony.EXE This is the executable operating software, invoked when you click on the Symphony icon.

Symphony.HLP The Help file for Symphony.EXE. When you press F1 in any Symphony window, this file is referenced for the proper Help topic.

FIRMWARE.OBJ The object file for firmware upgrades that accompanies Symphony.EXE.

RELNOTES.Doc A document that contains release notes. Usually accompanies new releases of Symphony.

Symphony.GID Information file used by Symphony.EXE. Must remain in C:\Symphony.

CAELINK.EXE The translator module for the CAE-Link translator.

Also see other QnApps dealing with functions described here for further specifics about files.