Limitations When Working With TargetLink Models
Working within a TargetLink subsystem is 100% supported by MoRe. When working beyond the boundaries of a TargetLink subsystem, there are some limitations that are described below:
- Remove Cross-Hierarchy Signal Forward: If a cross-hierarchy signal is removed that goes into an inport of a TargetLink simulation frame block, the removal is stopped at this inport. If a cross-hierarchy signal is removed that goes into an outport block of a TargetLink subsystem with simulation frame, the removal is stopped at this outport block.
- Remove Cross-Hierarchy Signal Backward: If a cross-hierarchy signal is removed that comes out of an outport of a TargetLink simulation frame block, the removal is stopped at this outport. If a cross-hierarchy signal is removed that comes out of an inport block of a TargetLink subsystem with simulation frame, the removal is stopped at this inport block.
- Move Blocks Up: The action is disabled if the current subsystem is a TargetLink subsystem with simulation frame.
- Move Blocks Down: TargetLink simulation frame subsystems are excluded from the list of possible target subsystems.
- Break Subsystem: The action is disabled if the selected block is a TargetLink simulation frame block.
- Split Subsystem: The action is disabled if the current subsystem is a TargetLink subsystem with simulation frame.
- Merge Subsystems: The action is disabled if one of the selected blocks is a TargetLink simulation frame block.
- Insert Subsystem Inport/Outport Above/Below: The action is disabled if the selected block is a TargetLink simulation frame block.
- Move Interface: The action is disabled if the selected block is a TargetLink simulation frame block.
- Rename Signal And Ports: The action does not rename ports of TargetLink simulation frame blocks. Additionally, port blocks are not renamed if the current subsystem is a TargetLink subsystem with simulation frame.