Atomic subsystem results into data dependency violation
5 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Hi,
I have a complex Simulink simulation. I have a subsystem usually run as non-atomic. Due to the need of making it as a subsystem running at a different sampling time from simulation time step of Simulink, I made it to be atomic. It was running OK for non-atomic but when I switched to atomic, the error below happened
"Input data dependency violation due to action subsystems. See Subsystem Examples in the Simulink library for valid and invalid examples of action subsystems".
I understand it may involve to a lot of detailed debugs with algebraic loop. Adding simple delays would help but I prefer not to if not having the understanding of the reason. Generally, what would be the reason that you could think of?
Thanks,
0 comentarios
Respuestas (1)
Jesús Zambrano
el 15 de Jul. de 2020
When converting a virtual subsystem into an atomic block, you are treating that block as a function where all its components are evaluate as a single unit. If that block is part of a loop, you might find problems if, at each sample time, the inputs of this block needs values from the outputs that come from the same blocks.
A similar question was posted and you can have a look here (see the asnwers including links to possible workaorunds):
0 comentarios
Ver también
Categorías
Más información sobre Schedule Model Components 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!