MEX file for MCC DAQ

I have a MCC USB-205 DAQ, the speed of it is very less because it doesnt support foreground and background operations. I thought of writing an MEX file to increase the speed of it. I downloaded the code from https://in.mathworks.com/matlabcentral/fileexchange/31989-sending-digital-codes-with-measurement-computing-boards-with-mex but i get the following errors,

>>mex digCode.c

Building with 'MinGW64 Compiler (C)'.

Error using mex

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0xc8): undefined reference to

`cbDConfigPort'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0xda): undefined reference to

`cbDConfigPort'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0xec): undefined reference to

`cbDConfigPort'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0x15c): undefined reference to

`cbDOut'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0x186): undefined reference to

`cbDOut'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0x1a4): undefined reference to

`cbDOut'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0x1c0): undefined reference to

`cbDOut'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0x230): undefined reference to

`cbDOut'

C:\Users\vin\AppData\Local\Temp\mex_24630160086887_8472\digCode.obj:digCode.c:(.text+0x24e): more undefined

references to `cbDOut' follow

collect2.exe: error: ld returned 1 exit status

Can anyone help me with it. Where can i find supporting documents to write mex file for mcc daq.

Answer 1

[Walter Roberson]

https://www.mccdaq.com/daq-software/universal-library.aspx

[A R]

Yes i downloaded the universal library for android, eclipse and android studio. But still i get this error

[Walter Roberson]

You need to ensure that the directory of the header file is included with a -I . For example,

mex -IC:\Users\vin\UniversalLibrary\include digCode.c

except with the path set to whatever is appropriate for your system.

You might also need a -L and -l to link the dll properly.

[A R]

thanks a lot. where will i find such informations to write mex file for data acquisition

[Walter Roberson]

This is standard compiler options. -I (capital eye) to name a directory that holds include files. -l (lower-case ell) to indicate the basic name of a dll to link against. -L (capital ell) to indicate a directory that holds dlls to link against (you would typically use -L to name the directory and then -l to name the library in the directory)