Bug : MatlabString cannot be cast to StructMatlabData

[phanthanhliem]

Hi,

I've just encountered a bug when i tried to export. The problem context is below
I have an slx model : "Plant_And_Control_FMU.slx".
I import it into "Plant_And_Control_FMU.simulink". No problems here, everything seems fine.
I then tried to export "Plant_And_Control_FMU.simulink" into "Plant_And_Control_FMU.slx" (in another folder, of course).
I haven't changed anything in the model.simulink, nothing.

Then I've got this error:

I have no idea about this kind of casting error.

[phanthanhliem]

I regenerated "Plant_And_Control_FMU.simulink", and reexport to obtain "Plant_And_Control_FMU.slx". There is no error this time. I don't know why the first import/export has the error like that.

[abelhegedus]

Thanks for the report! I suppose you no longer have the original .simulink that caused the error? It would be interesting to compare them to see if they differ in anything. If not, then there is some other setting or environment issue that caused it.

[phanthanhliem]

Hi abelhegedus,

Actually, the error of the first export is my fault, i didn't config correctly the library FMI toolbox, a library which allow us to import and export the FMU block. You can download the demo version here: http://web.modelon.com/cn/aavt4/fmit-download.
I have tried both licence & demo version, but both don't work.

The second exportation has no error, but the output was exactly the model with the same name (Plant_And_Control_FMU.slx), which exists in one of the path in Matlab.
You can see the warning here:

I dont understand why Massif write the output in the output directory as if it was a successful export,
although it did nothing but copying the whole model.

And finally, i still couldn't export "Plant_And_Control_FMU.simulink" into "Plant_And_Control_FMU.slx".
The errorneous exported model:

The origin model: Plant_And_Control_FMU.slx

And this is the error message from MASSIF:

I've tried import/export a model called "Plant_And_Control.slx" (a complex model) without using FMI Toolbox, it works fine. No problem at all.

Do you have any clue to import/export a model which use third party library (like FMI Toolbox) in this case?

[abelhegedus]

We will take a look at the issue, there should be no restriction on third party libraries. @imbur do you have any ideas?

[abelhegedus]

Check if problem still exists and add test to repo.