Starting with Guru Browser v59, a STDF Assembler is included via the Export > Export STDF File menu. STDF files are stored in Guru (ri.sys.ObjClass=RiDataLog) as multiple pieces that need to be assembled (header + detail + .... + summary) to create a valid STDF file. Typically, this is performed with a Guru Agent (see also STDF Reconstruct Agent). Normally, the "STDF Copy Agent" waits for an "STDF Summary" record to appear before collecting and assembling the pieces into a single STDF file. The assembled pieces comprise the STDF header, detail, and summary. The header is generated when the lot starts, detail entries will consist of 100 part sequences (or less), and the summary is created when the user presses STOP on the Test Exec. However, it is possible for testing to be interrupted in such a way that the STDF Summary file is not created. In this case, running an STDF Reconstruct Agent will cause the unprocessed STDF file to be assembled and copied.

Allow Missing Entries checkbox. Enable this entry to allow STDF files to be assembled from partial data. If a "detail" RiDataLog object is not successfully saved to disk due to data corruption when being written, it is identified as corrupt when it is read again to be backed up to the Guru Server that prevents corrupted objects from transferring. The Agent will then fail to construct the STDF file and log the error or may be configured to alert an administrator.

To Export a STDF File from RiDatalog Objects:

1. Choose Export > Export STDF File from Guru Browser (v59+) to open the STDF Assembler window.
2. Select a row that contains the data based on the Title matching the desired lot.
3. Modify the Rename Template to match the desired file name of the resulting .stdf file. (See Using Rename Template below)

Figure 1: Export STDF File



From the STDF Assembler window, select the data set that you want to export, look at the Title and Part Of column and modify the Rename Template to match your needs, then click on the Assemble/Emit Selected button.

Figure 2: STDF Assembler window



Using Rename Template

The Rename Template is used to automatically create a file name from guru keys by using the attributes of the selected datalog to construct a file name.
Any text entered into the rename Rename Template becomes a part of the file name. For example, entering "My Special Filename.abc" will cause all files copied by the agent to be called "My Special Filename.abc". Resulting in only one file, the last file copied, since they all came over with the same name. The naming of the file should be 'enhanced' by including Guru attributes in the Rename Template.

By enclosing Guru keys in angle brackets, any Guru keys can be specified in the file naming.

The following characters which were previously disallowed: + = ; , @
In addition, these characters are now disallowed: % & { }
The complete list of characters that are switched to dashes (-) is: | : { } < > / \ * ? # % & ` " \
Spaces still convert to underscore (_).

For example, a Rename Template entry of:

some-text<ri.dlog.Device>-more-text-<ri.dlog.Lot>-<ri.dlog.Sublot>.stdf

Would result in a filename of: some-text-DEVICE_NAME-more-text-LOT-SUBLOT.stdf

Here is a list of some useful Guru attributes.

ri.dlog.Device
ri.dlog.Lot
ri.dlog.SubLot
ri.dlog.EndTime
ri.dlog.OperatorName
ri.dlog.SetupId
ri.dlog.StartTime
ri.dlog.Tester
ri.dlog.TestExec
ri.dlog.Wafer
ri.hw.Esn
ri.hw.FixtureNumber
ri.hw.systemSn
ri.sys.Cid
ri.sys.CreationDate
ri.sys.ExpireOn
ri.sys.ObjFormat
ri.sys.Owner
ri.sys.Title
ri.sys.Name
ri.sys.User
ri.test.Device
ri.test.DeviceId
ri.test.Dib
ri.test.ExecBarcode
ri.test.Family
ri.test.Fixture
ri.test.FixtureClass
ri.test.Site
ri.test.Testplan

In addition, there are formatting options, specified by the hash '#'. For example:

#Date<ri.sys.CreationDate>: Formatted date: when the data file was created

#Time<ri.sys.CreationDate>: Formatted time: when the data file was created

#DateNow<>: Formatted DateTime: when the copy operation happened.

#IndexVal: Sequential index value. This can be used to ensure unique file names.

#Ditto: Holds the last file name used. This can be useful in conjunction with multiple destinations for the same file, when the same name is desired for each. Especially useful with #DateNow or #IndexVal to preclude the file having a different name at each target location.

Note that the Rename Template User Entry Dialoghas special keys for auto-inserting these values.