How to use Nokia PC Connectivity API in labview?

[larryD]

I wish I could use the camera on my Nokia phone in my labview project, in this case the AT command doesn’t apply. I guess Nokia_PC_Connectivity_API_3.2  (consist of LIB files and  header files)  might be useful, but I don’t know how to load a static library in Labview.  Do I have to write a C program first before labview could use those API function? Or is there a simple way to control my nokia phone?

Would be grateful if anyone could help!

[MikeS81]

Hi larryD,

if you have a dll, then you can call the exported functions with the "Call Library Function Node". No need to write a C program.

Mike

[larryD]

Thanks Mike, I'm going to try ur suggestion.

[thomaschae]

Hi,

Did you find the solutions how to use static library? I have the same issue, here.

If so, please share with me. (thomaschae@paran.com)

Thanks,

Thomas-

[Neil_Li]

 You can use the Tools>>Import>>Shared Library(.dll) in LV to create VIs for your DLL for convenience.

[Neil_Li]

 You can use the Tools>>Import>>Shared Library(.dll) in LV to create VIs for your DLL for convenience.

[thomaschae]

It supports DLL(*.dll) only, not LIB(*.lib). I need LIB interface.

Possible options are,

1) to make a new DLL calling LIB by using C/C++ complier (ex. visual c), then use "Call Library Function Node",

2) to generate new c source code calling external LIB, then using CIN(Code Interface Node).

They looked available, but  NI has addressed that either one won't work, unless original code desinger makes a new clean dll. 

Do you have another idea? 

Message Edited by thomaschae on 03-04-2010 10:00 PM

[rolfk]

---

thomaschae wrote:

It supports DLL(*.dll) only, not LIB(*.lib). I need LIB interface.

Possible options are,

1) to make a new DLL calling LIB by using C/C++ complier (ex. visual c), then use "Call Library Function Node",

2) to generate new c source code calling external LIB, then using CIN(Code Interface Node).

They looked available, but  NI has addressed that either one won't work, unless original code desinger makes a new clean dll. 

Do you have another idea? 

---

Don't go the CIN route! They are legacy technology and not supported anymore on all LabVIEW platforms. The shared library (Call Library Node) interface is the way to go nowadays.

And I don't understand your second last sentence. A lib while having the same file ending is not a standard format as its internal layout and format depends highly on the compiler that was used. So there is no way NI could make a general purpose interface node to interface directly to lib files. It is even so bad that a lib created with one comiler can not usually be used with a different compiler.

Message Edited by rolfk on 03-05-2010 07:44 AM

[thomaschae]

Yes, my point was that we don't seem to have any way to use library(*.lib) file.

I requested the original library maker to develop DLL file available to LV environment and the result seems now promissing.

Thanks, all.

Thomas-