Connector Transforms are different from Signal Processing (SP) Transforms. They are ticked periodically based on the Tick Period property of each Transform. (The MxVMC is a special case.)
Connector Transforms are dealt with as a group. They establish the connection to the System Under Test (SUT) and impose restrictions on how the Harness is Ticked. In a harness with Connector Transforms, the tick order is as follows:
1.SP Transforms upstream of the Connector Transforms are all ticked.
2.The Connector Transforms are ticked once. During this tick the Connector Transforms update their outputs to the SUT.
3.The Connector Transforms are ticked a second time. During this tick the Connector Transforms read their inputs from the SUT.
4.Finally all the SP Transforms downstream of the Connector Transforms are ticked.
•If the IsConnector, IsSUT, or Treat as SUT property of a Transform is set to True then the Transform is a Connector Transform.
•The SUT may be represented in a Harness by one of more Connector Transforms.
•Some Transforms cannot be classified as Connector Transforms, such as the OR Transform.
•Some Transforms are always Connector Transforms, such as the RS-232 Com Port Transform.
•Some Transforms are configurable. For example, the properties of the SIL-Easy Transform can be set either way. This is because the SIL-Easy Transform allows you to define the function of the Transform in C or C++. Other configurable Transforms are the MxVMC, Simulink, and DaVinci.
•If a Connector Transform uses a signal from another Connector Transform there must be a delay between them.
•Most Custom Transforms can be configured as Connector Transforms.
•In MxTransIt, Connector Transforms are orange:
The MxSuite provides the following Connector Transforms:
In this Section:
➢RS-232 COM Port
➢Monkeyrunner (ADB Connector)