Comments on: Bus Signals in the Generated Code

By: Angelo

Angelo — Fri, 17 Jul 2009 15:55:27 +0000

Hi wei,

thanks for yous suggestion, but maybe I found something more general to my problem. My primitive problem was to read the signal names flowing on lines and it seems that more people have these issues:

http://www.mathworks.de/support/solutions/data/1-2JW10T.html?product=SL&solution=1-2JW10T

I encountered some more problem with masked blocks but I think it could be a good way to go.

Cheers

angelo

By: wei

wei — Thu, 16 Jul 2009 17:47:50 +0000

@angelo, what you had is a port handle. port of Inport type can't propagate signal. Your command will work for outport. Alternatively if line handle is available, you can always do

set(lineH,'signalPropagation','on')

@seth, Block parameter is fairly documented. But not line, prot etc. Maybe worth an entry here?

By: Angelo

Angelo — Thu, 16 Jul 2009 11:35:59 +0000

Hi Seth,

I’m looking for a way to transmit names of signals from Simulink to Matlab (in a structure?) but I encountered some problem. One way should be showing the propagated signals (from the Signal Properties…) but I need switching with a command (e.g. with a set_param command: something like

set_param(ln_sn_hand.Inport(j),'ShowPropagatedSignals','all');

) this line parameter from ‘off’ to ‘on’ (or to ‘all’) and it seems to me this is not a enabled parameter of the line.

Could you give some input about that?

Thanks

angelo

By: Seth

Seth — Thu, 15 May 2008 16:04:54 +0000

@Bob – I chose to specify the name because I wanted to shorten things up for the blog post. When I used the Auto or Subsystem Name option I got this:

19 /* Output and update for atomic system: '/ReusableFcn' */ 20 void simplebusdemo_nv_ReusableFcn(const main_bus *rtu_0, 21 rtB_ReusableFcn_simplebusdemo_n *localB) 22 {

I was just trying to avoid the line wrap.

Regarding parameterization using bus signals, this is a limitation of the current behavior of bus signals. Currently, bus signals can not inherit the Inf sample time, so they end up in the step function even if the inputs are constant. It should be possible to use a custom storage class to control the generation of the code for the bus and put the code into the initialization section.

By: Bob

Bob — Thu, 08 May 2008 13:00:38 +0000

Occasionally we’ve used busses to parameterize a model. To cut down on function interface overhead, the non-virtual bus makes sense. But if you use a set of Constant blocks to feed a Bus Creator outputting a non-virtual bus, the generated code looks like:
rtb_bus.bus1.Parameter1 = 7;
rtb_bus.bus1.Parameter2 = FRED;
rtb_bus.bus2.Parameter3 = 8;
instead of:
rtb_bus = { {7, FRED}, {8} };
And this usually appears in the step, not the initialize.

Is there a way to get the preferred output?

By: Bob

Bob — Thu, 08 May 2008 12:56:13 +0000

Any particular reason you chose to specify the name of the atomic subsystem? I try to avoid that in case I’ve used the block twice with different I/O data types, and usually find the name in the generated code comes close enough to the subsystem name to make traceability possible.