Function variables are resolved in the workspace, not a .Simulink.Signal. object
44 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
This is part of an encryption algorithm that produces a matrix.
Variable 'img' is resolved in workspace ('base') for block 'test01/MATLAB Function4' but it is not a 'Simulink.Signal' object.
7 commentaires
Paul
le 31 Jan 2023
It would be better to copy/paste the code here as text rather than an image.
Is lambd a scalar? If not, that code won't run at all because the output of mod is a matrix and X(i) is sclar.
Also, I suspect that reshape call is going to be a problem. The code generator needs to be able to figure out the size of img based on the code and/or the properties of the input and ouputs to the function, not the values of the inputs. Unless maybe img is supposed to be a variable size array.
Setting all that aside, this code in and of itself should not be causing any errors about img being global. I think there's a lot more about the workflow that causes the the problem, which hasn't been shown here.
Réponse acceptée
Fangjun Jiang
le 31 Jan 2023
Modifié(e) : Fangjun Jiang
le 31 Jan 2023
In the MATLAB Function block editor, click menu button "Edit Data", in the "Property Inspector", "Symbols" section, find and select the item for "img". In the "Advanced" section, you must have checked the "Data must resolve to signal object" option.
If this is not your intention, un-check it. It seems that this is likely the case. This will get rid of this error.
If it is, then you need to create a Simulink.Signal object in base workspace and set many properties.
img=Simulink.Signal
open img
0 commentaires
Plus de réponses (0)
Voir également
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!