Modelica.Blocks.Routing.Extractor doesn't work

[Peter Junglas]

In the attached model the input is a const 4-vector, the index runs periodically from 1 to 4. The output is not the corresponding vector element, but is constant.

[Peter Junglas]

model file

[Adrian Pop]

Hi,

Can you add a bit more info on this:
What MSL are you using?
What should the output look like?

Cheers,
Adrian Pop/

[Peter Junglas]

Sure. I'm using MSL 3.2.1, OpenModelica 1.9.0 beta 2, r14139 as of today.

The extractor gets the vector [1.1, 2.2, 3.3, 4.4] as input u, the index runs cyclically from 1 to 4, changing every second. Therefore the output should be (1.1, 2.2, 3.3, 4.4, 1.1, 2.2, ..), changing every second. But it is constant, = 1.1 .

If I use my own extractor block using the MSL code but dropping the line

"when {initial(),change(index)} then"

(and the "end when" of course)

then it works. So I assume there is a problem with OpenModelicas event handling.

Two further remarks:

• Yesterday the sawtooth block worked, today it runs amok! Have a look at its output in TestExtractor to see what I mean!

• In OMEdit you cannot connect the multiplexer output with the extractor input. OMEdit asks for an index, then (giving "1") shows an error message ("Unmatched dimension"). Obviously it cannot connect vector signals.

Hope that helps.

Greetings from Diepholz/Germany

Peter

[Willi Braun]

The issue with sawtooth is fixed in r14197.

The other problem with the extractor is that we don't generate events for functions ceil, floor, div, mod, rem.

[Willi Braun]

fixed in r14235.