Embedded coder single task tunable time step
3 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Ben Rancici
el 16 de Oct. de 2019
Comentada: Ben Rancici
el 26 de Mzo. de 2020
In my embedded generated code, one "magic number" still remains: the time step (used in Discrete Integrators or Filters code for instance).
I would like to make this time step tunable by using a dictionary entry with "Define" Storage Class, so I could make it consistant with the actual time step of my target.
Whatever the storage class I choose, in the end the generated code still has a numerical value instead of a tunable variable.
Is this normal? Is there a workaround?
0 comentarios
Respuesta aceptada
Nick Sarnie
el 18 de Oct. de 2019
Editada: Nick Sarnie
el 18 de Oct. de 2019
Hi Ben,
It sounds like you are trying to make the 'Sample time' parameter on blocks be tunable in the generated code.
This is not possible, because changing the sample time effects other parts of the model, such as sorted block order, data transfers, sample time propagation, and more. It's not as simple as changing a variable value in the geneated code.
A link with more information: https://www.mathworks.com/help/ecoder/ug/modeling-semantic-considerations.html#f1116518
If you want to have a model that is sample-time independent, consider using model reference: https://www.mathworks.com/help/simulink/ug/inherit-sample-times-for-model-referencing-1.html
However, this will use the sample time of the Model Reference block in the upper model.
Thanks,
Nick
Más respuestas (0)
Ver también
Categorías
Más información sobre Deployment, Integration, and Supported Hardware en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!