Naming Problem that Occurs Repeatedly
2 views (last 30 days)
Show older comments
Hello, My problem is specific to SIMULINK, model and code generation advisor, and Embedded Coder.
I am using model referencing (i.e. Referenced models) in an integrated model and my subsystems have similarly named signals. When I was using Model Advisor to check my model for simulation and code generation problems, I got this error:
Error occurred during model compile.
Potential usage conflicts for identifier 'MdlrefDW_Other_Systems_Inputs_T'. This might occur when multiple referenced models have similar model names and similar naming rules. You can resolve this conflict by: increase the maximum identifier length parameter on the Symbols pane of the Configuration Parameter dialog, add different literal strings in identifier naming rules for each referenced model, or use dis-similar names for each referenced model
Potential usage conflicts for identifier 'MdlrefDW_Other_Systems_Inputs_T'. This might occur when multiple referenced models have similar model names and similar naming rules. You can resolve this conflict by: increase the maximum identifier length parameter on the Symbols pane of the Configuration Parameter dialog, add different literal strings in identifier naming rules for each referenced model, or use dis-similar names for each referenced model
Potential usage conflicts for identifier 'MdlrefDW_Other_Systems_Inputs_T'. This might occur when multiple referenced models have similar model names and similar naming rules. You can resolve this conflict by: increase the maximum identifier length parameter on the Symbols pane of the Configuration Parameter dialog, add different literal strings in identifier naming rules for each referenced model, or use dis-similar names for each referenced model
I understand that it occurs for similar/identical data ports and blocks that I may have. However, I grouped input and output port signals as non-virtual buses and it still comes up with this error. I don't understand why this is a problem? Why do I have to change my system because SIMULINK doesn't cope with names? Is it a limitation or is it something that I need to fix in SIMULINK. I don't want to change my system design names as the signals and parameter names are part of my customer specification. I tried to change the maximum length for identifiers from the config menu, but it violates my optimisation
The most confusing part is that the section that chuks this error out says "Identify questionable operations for strict single-precision design" but says that the names are similar or identical?!!!!
0 Comments
Answers (0)
See Also
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!