Using a bus-signal as an Input into a 'Model'-Block in Simulink
4 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Sönke Matthiesen
el 30 de Jul. de 2019
Comentada: Fangjun Jiang
el 2 de Ag. de 2019
Hello everybody,
I am currently working on quite a complex simulink-model. To make the model more modular I wanted to use the 'Model'-Block to allow an easy swap between pre-defined models. However since the model is very complex I am currently using bus-signals(virtual) to make the model more "readable" and it seems, that those signals do not get recognized by the 'model'-block and its contents. The error-message I receive is, that the signal in the 'Model'-Block is not a bus-signal, althought the signal I input is.
How do I get around this issue? I want to the modularity of the 'model'-block with the usability of the bus-signals. Are there alternitives? If not, then what does the bus-signal turn into, once it 'crosses' over to the 'model'-block?
Thank you in advance for your answers!
0 comentarios
Respuesta aceptada
Fangjun Jiang
el 30 de Jul. de 2019
see the demo model: sldemo_mdlref_conversion
2 comentarios
Fangjun Jiang
el 2 de Ag. de 2019
The error must be caused by something else. It sounds like a mismatch issue. It is expecting "Bus1.Bus2" but 'mysignal' is feeded, or vise versa.
You can certainly select any signal or bus element (no matter how "deep") within a bus using a BusSelector block. In the demo model (after the conversion), try to add LIMITBUS.lower_limit at the first BusSelector block inside the reference model.
Más respuestas (0)
Ver también
Categorías
Más información sobre Simulink Environment Customization 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!