Modelica.Electrical.Digital.Sources.Table

[Christian Schubert]

Hi,

while comparing results I found that Modelica.Electrical.Digital.Sources.Table produces wrong results which causes many MSL Models to fail comparison.
The table is written as a simple algorithm and the data is stored as an array. Thus it is all pure Modelica and therefore critical.

See the attached picture and model for details.

[Willi Braun]

As far as I see it's not a runtime issue. Just the enumeration to integer are translated different:
x={Logic.'U',Logic.'X',Logic.'0',Logic.'1',Logic.'Z',Logic.'W',Logic.'L',Logic.'H',Logic.'-'})
OM: x = {1,1,2,3,4,5,6,7,8};
Dymola: x = {1,2,3,4,5,6,7,8,9};

[Martin Sjölund]

Did you use the exact same version of MSL? It might be that the trunk uses a different table.

[Christian Schubert]

I've reran it again with Dymola and MSL 3.2.1 and I got the same result.

But surely, Logic.'U' and Logic.'X' should be mapped to different integer values, right?

[Martin Sjölund]

Ok, this is a bit weird... I got the following array in the code using just that assignment...
static const modelica_integer _OMC_LIT0_data[] = {1, 1, 2, 3, 4, 5, 6, 7, 8};

Maybe I can fix this before I go to Canada...

[Martin Sjölund]

Should work in r14168 but did not run tests.

[Adrian Pop]

This seems to be fixed now. Christian, can you enable the test for it in msl32?