Trace Data Collection

Trace data collection allows the host to configure periodic updates from the tool. Trace data collection can be set up quite easily in TransSECS and the data can be stored to a database using technique described in this video.

Usually, trace data should only be connected when something “interesting” is happening at the tool, for example when the tool is actually process, a recipe step or recipe has is running. In SECS/GEM terms this means between two events, for example the process start and process end events.

You can also set the frequency of data collection, the shortest interval supported by the SECS/GEM standard is a centi-second (0.01 seconds). There's an option to set the number of samples to be collected and TransSECS supports this, but, generally, the data collection will end when the “End Event” is seen.

Configuration is quite simple. Right-click the root node to add the TRID node and then right-click that node to add a Trace.

The TRID must be greater than zero and unique amongst your traces. The name just provides a human-readable tag.

Ensure that the “Max Samples” is larger than the number you expect to collect - the trace data collection will end when the “End Event” is received even if this number of samples have not been collected.

Set the time interval. This is seconds and decimal seconds. The minimum, per the standard, is 0.01 seconds, but any particular tool must document the smallest interval supported which may be greater than 0.01 seconds. A maximum rate of once per second (1.0 seconds) is not unknown.

Choose the “Start” and “End” events. Data collection will start when the “Start” event is received and stop when the “End” event is received (or when the maximum number of samples have been collected - whichever comes first). Typically the start and end event should be the start of processing, or the start of a recipe step or similar.

Trace data can be saved in TransSECS in a similar manner to report data as described in this video.

Simply add an an Historical server as described in the video (a different server from the one used for reports) and connect it to the Device/Tagname

As each trace is received it will be stored to the table.