AnsweredAssumed Answered

about MATLAB cosimulation

Question asked by oochoo on May 12, 2008
Latest reply on Jun 1, 2008 by oochoo

Like • Show 0 Likes0
Comment • 10

In the current schematic of mine, in which directory should I put the *.m files?

When I created the Matlab cosimulation, I put it in the directory of "C:\users\default\adsptolemy\src\matlabipimport\matlab" and it has already been available in the left palette under "Numeric Matlab".

When I started up the simulation, it has the following errors:
"Could not load matlab library libeng"
and
"MatlabLibLink'M1':Please make sure Matlab is correctly installed".

Hope for help. 3X!

No one else has this question

Outcomes

10 Replies

ikoyfman May 13, 2008 8:43 AM
Mark Correct
Correct Answer
The simulation errors you cited are not related to the placement of the .m files. They concern your MATLAB installation.

If you're running on 64-bit Windows you need to use ADS 2008 Update 1 as previous ADS versions do not support 64-bit MATLAB cosimulation. Alternatively, you can install 32-bit MATLAB (the default MATLAB installation on 64-bit Windows is 64-bit; to install 32-bit MATLAB you need to run the 32-bit MATLAB installer manually). However, the MATLAB compiler won't work in the 32-bit mode on 64-bit Windows. Which is fine, because the script mode performance is equivalent to the compiled performance in the new MATLAB releases (a compiled MATLAB program today is just a wrapper around the regular interpreter).

If you're on 32-bit Windows, then you need to configure the system. Again, ADS 2008 Update 1 makes things easier, but if you're using an older version you need to make sure you have MATLAB in the system path and the MATLAB COM server is properly registered.

To place MATLAB in the system path, open the Windows Control Panel, System, Advanced tab; click on Environment Variables and add <matlab root>\bin\win32 to the PATH, where <matlab root> is the MATLAB home directory, e.g. C:\Program Files\MATLAB\R2007a. If you have multiple versions of MATLAB, make sure the path to the one you want to use in the simulation comes first. ADS 2008 Update 1 takes care of this step automatically.

To register the MATLAB COM server, open Windows Command Prompt and run the command matlab /regserver.

Finally, to answer your first question, the .m files are expected to be in the data folder of your ADS project.
Like • Show 0 Likes0
Actions
oochoo May 13, 2008 7:48 PM
Mark Correct
Correct Answer
First, thank you very much for your reply!

Indeedly, I'm running on 64-bit Windows. I'm using ADS 2008 Update 1. Also, the MATLAB R2007b is 64-bit.

When I setup the environment variable, there is only "win64" but no "win32" under C:\Program Files\MATLAB\R2007a\bin\. So I set "PATH=C:\Program Files\MATLAB\R2007a\bin\win64. You said that "ADS 2008 Update 1 takes care of this step automatically". But after I installed the ADS 2008U1, it seems that to set up the PATH environment variable manually is still required.

Now, I still have problem. The errors are the same:
"Could not load matlab library libeng
MatlabLibLink X1: make sure matlab is correctly installed."

What's the library libeng is for?

I have implemented the "setup matlab cosimulation" described in the ADS Ptolemy Simulation, that is "matlab /regserver". It's ok. But for "Finishing the MATLAB Compiler Configuration", warning said "mbuild is not recognized as an internal or external command, operable program or batch file" when I executed the "mbuild -setup" command.

Is there any place that I mistake?
Like • Show 0 Likes0
Actions
oochoo May 13, 2008 8:28 PM
Mark Correct
Correct Answer
On a 32-bit Windows computer,I also installed ADS 2008 and MATLAB R2007b.
I set up all of the requirements for the cosimulation.
I use the same MatlabLibLink as before.

But this time, the error is "MatlabLibLink 'X1': could not load MCR library".
What does this message mean? How could I resolve it?
Like • Show 0 Likes0
Actions
ikoyfman May 20, 2008 6:20 AM
Mark Correct
Correct Answer
At this point I recommend that you use SCRIPT mode. That'll take care of the MCR issue for now.

libeng.dll is the MATLAB engine interface. It should be in your <matlab root>\bin\win64 folder together with matlab.exe. If you're running ADS 2008 Update 1 on 64-bit Windows and you have executed "matlab /regserver" then the simulation should work.

In the ADS main window you should see Tools\Configuration Explorer menu. At the end of the PATH variable you should see the path to <matlab root>\bin\win64. Check for that and check that you have libeng.dll in that folder.
Like • Show 0 Likes0
Actions
oochoo May 26, 2008 7:07 PM
Mark Correct
Correct Answer
Yes. Now I'm converting to try the script mode model.
I am running ADS 2008 Update 1 on 64-bit Windows and have
executed "matlab /regserver". Also I checked the PATH variable and
it's <matlab root>\bin\win64 and also libeng.dll is in <matlab
root>\bin\win64 folder.
But still the simulation doesn't work.
The following is the error information given by ADS hpeesofsim:

Error detected by hpeesofsim during Ptolemy simulation initialization `DF'.
MatlabF_M `M1': Could not load matlab library libeng:
Error detected by hpeesofsim during Ptolemy simulation initialization `DF'.
MatlabF_M `M1': Matlab could not be invoked. Possible reasons are:
- All Matlab licenses are in use.
- You need to add Matlab bin\win32 folder to your PATH environment
variable.
- You need to register Matlab COM server. Run matlab /regserver from
Windows command line.
Error detected by hpeesofsim during Ptolemy simulation wrap up `DF'.
MatlabF_M `M1': Matlab could not be invoked.
Error detected by hpeesofsim during Ptolemy simulation wrap up `DF'.
MatlabF_M `M1': Matlab could not be invoked.

What's the reason that Matlab could not be invoked even if I have checked
the possible 3 reasons it gave.

Hope for your help.
Like • Show 0 Likes0
Actions
ikoyfman May 27, 2008 10:56 AM
Mark Correct
Correct Answer
I'm able to run a cosimulation on 64-bit ADS with 64-bit MATLAB. Does your MATLAB run properly by itself? Are you certain that you run 64-bit ADS? I can't think of a reason this wouldn't work. You may try using Depency Walker and see what's missing from libeng.dll: http://www.dependencywalker.com
Like • Show 0 Likes0
Actions
oochoo May 29, 2008 4:12 PM
Mark Correct
Correct Answer
Now I temporarily give up the co-simulation on Windows 64. We found that the 32-bit ADS and 32-bit Matlab can co-operate together, so I am now trying to do the co-sim on another computer which has 32-bit windows and also 32-bit ADS and 32-bit Matlab.

We are using the script mode and MatlabF_M model is employed. We referred to the example "DSP/dsp_demos_prj/networks/SOMBRERO.dsn".
Now the problem I encountered is when the Ptolemy DF engine run, it gives the error information which says"Function definitions are not permitted at the prompt or in scripts." Does it means that our .m function have wrong definition or something?
Like • Show 0 Likes0
Actions
oochoo May 29, 2008 4:20 PM
Mark Correct
Correct Answer
By the way, there is no custom-defined function in the Matlab main code. Only some Matlab built-in functions are called in the main code.
Like • Show 0 Likes0
Actions
ikoyfman May 30, 2008 2:27 AM
Mark Correct
Correct Answer
Yes, there must be something wrong with the script. Please contact our tech support if you need help debugging it.

I'd think Matlab_M type of component would be easier to use.
Like • Show 0 Likes0
Actions
oochoo Jun 1, 2008 9:58 PM
Mark Correct
Correct Answer
Thank you for your recommendation. Now I'm using the Matlab_M component and it is really easier to use.

Could you please tell me when writing Functions for "MatlabFunction" item, how to insert a new line after the semicolon to improve readability?

Just as the following example:
[output#2, output#1] = eig( input#2, input#1 );
if ( exist(`myEigFig') == 0 ) myEigFig = figure; end;
figure(myEigFig);
plot( output#1);

3X!
Like • Show 0 Likes0
Actions

about MATLAB cosimulation

Outcomes

Related Content

Recommended Content