Variables in the base workspace can be accessed from the event actions of the Entity Generator. Additionally, mask-specific parameters, MATLAB variables, and parameters in the model workspace are also available from the event actions section. For further details, the following command provides more information:
web(fullfile(docroot, 'simevents/ug/event-action-languages.html#bvckoh2'))
A variable can be placed in the base workspace, and the assignin function can be used within a MATLAB Function block to set its value during simulation. However, this may not be of much use as the updated value will not be reflected in the Entity Generator, as base workspace parameters used in Simulink are intended to remain constant throughout the simulation. Also, since assignin does not support code generation, it needs to be defined as coder.extrinsic. An alternative here is to use Dashboard Blocks:
web(fullfile(docroot, 'simulink/ug/tune-and-visualize-your-model-with-dashboard-blocks.html'))
However, If the variation of the entity's attribute value is simple enough, I recommend defining a Simulink Function that outputs the entity's attribute value. This Simulink Function can be called within the Entity Generator to set the attribute value, as illustrated below.
Alternatively, modifying the Entity Generator block to accept the attribute's value as input is another option, especially for more complex or permanent use cases. More information on this can be found with the following command:
web(fullfile(docroot, 'simevents/ug/custom-entity-generator-block-with-signal-input-1.html'))
