|
Next revision
|
Previous revision
|
configuring_traces_trids [2023/03/10 12:02]
wikiadmin created |
configuring_traces_trids [2023/03/10 12:08] (current)
wikiadmin |
| ====== Trace Data Collection ====== | ====== 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 [[https://www.youtube.com/watch?v=SlWOgyQv4kM|this video]]. | Collecting trace data involves setting up periodic updates from the tool, which can be easily configured in TransSECS. The data can then be stored in a database using the method outlined in [[https://www.youtube.com/watch?v=SlWOgyQv4kM|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. | Usually, trace data should only be collected 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 collect it at any time, it's usually just not worthwhile when the tool is idle. |
| |
| 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. | 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. |
| 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. | 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. | 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. If the start and end events are the same, trace data collection will be continuous with the collection automatically restarting whenever the event is received. |
| | |
| | From the multi-select list, choose any variable you wish to monitor. |
| | |
| | When you next build/deploy the project the trace data collection will occur on the events provided. |
| |
| |