jtliang Registered: 12/18/08
Posts: 1
|
|
| |
Reply with quote | #1 | I tried to import a very basic Simulink model to test out the process. Basically, the simulink model was a step input to a transfer function block to a scope.
When I import using the Vissim Simulink import feature, I get this very cryptic message.
could not complete conversion of the SIMULINK model
Syntax problem in line: 5
{ expected
Also, the import log is below.
----------------Compiling...
Line 4 : warning: the common parser was loaded. Requested parser [GraphicalInterface]
I am not sure what is going on. Did I install Vissim incorrectly. I'm running Simulink version 6.4 (R2006a)
|
| Loading... | | |
a_a Registered: 03/30/07
Posts: 10
|
|
| |
Reply with quote | #2 |
Everything is OK with VisSim installation. Also, the problem is not in the complexity of the model. Every new Simulink release has slightly different syntax of .mdl files. That's what happened in this case, we just missed something. If you can send the model to support@vissol.com I'll take a look. |
| Loading... | | |
a_a Registered: 03/30/07
Posts: 10
|
|
| |
Reply with quote | #3 | The current Simulink translator build is 35. To check the version of the translator one has to locate simflt.dll in the VisSim folder and do Properties > Version.
That Simulink 6.* file format is supported starting from the build 34.
|
| Loading... | | |
poisonivy83 Registered: 10/05/09
Posts: 1
|
|
| |
Reply with quote | #4 | Hi.
I am also facing the same error. I have checked the build of Vissim as 35 and of Simulink is 6.1. Can you please look into the issue. Its a very simple Simulink model
Attached Files:
firstOrderTransferFn.zip (4.62 KB, 1 views)
|
| Loading... | | |
a_a Registered: 03/30/07
Posts: 10
|
|
| |
Reply with quote | #5 | I did not get that error message on my computer. It is possible that your VisSim uses Simulink translator from different location. To check this out, open vissim.ini and search for
diagramFilters32
The left hand side value shows where your actual Simulink translator is.
|
| Loading... | | |