To display the DataBlock Properties dialog, right-click on the plot area of a Signal and select DataBlock->Properties. See Manipulating DataBlocks.
The first property of a DataBlock is its name. You can use the default name or enter a new name here. The rest of the properties are categorized into four tabs. These are described below:
•Description - A field to allow you to describe the purpose of the DataBlock
•Duration - This is the time duration of the DataBlock.
Initially you provide information about how a Signal changes over time by using the mouse to represent graphically how the Signal changes over time. This information is stored in the XML TestCase file in the form of a sequence of Transitions. The data may also be imported into the TestCase. It is still stored in the TestCase file. Apart from a sequence of Transitions, there are a couple of other ways that the data may be captured in the XML file. These are:
•Signal Generator - You can use a Signal Generator to create a waveform. Currently, Sine, Random, PWM, and Sawtooth waveforms are supported. In this case, the XML TestCase file stores only the parameters needed by the Signal Generator.
•External Data Source - The XML TestCase file references an External Data File (CSV format). The CSV file stores the information about how Signals change over time. It is not imported permanently into the TestCase, but is loaded when the TestCase is loaded.
The following DataBlock properties apply only to output Signals. For more information, see Pass/Fail Judgment Overview.
To enable or disable Pass/Fail checking for multiple Signals, you must use the context menu.
Triggers are used to cause a change in the execution path of a sequence of tests, or for setting up relative time pass/fail criteria.
A DataBlock can have zero or more Triggers defined. Select the Triggers tab to define or edit Triggers. See Creating a Trigger.
•A Trigger should be named. It is useful for maintenance purposes. Optionally a description can be provided.
•Trigger Condition - This governs when a Trigger will fire. For more details, see Creating a Trigger–Trigger Condition.
oChange - A Trigger can fire on a particular transition. For example, a Trigger could fire when the second Message transition is received.
oThreshold - A Trigger can fire when a Signal Value threshold is crossed. For example, a Trigger could fire if the Temperature exceeds 30 deg.
oFailure - A Trigger can fire when a failure is detected.
•Trigger Action - This governs what action is taken when a Trigger Fires
oNone - No action is taken. This is useful however for Relative Time Pass/Fail criteria (set up in a TestCase). Measurements are made between the time of two Trigger events.
oSet TestCase Complete - This causes the TestCase to terminate immediately, but the Scenario continues. This is useful when you want to wait in a TestCase until a condition is met. You could configure a test to advance to the next TestCase once the temperature is reached, or fail if the temperature is not reached before the end of the TestCase
oSet Scenario Complete - This causes the Scenario to terminate immediately. It is usually used if some unsafe condition is encountered, for example if a current exceeds a limit.
For more information, see Creating a Trigger.
Creating a Trigger (example)