Jump to content

Search the Community

Showing results for tags 'dll'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

  1. DLL functions or shared variables? Or something else? I have a Labview 2014-64 executable (or I can build a DLL) that runs one piece of equipment, the X-ray. The other engineer has a large CVI Labwindows 2015 + MS Visual Studio 2012 (C++) executable that runs everything else. I want the Labview code to be a slave of the CVI code, accepting commands to turn X-ray On or Off, reporting failures, and the like. Translating the X-ray code into C++ would be possible in principle, but not fun. Shared variables look easy, but I'm kinda scared of them. I would define all the shared variab
  2. To use a controller from LabVIEW I have to use some functions of a DLL. For one of the functions, according to the header file .h there is a structure data with parameters of different types that I have to pass to the dll. Some of the parameres are BYTE (1 Byte) and WORD (2 Bytes). When compiling this kind of structure with Visual C++ and looking at it's size with "sizeof()" it seems to me that 4 Bytes variables have to start in a position multiple of 4. For example if there is a BYTE and then a DWORD, the 3 Bytes after the BYTE are ignored and the DWORD starts at Bytes 5 to 8.
  3. So I created a DLL from a Labview VI that has a 2D array input (and some scalar inputs) and some 2D array outputs. Labview creates a .h file with these lines And then it defines the 2D array arguments to my function as being of this type: "void __cdecl Linear_discrim_4dll(DoubleArray *dataObsFeat, int32_t grpAsz," etc etc. Trouble is, I have no idea how to fill out this structure so that the DLL can use it. Say for simplicity I had a 2 by 3 input called dataObsFeat with elements {1,2,3; 11,12,13}; how would I create the object with these values in C or C++ and pass it to the funct
  4. Hi When I call the DLL, there is a structure: struct Signal { uint32 nStartBit; uint32 nLen; double nFactor; double nOffset; double nMin; double nMax; double nValue; uint64 nRawValue; bool is_signed; char unit[11]; char strName[66]; char strComment[201]; }; There is another Message structure to the above Signal: struct Message { uint32 nSignalCount; uint32 nID; uint8 nExtend; uint32 nSize; Signal vSignals[513]; char strName[66]; char strComment[201]; } The point is Signal vSignals[513]; I've tried to solve it like
  5. Hello! I'd like to resize LStrHandle string in a C++ based DLL ... which is perfectly working on desktop Windows (ex.:Win7 32/64 bit) platform by include "extcode.h" and linking "labviewv.lib", with calling "NumericArrayResize" function. BUT I'd like to do the same on Windows Embedded Compact 7.0 with ARM(Cortex-A8). When I build the DLL project on "Smart device / WindowsCE" platform it compiled successfully but the linker stopped because "NumericArrayResize" is unresolved symbol ... I think the reason is that the "labviewv.lib" generated for x86 architecture not for ARM. So m
  6. The task is to process a bundle by a DLL embedded in LABVIEW. LABVIEW crashes even if the coded is most simple. For example, I created an array of double, bundled it and plugged it into the DLL. The parameters of the DLL are "Adapt to Type". The prototype in Labview is "void pointertest(void *source);" The C program: // dllmain.cpp : Defines the entry point for the DLL application. #include "stdafx.h" #include <stdio.h> #include <stdlib.h> #include "Header.h" extern "C" __declspec(dllexport)void pointertest(LVCluster *source); BOOL APIENTRY Dll
  7. Good morning, I have a DLL I created (in Labview) that takes in string information, does some magic crunching on it to create a password that is passed out as a string. This DLL will be called from CVI and probably from a C# application. This should be so simple, however I cannot figure out how to pass the string in and get the modified string out of my DLL. I've had no luck at all getting this DLL to work by trying many different things. It crashes LV, returns and error, or simply passes nothing out during my trials. I've included the project (its small) in zipped forma
  8. Hi I am developing a LabVIEW based vision system. Though the front-end is to be developed in C#. The processed images should be displayed on the front-end. Has anyone experience in how to convert, pass and display IMAQ images in C# Thanks
  9. I'm using a Labview Shared Library (DLL) to comunicate between a C# program (made by another company) and a labview Executeable (which means different processes) on the same PC. Currently i'm using network published shared variables, to communicate between the Labview DLL and the LABVIEW program (both made by me) which works well, except for the performance. Each time the DLL is called it needs to connect to the shared variable, which takes between 50 and 300 ms. When it is connected, the data transfer is instant. I have tried to use the PSP "Open Variable Connection In Background", which
  10. Hello, I am trying to figure out, if it is possible to create a native LabVIEW I/O interface to C/C++ code, that is using the I/O functions through callbacks. The scenario is as follows: I made a toolkit to process multimedia formats and (so far only) video codecs, it is using internally FFmpeg shared objects (DLLs or SOs, further just "DLLs"). They way the FFmpeg DLLs access I/O is through callback mechanism. Following all happens in the wrapper. If I want the toolkit to read data from some I/O like network or disk, I have to create a session, and part of the session are func
  11. I can't call the following dll function .... int sqlite3_open( const char *filename, /* Database filename (UTF-8) */ sqlite3 **ppDb /* OUT: SQLite db handle */);
  12. Hei, I am using Microsft Visual studio 2010 for the dll. I have created an image in labview which is then sent to the dll in order to extract the rgb values. I was hoping to get the arrays of red, blue and green with the data representation from 0-255 (U8). But instead, I got a weird problem on the linker. Sometimes it compiles okey, sometimes not. I was wondering that I'm doing something wrong with the image variables (color:purple), because you can handle it like array of pixels or like handles which are in the end structures. So, which method should I use? Till now I used it like array
  13. Hi, I am writing a LabVIEW API based on a 3rd party DLL. The DLL function I am working on right now returns a string and 2 U32. The string is only an output, but the 2 U32 are used as both inputs and outputs. So long story short the 3 parameters are defined as pointers. The 2 U32 work as specified in the documentation, one of them (psize) returning the number of characters that the string is supposed to return. However I can't get the string properly. The documentation tells me that it is a C String and I configured the parameter as such, but when I run the function I get only the firs
  14. Hi everyone. I wrote wrapper in Visual Studio for OpenCV calibrateCamera() function. Every operation like converting 1D array of points to vector<vector<Point2f>> etc, works ok, except most important thing. When function ()calibrateCamera is called, LabVIEW crashes. When this line is commented out, dll works ok (at least labview is still alive). Im out of ideas. I suspect that this is problem with memory management but i dont have an idea where it cames from. Function do not operate directly on data passed from LabVIEW. Ultimately I can compile code as exe and call it via cmd, b
  15. Hello, I write here a topic, because I'm looking for a help since I can not deal with some issue for a long time. I'm trying to write LabView program which will program uC flash using JTAG usbWiggler manufactured by Macraigor Systems. The manufacturer provides customers with program to do whole staff connected with programming, but it's stand alone app and I would like to build the programming process into the test sequence performed by LabView (program + test). Additionally the manufacturer provides a library to call various functions related to programming, erasing etc. I tried to write
  16. Hi, I am having trouble where Labview does not detect the required "edk.dll" file (as missing) eventhought it is in the same VI directory. Any help is appreciated attached are the images labviewsystemerror.png shows the error stated. labviewsystemerror2.png show the labview library explore (edk.all not detected) labviewsystemerror3.png show the edk.dll is in the same folder as the LabviewEmotiv.dll
  17. Hi everyone, I had linked a *.dll using 'Import Shared Library'. However, I encounter this error once it is done: Your generated files are installed in the following folder: C:Program FilesNational InstrumentsLabVIEW 2013user.libLabVIEW_Emotiv_emostate_EEG Parsing header file warnings: No errors/warnings occurred when parsing the header file. The following errors/warnings occurred when generating the wrapper VIs for this shared library. VI Not Executable The VI is not executable because of one of the following reasons: 1. The shared library or a dependent file is not installed. To
  18. Hi guys, I am struggling with test stand deployment for 3 days. hope somebody can help. ( I am using teststand 4.0 nd labview 8.5 and .net 2.0) I have sequence files, with many subVi' s and .net assmeblies with dependancies, added to workspace , and when i run the sequence file, it works fine. Specifically, the sequence file calls many Vi's, some of which use the .net assembly from "C:program filesNational instrumentslabview 8.5use.lib" ( and not specifically from the folder where the Vi resides), and still it works. However, when i build the same using deployment
  19. I'm trying to use a DLL which is developed by a third party. I created wrappers using Import Shared Library Wizard. When I call this function: int _Initialize(char *ipAddress, int *cameraCount); I get error 1097. I've checked the parameter setup, etc. I think it should be correct. Only one thing seems a bit weird.If you look at the prototype definition in CLFN-configure window, the function name is something totally different than selected. So, I'm wondering if this has anything to do with the actual problem? Header looks like this: #pragma once#include "PeakStructu
  20. I am developing a packed library that puts a LabVIEW wrapper on calling functions from a single DLL, and have noticed that, when building it, it does not grab the nested DLLs that are being called by the main DLL. Is this a known behavior? And can I set it to copy all dependencies into the builds folder? I know I can manually set it to include specific files, but seeing as the dependencies are listed within the DLL itself, I would imagine that LabVIEW would automatically dig through those files and find all the dependencies. I'm using Labview 2012, and the DLL is written in C#.
  21. Hi All! Since LabVIEW uses only Windows MME driver for sound in and out, I'm looking for an other way to get sound data into LabVIEW with much less latency. Has someone use ASIO4ALL for audio input? For sound out I use Midi via MME and the Windows own synthesizer. Its latency is really not high. But the input data comes with some hundred milliseconds lateness. With MME: I tested on 2 systems. About 350ms latency and not really depending of the system load. I tried also with small sample packages of 600 and 1200 byte/chn and a sound card acquisition rate of 96kS/s. In order to c
  22. Hello, I am trying to call a function from a dll with a pointer to a complex struct. I have tried multiple ways to represent the string in the struct (see attached typedefs), but the output clusters from the dll call always has the same values as input (i.e the dll isn't updating the output values). The ref ptr is based on an example from this link and I have attached a screenshot of my code for this case: https://decibel.ni.com/content/docs/DOC-9079 Here is how the vendor defines the struct: typedef struct { dword passkey; //password dword request; //0=readprop, 1=w
  23. First post LAVA, let's see how it goes... I'm propably missing something obvious here? I'm trying to call a DLL which takes a struct as a parameter. When I run the code, I get these two errors and LABView crashes. Any ideas?
  24. hi everyone here! recently i have come to a odd problem with lvrt(ets) and have no idea about how it goes. My project uses 10 or more dlls which were wrote by third party and had been put into the RT's C:ni-rtstartupdata folder, and this path had been added to the system find path list. Each of the dlls may have several VI calls(each for different functions in the dll) in the project. And when i try to deploy the whole project, my RT hung with one of it's cpu went to 100% loads. And the odd thing is, when i try to disable one of the dll (means to disable all the vis that call the
  25. I'm probably missing something fundamental about how variants are stored in memory . I want to create an array of pointers to variants. I seem to be able to write quite happily, but when read; it causes a problem. The following VI demonstrates what I am trying to do. It runs through once quite happily, but on the second execution it fails on the DSDisposePointer (even though the variant has been written and read correctly). If you disable the read, then it doesn't crash so it must be something to do with the way I'm retrieving the data. Any help appreciated. varpointers.vi
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.