Problems with import of Simulink Model in Activate
Hello,
i'm pretty new to Activate and Altair Tools in general. In the past i just worked with Matlab / Simulink.
I am trying to import my Simulink model into Active, but i get multiple Errors in my Command Window. Below are some examples.
When i start the import i just get multiple errors like these and nothing else happens.
Is there a smooth way to find out what these error's mean and how i could fix them?
Thanks for your help.
Aiko
Error: error when executing 'C:\Users\kbrm\AppData\Local\Temp\Tempdir_6cKB6e\simport.bat': simport warning:
xml deep ast to xml explicit ast: dropping 'Object' implementation section items
simport warning:
xml deep ast to xml explicit ast: dropping 'Object' implementation section item
simport warning: xml deep ast to xml explicit ast: dropping unit
simport warning:
Xml_explicit_ast_to_mdl_ast: graphical binding for ident FunctionName was droppedsimport warning:
during block translation,
Implicit coercion of string ``3'' to an integer for ident 'NumInputPorts'
simport warning:
during block translation,
'block Winkel\n, with type Scope',
Neither SampleTime, nor tsamp, nor sample_time was found
in the block arguments, using default ('Inherit' mode)
simport warning:
Xml_explicit_ast_to_mdl_ast: graphical binding for ident Inputs was dropped
Answers
-
Hi Aiko,
The list only shows warnings with not much importance. Please provide the complete output messages, if available.
Regards
0 -
Hello RoKet,
the full ouput message is too long for this post, so i attached it as a txt.file.
Thanks for your help!
Aiko
0 -
Hi Aiko,
Unfortunately there are too many messages, and the list stops before an interesting error message appears. I propose to split you model into several parts and import them separately.
Here are some common hints for a successful import (thanks to @Ramine and @christiankeh)
- Import of *.m files only works for parameters defined in this file, not for functions. To make this work as expected, you have to rename the file file extensions from*.m to *.oml and either ddd the path to the *.oml-files to the ModelInitialization script or open the corresponding path to the *.oml-files in th FileBrowser
- Sometimes the importer can't recognize the correct output port size. In this case the row size of the output port has to be set manually. It happens e.g. if a Demux block is attached to the output port.
- If an error message stating that the code within an OML block is too long, you can solve this, by “unchecking” the attribute “Atomic” in the superblock.
Regards
0 -
Hi, I am getting the same error
can you help me with that?0