Hi Maria,
The Signal Specification and routing subsystems (Input and Output Conversion subsystems) ensure that signals passed into the Component Under Test (CUT) comply with the main model. These subsystems enforce the compiled attributes of the CUT inputs and outputs.
Changes to sources and sinks are retained, but other parts adapt to match the main model during synchronization. This ensures compatibility between the harness and the main model.
Note that some source blocks, like Signal Builder, may require additional blocks (e.g., Rate Transition) for proper functionality. These subsystems also help complete Data Store and From-Goto hierarchies and handle virtual bus signals by expanding and merging them as needed.
If you need to define your own rules for input specification, you can create a harness without compiling the model by selecting "Create without compiling the model" under Advanced Properties during harness creation. This makes the Signal Specification and routing subsystems pass-through, but may require additional adjustments to ensure the harness compiles.
For more details, please refer to the documentation:
