How to build a dll for labview pda, which uses the intel ipp primitives in it

Hi all,
For my application, I need to call a c dll from Labview PDA, and in the c function i need to use intel IPP function. When i call my dll, i get an error saying the ippfunction i use, say "ippsCopy_16s missing c or vi file". Can someone tell me what I might be doing wrong?

Hi Vani,
When using a DLL in a PDA there are some special considerations you have to take. Please take a look at the following knowledgebase describing the process.
Eli S.
National Instruments
Applications Engineer

Similar Messages

Error message when building an application for Labview PDA

When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
When looking at the error log, it reads "The system cannot find the file specified."
This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
When installing Labview PDA, I installed files as follows, and in this order:
(i) Labview 7.1 (installed previously)
(ii) Microsoft eMbedded Visual C++ 4.0
(iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
(iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
(v) Microsoft ActiveSync 3.8
(vi) NI Labview 7.1 PDA module for PocketPC
(vii) DAQmx Base 1.0 for PDA or later
Any ideas?

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

How to create a DLL for LabVIEW in MatLab

I want to use MatLab-Code from an M-file in LabView without MatLab. So i decide to use external code in a DLL. Can anybody give me some hints - how to do? (How to create, how to use?)
Used System Windows 98, LabVIEW 6.1, MatLab 6.1 R12.1
Thanks

Hi,
I use Matlab-Code in Labview and it's don't need create a dll. The LV was a tool, matlab script, you can write your code Matlab here. see the examples of LV.I think the lV 6.1 have.
Dll it's very complicated

How do I tell if my i7 MBP is using the Intel HD or Nvidia 330?

Can someone please tell me where can I identify if my MBP i7 is using the Intel and or the Nvidia?
I know that the system is supposedly delegating these actions from one to another, but I am trying to monitor my battery life as it appears to be running a tad short from what Apple is stating is feasible.
Any assistance would be greatly appreciated.
Thanks.

Some info here that will help http://www.markc.me.uk/MarkC/Blog/Entries/2010/4/21Early_2010_Macbook_Pro_-_Battery_LifePoor.html

How to remove the "int len" of my return string on the DLLS header when building a DLL on LabVIEW 8.5

Hi all.
I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors.
But LabVIEW creates another output, the lenght of the return string.
This is a problem because I have other DLLs and I need them to be compatible.
How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer?
String Handle Pointer removes the length from the header but I don't know the difference between this data types.
Thanks in advance for the help.
Daniel Coelho
Portugal
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda

Daniel Coelho wrote:
Hi all.
I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors.
But LabVIEW creates another output, the lenght of the return string.
This is a problem because I have other DLLs and I need them to be compatible.
How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer?
String Handle Pointer removes the length from the header but I don't know the difference between this data types.
Thanks in advance for the help.
Daniel Coelho
Portugal
C string pointer is a pointer to a memory location whose string information is terminated by a 0 byte. Pascal String Pointer is a pointer to a memory location where the first byte specifies the number of bytes to follow. This obviously allows only for strings up to 255 character length.
LabVIEW String Handle is a pointer to a pointer to a memory location where the first 4 bytes are an int32 value indicating the number of characters to follow. You can read such a String handle in a function without many problems, but you can only create, resize and delete such a handle by using LabVIEW memory manager functions. So this makes only sense if the caller of such a DLL is LabVIEW too as another caller would have to go through several hoops and tricks in order to gain access to the correct LabVIEW kernel that could provide the memory manager functions to deal with such handles.
Last but not least output strings whose allocated length is not passed to the funciton as additional parameter are a huge secerity risk (talk about buffer overrun errors). LabVIEW DLL Builder does not support the creation of DLLs with output string (or array parameters) without the explicit passing of an additional parameter telling the DLL function how large the allocated size is (so that the DLL function can make sure to never write over the end of the buffer).
The additional length parameter only disappears for String Handles because LabVIEW will simply resize them to whatever length is necessary and that is also the reason why those handles need to be allocated by the same memory manager instance that is also going to execute the DLL function.
Resizing of memory pointers is non-standardized and in normal circumstances not suited for passed function parameters at all.
Rolf Kalbermatter
Message Edited by rolfk on 06-13-2008 12:28 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Building Dll for labVIEW RT gives errors

Hi All
Does building dll for labVIEW RT using CVI require labview runtime engine to be installed?
becuase i get some errors of unsatisfied referances to some library while building the dll with target selceted to "labVIEW real time only".
Regards
Arun

Hello Arun,
You don't need to have LabVIEW Run Time installed on your machine. Please check the link below to see the function that are supported by exporting the LabWindows/CVI LabVIEW RT Engine
http://digital.ni.com/public.nsf/websearch/D3EFE7C6F073384886256FDD005FBCDA?OpenDocument
Ame G.
National Instruments

How to use LabVIEW FPGA on Custom FPGA board other than NI products .....Also how to develop RTx DLL for a customised motion controller hardware

I'm using RTx, LabVIEW RT and LabVIEW FPGA.
The GUI is windows based. The motion control and FPGA are RTx based.
Is there any way to develop device drivers for the custom hardware in RTx. For example motion controller hardware, FPGA hardware, PCI hardware.
Is there a possibility to use custom FPGA boards to use with LabVIEW FPGA.
Please send me some links
Thanks
Bhoopathy
Take life as it comes! you may never know what's gonna happen Tommorrow

CODE WARRIOR Hello. I believe this question was answered in a previous post. Please let us know if you have any new questioins or if you need some clarification.
You are able to develop device drivers for your custom hardware using the NI Measurement Hardware Driver Development Kit.
However, it is not possible to use custom FPGA boards with LabVIEW FPGA. The FPGA boards have to be one of our R Series boards. Here are some links that should shed some light on the Measurement Hardware DDK.
Measurement Hardware Driver Development Kit Frequently Asked Questions
NI Measurement Hardware DDK (Driver Development Kit)
Please post if you have further questios.
Efosa O.
NIAE

Build a DLL in LabVIEW & Use the DLL in LabVIEW

I am trying to build a DLL for the simple vi with LabVIEW and want to use the DLL in LabVIEW. is it impossible?
I wrote a vi and it have 2 terminals. one is the input for numeric dbl data type and one another is the output for numeric dbl 1D array data type.
It was built with the Application builder for LabVIEW 8.0 and DLL was created successfully.
I want to use this DLL in new vi with LabVIEW.
Call library function used. I wrote a new vi to use that DLL.
In config dialog I config each parameter for dll and connected terminals. but it doesn't work
pleas refer to the attatched file and let me know what I missed.
Attachments:
Array1D.zip ‏60 KB

At first I kept scratching my head wondering why someone would want to do this. Create a DLL in LabVIEW to call it from LabVIEW. Seems redundant. But, perhaps it's an exercise or perhaps it's for testing the DLL...
In any event, calling the DLL worked for me in 8.2. How are you configuring your Call LIbrary Function node? I have it set up as follows:
return type: void
iteration: Numeric, Signed 32-bit Integer, pass by value
array1D2: array type, Signed 32-bit Integer, 1 dimension, "Array Data Pointer" format
len: Numeric, Signed 32-bit Integer, pass by value
Then I called the DLL like this:
Message Edited by smercurio_fc on 03-16-2007 12:57 PM
Attachments:
Example_BD.png ‏2 KB

How to build an .exe for cFieldPoint on a PC ?

Hi all,
A couple of weeks ago I installed a system with a compact FieldPoint running a in RT mode (cFP 2020 and LV 7.1.1).
To load the .exe on the cFP, I connected my PC to the cFP (ethernet), selected the cFP as execution target for LabVIEW and then opened the application builder. I assume this is the normal way to do... but is this the only way ?
In fact, my customer is asking for some more features, so my question is quite simple :
Can I build an .exe for the cFP on my PC (without connecting to the cFP target), mail it to the customer and tell him to replace the .exe file on the module ?
Thanks for any help
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Hi Kahlid ,
I noticed you were reply someone on pretty much close to same problem whatever i am having , I am working on LabVIEW8.2 with cFP. I created a project with an executable (run from My Computer), the other executable is running in the field point , I used shared variable to transfer data from field point to host program. Now I want to Uninstall LabVIEW from the same computer but want to keep MAX and one .exe file to run host VI. How to do that , any suggestion about copying or moving only .exe file ? or lets say if I want to run the same program in another new PC with same Field Point hardware and program how to copy/install executable in the new PC?
Thanks and best regards,
Faiyaz Syed

How to build a DLL that has Pascal calling conventions with application builder?

Hi,
I'm researching for possible solution to one of our problems.
In one case, solution would be to build a DLL from LabView
code. This should be simple task, but the application that
is going to load the DLL requires that the functions in the
library are exported using Pascal calling conventions,
similar to the C/C++ example code below.
DWORD APPEXPORT far APPPASCAL function(char hexr[])
Could this be possible with LabView somehow? Or is it best just
to write the DLL with C/C++?
Thanks.

Thanks Wiebe.
I don't know whether I need pass string pointers or not. The example
I posted was from the manual of the program that will be using the DLL
I build with LabView. I only wanted to show with it the exported calling
convention needed. It seems that it actually confused my question rather
than clearing it.
Anyway, now I know that it's possible to declare the calling convention
when building the DLL. And it's always good to know that I might encounter
different pointer types on the way, this may actually save me from a lot of
debugging some day.

How to build demo versions with Labview ?

Hello,
is it possible to design Labview applications in a kind,
that it is possible to generate "demo versions" of it ? Demo version in the means of feature-limited crippled versions of a full instrumentation software, where SOME hardware access is denied, but you can load and view and analyse data.
Of course it might be useful to compile this demo version with the Labview Application Builder,
What might be the business modell for demo versions:
A hardware manufacturer creates a Labview application which controls the manufacturer's components, and allows instrumentation and data recording. The application is not free but sold for extra money.
As pre-sales benifit, the manufacturer would like to send the (compiled) Labview application to future customers.
Now the problem is, that the customer has not (all) the external devices or PCI/USB devices,
on the other hand the hardware manufacturer does not want to give the "full application" as gilft to the customers.
Now with traditional software development with C++, Java, C#,
either a demo version is gained from the full version by replacing some module with hardware access by modules wth "empty" function body or with function body which return constant values instead of accessing the hardware.
In the world of process industry, usual process control systems may supply "alternative" values if the original device is not available.
What kind of software structure must I build with Labview, to do the same ?
Now the problem with Labview applications is
Labview applications depend on drivers. Drivers depend on hardware.
So if the FULL commercial version of the Labview program accesses a DAQmx driver, GPIB driver or any other hardware driver by a VI,
and often this means that a special manufacturer VI is used in the Labview program which does the actual hardware access,
how to modify the software to make a demo version
a) so that IF the customer buys the hardware and gets the hardware driver, he still does not have the full version
b) so if the customer neither has the hardware nor the driver, he still can run the Labview software and load an view data, push buttons, can execute menu items even can manipulate data ect, can use the manufacturer's VI
Unfortunately, it is no solution just to delete "some" of the VIs with hardware access from the distribution of the demo version, as this just causes error messages during the loading of the (compiled) Labview demo application.
Message Edited by hemmerling on 01-11-2007 12:35 AM
Message Edited by hemmerling on 01-11-2007 12:37 AM

Thanks alot.
Conditional Disable and Diagram Disable Structures
http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/cond_diagram_disable/
are indeed at least a part of what I wanted.
Anyhow, as such "suspended" VIs are often the *source* of signals,
so there must be an addtional method how to provide "alternative" signals for the demo version,
which does not make the administration / further development the full version too complicated...
For example: The VI for an external signal generator device is disabled, but alternatively it would be nice if the users of the demo version can get a fixed sinus signal instead...
How to do that with Labview and the "Conditional Disable and Diagram Disable Struktures",
and can I test this all even without Labview Application Builder, in the full development system ( so that I don´t need the compiler for frequent checking ) ?
Btw, with what version was this "Conditional Disable and Diagramm Disable" feature introduced ? Is ist already available with Labview 7.0, /.1 ?
Sincerely
Rolf

How to compile a dll for JNI in the CMD correctly

Now I find alot of old threads on using the mno command in cygwin to created dlls to use as an interface between c and Java, however I know this command is no longer available in cygwin and so I took the advid of downloading minGW and using this in the CMD instead.
However every example I try to compile and run this way throws the unsatified link error when the native function is to be called by the Java program. I believe it must be a compiling error creating a mismatch between the native function and the function to be called.
Here is the method I'm using to comile dlls for JNI, it is from the FAQ section of the minGw website:
gcc -Wall -D_JNI_IMPLEMENTATION_ -Wl,--kill-at
-Ic:/j2sdk1.4.1_02/include -Ic:/j2sdk1.4.1_02/include/win32
-shared someJavaImp.c -o JavaImp.dll
Is this how dll should be compiled? If not any suggestions?

sudsey wrote:
I know how to program well in C and Java, I just need to know the proper way to compile a dll for JNI.1. Get the MS IDE
2. Create a dll project - it must NOT be a managed dll
3. All done.

Call a dll for Labview: Function not found in library

Hello,
I am trying to call a very simple .dll form Labview. I compiled the .dll for x64 using Visual Studio 2010, because I am using Labview(64-bit). I did everything exactly the way I read it in several Tutorials. But the "Call Library Function Node" doesn't create a popup menu with the avalible functions like it is supposed to do. The Import Wizard doesn't find any functions neither. What is wrong with my .dll?
I added a block marked 'extern "C" ' into my source file, but it still won't work.
Thanks
Matthias
Solved!
Go to Solution.
Attachments:
DynamicLibrary.zip ‏2452 KB

You need to define an entry point to the DLL
BOOL APIENTRY DllMain( HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved )
return TRUE;
Also add extern "C" __declspec(dllexport) to your functions
More details here: http://www.ni.com/white-paper/3056/en
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

How to build ear files for ADF application using Ant task

How to build ear files for ADF applications using Ant. The ojdeploy ant task can not find application-level deployment profiles. I am trying to automated build and release for ADF application.
Any help is highly appreciated.
Thanks
Shiva

Hi Timo
Thanks for your reply.
I have successfully created ear file using ojdeploy on jenkins. however when am trying to auto deploy using WLDeploy ant task am getting the following
error :
weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/oracle/webcenter/quicklinks/scopedMD" mapped to metadata-store-usage "WebCenterFileMetadataStore" but its definition was not found in MDS configuration
Please advise how to handle this.
As am a newbie to ADF, could you please advise if it is possible for the ADF application deployments can be automated for different environments using jenkins due to this MDS dependencies.
Appreciate your help.
Thanks
Shiva

How to set different icons for different windows which is seen in the top left corner?

Hi
How to set different icons for different windows which is seen in the top left corner? I know when building exe there is a option to edit icons or add icons and that icon is default for all the windows in the project. But i want different icons for different windows which is possible in VB.
Is there any way to set icon by calling any dlls.
Thanks & Regards
Samuel J
[email protected]

Hi Sam,
no problem. See the attachment.
Mike
Attachments:
TestIcon_LV85.zip ‏44 KB

How to build a dll for labview pda, which uses the intel ipp primitives in it

Similar Messages

Maybe you are looking for