One or more output arguments not assigned during call to "AcqNUpdates_nonUI".

[chcsott]

>> [data, time, initial_time, code, source, status] = AcqNUpdates_nonUI('dev1/ai0', -2, 2, 10, 10, 10)

Warning: LabVIEW MEX-File Error - Parameter 1: Failed to load some MEX-function DLLs installed by The

MathWorks, Inc. MATLAB(R). These DLLs include libmx.dll and libmex.dll. They should be installed when

MATLAB(R) is installed. Make sure they are in the system's path. 

??? One or more output arguments not assigned during call to "AcqNUpdates_nonUI".

Not sure what's going on here... AcqNUpdate_UI seems to work fine... (though it still gives the libmx.dll, libmex.dll warning) 

I did add the \R2009a\bin\ path for libmex.dll but it didn't seem to stop the warning. I cannot find libmx.dll...

Any help would be appreciated. 

[chcsott]

Sorry, libmx.dll is in \R2009a\bin\win32 and that path has been et.

[chcsott]

I am running Matlab R2009a Version 7.8.0.347

The readme says NI DAQ toolbox has been verified on versions 13 and 14.

Could this be the root of my problems? I think there may be confusion between "release" and "version"? 

Message Edited by chcsott on 10-28-2009 03:18 PM

[Little_Helper]

Hello Chcsott

I ran into the same problem when upgrading from Matlab R2007b to Matlab R2009b. According to the Matlab help in R2009b it is stated:

In the future, on 32-bit Microsoft Windows systems, MATLAB will not support MEX-files with a .dll file extension. In MATLAB Version 7.7 (R2008b), if you run a MEX-file with a .dll file extension, MATLAB displays a warning. 

As I read it, this means that mex-files compiled in Labview and Math Interface Toolkit will not work in future versions after Matlab R2008a.

I have contacted Labview support Denmark to find a solution, but we are still working on this.

This is a big problem to me, because now most of my code do not work anymore, unless I use Matlab R2007b.

Best regards

Simon Bøgh

MSc. Eng. Manufacturing Technology

[miskoL]

Hi,

may i know what is the update on this situation? i'm facing the same problem currently.

[BROhan]

Hi miskoL,

I'm sorry. I don't really understand exactly what your issue is. Could you be a little more specific what problem you are referring to? Are you trying to use the  Math Interface Toolkit or DAQmx hardware?

[miskoL]

Hi BROhan and thank you for your concern,

i want to create a program that will acquire data each time a trigger occurs. the data stays in the hardware, and if a trigger occurs again data is saved. then only after N number of triggers, all the data is transferred to PC in a single transaction. 

note: software that i'm using is MATLAB 2009a, hardware is NI USB-6218
p/s: below is not the coding, just a block diagram of the flow.

start(ai)

wait dio input
single scan %let's visualize the data is saved in hardware buffer here. data(1,1)
wait dio input %daq stop/pause/hold acquisition
single scan %data(2,1)
wait dio input
single scan %data(3,1)

stop(ai)
getdata %transfer all data to PC after N number of scan(this example is 3) ---> data = [1;2;3;....N;]

i have tried some of the examples provided, 

ContAcqTriggerStart_UI.m = starts acquisition when i triggered pfi0(the triggering start is what i want), but continuous acquisition is not what i want.

FiniteAcqTriggerStartAndRef_UI.m = this is mostly what i want, even though the Reference part is not what i wanted, but i can just neglect pre-triggered data. there's 2 problem with this one, the data is not saved in a buffer, each trigger transfer the data to PC(i dont desire this), another problem it's a gui.

FiniteAcqTriggerStart.m = this is a coding (non gui) example. this probably is the key to solve some of my problem(it's a start i might say). unfortunately, it cannot be used.

the syntax to run the code is (i followed the guideline):

[data, time, initial_time, timed_out] = FiniteAcqTriggerStart ('dev2/ai0',-10,10,100,1000,'pfi0',0,10)


Warning: LabVIEW MEX-File Error - Parameter 1: Failed to load some
MEX-function DLLs installed by The MathWorks, Inc. MATLAB(R). These DLLs
include libmx.dll and libmex.dll. They should be installed when MATLAB(R) is
installed. Make sure they are in the system's path. 
??? One or more output arguments not assigned during call to
"AcqTriggerStart_nonUI".

Error in ==> FiniteAcqTriggerStart at 146
[data, time, initial_time, code, source, status] =
AcqTriggerStart_nonUI(Physical_Channel, Minimum_Value, Maximum_Value,
Samples_per_Channel, Sample_Rate_Hz, Trigger_Source, Edge, Timeout);


the gui can run even though it also gave the same warning.

Please help, thank you.

[EEsRULEtheWORLD]

Hi miskoL,

Mex.dll files are no longer supported in version Matlab® 2009a or greater.  You will need to use Matlab® 2008b or earlier in order to avoid this error.

MATLAB® is a registered trademark of The MathWorks, Inc. Other product and company names listed are trademarks and trade names of their respective companies.

[miskoL]

Hi,

thank you for the reply. may i ask what is your suggestion without me changing my matlab version, and solve my described problems above?

Thank you.

[EEsRULEtheWORLD]

Hi miskoL,

Unfortunately, you will need to use a Matlab® 2008b or earlier.  There is currently no development being done on our end to support Matlab® 2009a or greater.  I apologize for the inconvenience.

MATLAB® is a registered trademark of The MathWorks, Inc. Other product and company names listed are trademarks and trade names of their respective companies.