Why do I get an error when using the same get or set functions for different signal objects in a Simulink model with Embedded Coder R2014b or R2015a?
15 views (last 30 days)
I have a Simulink model with different signal objects with GetSet Custom Storage Class using the same get or set functions. This worked with Embedded Coder R2014a. I recently upgraded to R2014b and get an error message related to "Potential conflicting usages of identifier <get/set_function_name>". Why do I get this error and how can I resolve this issue?
This is an expected behavior. Though this workflow might have been possible in Embedded Coder R2014a, it was not an intended or desired workflow. Hence, it is no longer supported in Embedded Coder R2014b and later releases.
In Embedded Coder R2014b and later, if you have different signal objects connected to different signals, you need to use different get and set functions for these. Alternatively, you should use the same signal line for common get or set functions.
Though not recommended for code generation, you can use the following workaround to avoid this error during simulation when multiple signal objects share get or set functions:
(1) Open the 'Configuration Parameters' editor for the model.
(2) In the 'Code Generation' pane, select the ERT-based 'System target file' (ert.tlc).
(3) Enable the option 'Ignore Custom Storage Classes'.
More Answers (0)