Hi Aitor,
There can be multiple reasons for such situation to arise. Following pointers can be rechecked to ensure that there are no issues:
Library Link Configuration:
- Ensure that the library link is properly configured for both the main model and the linked subsystems.
- Verify that the library link is set up correctly, including the necessary library paths and dependencies, to ensure that all required functions and blocks are accessible.
MATLAB Function Block Dependencies:
- Check if the MATLAB Function block inside the linked subsystem has any dependencies on functions or variables that are not available or accessible.
- Ensure that all required functions and variables are properly defined and accessible within the linked subsystem and its parent model.
- Pay attention to any dependencies on custom MATLAB functions or external files that may not be linked correctly or have conflicting versions.
Code Generation Settings:
- If you are generating code from the model, verify that the code generation settings for the linked subsystems and the MATLAB Function block are compatible.
- Make sure that the code generation settings, such as the language, optimization level, and target hardware, are consistent for all linked subsystems and the MATLAB Function block.
- In some cases, certain code generation settings may cause conflicts or compatibility issues, resulting in errors when using linked subsystems with MATLAB Function blocks.
Compatibility with Linked Subsystems:
- Confirm that the MATLAB Function block is compatible with the use of linked subsystems.
- Some blocks, including certain variants of the MATLAB Function block, may have limitations or restrictions when used within linked subsystems.
- Check the documentation or release notes for your specific version of Simulink to ensure that the MATLAB Function block is supported in the context of linked subsystems.
Hope this helps.
