matlab script sever don't work in labview

[zjwever@yahoo.com.cn]

in my application ,matlab script always doesn't work with a error1050,even the matlab script examples in labview help examples also can't work at all, can you
tell me the reason.

[pawel]

Maybe the version of Matlab alb LV would give some clues?
regards
Pawel

[Randy_H]

Depending upon the version of LabVIEW and MATLAB that you are using, please see the following KnowledgeBase from our web site:

KnowledgeBase 2C1AH6DM: LabVIEW 6.x and Earlier Does Not Interface Properly with MATLAB 6.1 or MATLAB 6.5 [broken link removed; article no longer available]

Randy Hoskin
Applications Engineer
National Instruments

[marc lawrence]

We have a similar problem with LV (any version) and a clean installation of matlab 6.5 We raised a query with NI - but have not had an answer... In the end im having to write a new CIN to do DCOM in order to solve the problem.... which is annoying.

[wha@atmel]

find here a comment from a different user group:

"I have updated a collection of VIs for reading and writing MATLAB .mat
files. It supports most popular data types - 2D arrays of DBL, SGL, I32,
I16, U16, U8, CDB and CSG, and 1D arrays of STR. It is useful for data
exchange with MATLAB, but I also find .mat format convenient aside of MATLAB
for storing multiple variables in binary format. These VIs are freeware;
those interested can download them by following this link:
http://solidusintegration.com/MatlabFileReadWrite.zip
I will appreciate any feedback on this library.
Sergey Liberman "

regards
wha

[marc lawrence]

Thanks, but we will be doing most things on DCOM (ie across networks).

So I am not the only one with this problem...

[Sergey Yakovlev]

Nevertheless I would suggest to try with corrected dll attached above. Put
matlab service in manual mode.
On PC it works.

"Marc" wrote in message
news:506500000005000000C5060100-1042324653000@exchange.ni.com...
> Thanks, but we will be doing most things on DCOM (ie across networks).
>
> So I am not the only one with this problem...

[marc lawrence]

Hi Sergey

Yep the files look interesting - as well as the control. The actual application is to make sure we have realtime data exchange along with 'callback' functionality. There are a variety of approaches - reading .mat files, using DDE and COM. NetworkDDE is not supported by matlab - so that is one option gone. Using shared network drives is a solution - but still means Matlab and Labview are mutually dependant. With DCOM (and Matlab in /Automation mode) it is possible to have two 'masters' talking independantly without shared network drives...
I think at the end I will have to construct a new control (or cin) module to do this...
Marc

[Sergey Yakovlev]

Marc,

You have one forgotten possibility to communicate LabView with remote
MATLAB - it is TCP/IP.
It is easy to realize and may be helpful in your application.

Regards,
Sergey.

"Marc" wrote in message
news:506500000005000000DE060100-1042324653000@exchange.ni.com...
> Hi Sergey
>
> Yep the files look interesting - as well as the control. The actual
> application is to make sure we have realtime data exchange along with
> 'callback' functionality. There are a variety of approaches - reading
> mat files, using DDE and COM. NetworkDDE is not supported by matlab -
> so that is one option gone. Using shared network drives is a solution
> - but still means Matlab and Labview are mutually dependant. With DC
OM
> (and Matlab in /Automation mode) it is possible to have two 'masters'
> talking independantly without shared network drives...
> I think at the end I will have to construct a new control (or cin)
> module to do this...
> Marc