IadsRead in MatLab and/or Visual studio

137 views
Skip to first unread message

Adam Chant

unread,
Nov 17, 2009, 9:47:52 AM11/17/09
to IADS Group
I have a few questions as I pound away at a GUI for my engineers w/o iads.
When I run my GUI I get the following warning:
"Calling MEX-file 'C:\Program Files\IADS\MatlabExtension\iadsread.dll'.
MEX-files with .dll extensions will not execute in a future version of MATLAB."

Short of building a time machine out of a DeLorean can anyone tell me what
future version of MatLab will no longer support the .dll ? I'm running R2008b
and am hesitant to upgrade.

Also Sorry if this has been covered, but is there another iadsread type of
interface for visual studio?

Is it IadsAutomationLib or IadsConfigInterface?

Thanks,
-Adam Chant

Michael Jones

unread,
Nov 17, 2009, 12:46:35 PM11/17/09
to IADS
I did some quick research on the .dll convention for MEX.
http://www.mathworks.com/access/helpdesk/help/techdoc/rn/broifyr-1.html
Looking at some discussions on the topic It appears that all you would
need todo is rename the file from *.dll to *.mexw32 although matlab
indicates it would need a recompile. Evidently this is not yet
implemented through MATLAB Version 7.7 (R2008b) Is there a newer
version yet?

Your starting point in VB or VC would be Iads.Application. There are
quite a few examples in the files section here on google, or throw up
any questions that come up here on the group.

Finding a DeLorian shouldn't be too hard, but sourcing a flux
capacitor and 1.21 gigwatts of power is gonna be a problem!

James Bretz

unread,
Nov 17, 2009, 12:49:21 PM11/17/09
to ia...@googlegroups.com
Hi Adam,

> When I run my GUI I get the following warning:
> "Calling MEX-file 'C:\Program Files\IADS\MatlabExtension\iadsread.dll'.
> MEX-files with .dll extensions will not execute in a future version of
> MATLAB."

Ya Adam. That's nothing to do with your program or even the dll contents.
It's actually that Matlab is again breaking the existing mex interface.

From what I understand, all we need to do to "fix" this issue is to rename
the iadsread.dll to iadsread.mex32. Give it a shot and see it the warning
goes away.

Since a number of people are using 64Bit Matlab, we'll probably have to
produce a 64 bit version soon. In the end it will be iadsread.dll (older
versions), iadsread.mex32, and iadsread.mex64
Jim

Reply all
Reply to author
Forward
0 new messages