Why Bus Selector unable to identify input signals ?
213 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
ing ming chew
el 30 de Oct. de 2020
Comentada: ing ming chew
el 2 de Nov. de 2020
I am connecting a Model predictive controller unit to a TITO system. It is controlled by closed loop. When running the simulation, error message below was pop up.
The signal connected to the input port of 'MultvariableTank3aTestOnly/Bus Selector1' is not a bus signal. The input to the Bus Selector block must be a virtual or nonvirtual bus signal. A possible cause of this error is the use of a bus-capable block (such as Merge or Unit Delay) that in this current situation is unable to propagate the bus downstream to the block reported in this error. Please see Simulink documentation for further information on composite (i.e. bus) signals and their proper usage.
Component:Model Predictive Controller | Category:Find Operating Point error
Could somebody advice me how to solve it? Really appreciate it.
Anthony
3 comentarios
Rhea Chandy
el 2 de Nov. de 2020
To add to what RenatoL said above,are you using a Mux block or a Merge block to combine inputs? It may be helpful if you share your model so that I can see where is the issue has come up.
Respuesta aceptada
Rhea Chandy
el 2 de Nov. de 2020
Hi, it seems like you are getting this error because you're using a bus selector block for the output of the MPC block.
Consider using Demux block to extract the components of the input MPC signal and output separate signals. Also use Mux blocks to combine the input signals. Further, In the example you've showed, it is mux and demux blocks that are used.
Más respuestas (0)
Ver también
Categorías
Más información sobre Linear Plant Specification 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!