CheckConditionWithTimeConstraint¶

ID: Check/CheckConditionWithTimeConstraint

Checks if the signal exceeds/undercuts a threshold in a defined time window.

Note: The signal value must exceed/undercut the threshold (defined by the conditions) for a defined time frame [minTime, maxTime] and then go back to its initial condition.

Signals¶

Signal¶

The signal to check.

• Direction: IN

• Optional: False

Parameters¶

AllowFailedInstances¶

Specifies if the timing diagram can fail. The value has to be a boolean value (True or False).None is also valid here and means False.

• Direction: IN

• Type: PYOBJECT

MaxParallelInstances¶

Maximum number of diagram instances that can be evaluated in parallel. A value <= 0 indicates no limitation.None is also valid here and means 1.

• Direction: IN

• Type: INTEGER

MinMaxSuccessfulInstances¶

Specifies how often the timing diagram must run successfully. The value can be a number or a range (two comma-separated values in parentheses). For value “None”, the appropriate boundary will not be checked.

• Direction: IN

• Type: PYOBJECT

firstCondition¶

This is the first and last condition of the signal value. For example: ‘VALUE <= 3’ (see in the help “Reference timing diagram-based trace step templates”).

• Direction: IN

• Type: STRING

maxTime¶

This is the maximum time that the second condition should be true.

• Direction: IN

• Type: FLOAT

minTime¶

This is the minimum time that the second condition should be true.

• Direction: IN

• Type: FLOAT

secondCondition¶

This is the second condition of the signal value. This must be true in the given time window between minTime and maxTime. For example: ‘VALUE > 3’ (see in the help “Reference timing diagram-based trace step templates”).

• Direction: IN

• Type: STRING