Library function 8.6 VG in an example is not found

Similar Questions

• 'Library not found or failed to load' on the other system

  Hi all

  I searched a bit on the forum and found similar problems, but not really a solution. So I'll give a try with this post:

  I have two similar computers: Windows 7, 64-bit, Labview 2011 (service pack 1) is installed.

  And the goal is to acquire images of an acquisition card BitFlow.

  BitFlow software provided for the frame grabber, which has been tested for windows 7, 64-bit and Labview 2011. With a machine (machine A), the program works very well. No problem.

  On the other machine (machine B), Labview is unable to read the supplied library: after selecting the library in the library function node call, Labview gave the error 'Could not be found or failed to load library' on the node library function call.

  Machine b - in all my knowledge - the same configuration of all software compared to a machine, so I don't know what the problem is here. The only difference is that machine B has a different computer security protocol - but it has administrator rights...

  In addition, I tried a stand-alone executable file (and the installation program) who worked on a third computer, but not on the machine B - because of the same problem.

  Does anyone have an idea what direction am I looking for the solution? Or what may be the problem? Or what I'm missing here?

  Let me know if you need any additional info.

  Best regards

  Michael

  Haverdings wrote:
  "Library could not be found or failed to load." I guess this would mean a "failed to load" error (because the library is present), but I don't know that the 'fault' it is.

  Bitflow is installed by simply copying the files on your computer. No installer is required - even though they claim. Is there a way to check if the required version of the C runtime is used?

  Thanks for the replies

  Well, then the message could be more developed and make a difference file not found explicitly and not being not able to load, if LabVIEW would make some extra humba mumba woodoo, that's exactly what Windows shows a request when he tries to load a DLL. This code error, simply said, sorry, I could not load the DLL and that could be because it does not exist, but also because I couldn't load it for other reasons, such as the missing dependencies, (a corrupted OS or anything else). Not very useful to you, and I don't know LabVIEW must try to be smarter than Windows here, trying to see if the DLL actually existed. For all it's worth can be a text file or what is not a DLL, the DLL name!

  An interesting read that actually explains the problem a little more can be found here. You see that it isn't a problem of LabVIEW but just about anyones problem faced DLLs that can go just about anywhere.

  The best way to see what your DLL dependencies, is to charge with the program of the mentioned dependencies in this viewer. He has problems it is today on Windows 7 systems, but still can give you some useful information.

• How does the library function call Labview? Can I emulate using C++?

  Hi all. I recently finished writing a dll CUDA for LabView, and now I'm in the steps of optimization of code, memory management, etc. BUT since my code depends on the entries of Labview (lots of data under types of specific data as table manages and Clusters labview) I can't use the CUDA Profiler or the Profiler VC ++ on the DLL. What I intend to do runs labview and then out of all data entry for the DLL in a binary file and then add an additional function in my code that will read in the binary file, allocate and assign variables to their respective positions, and then call the specific DLL function in Labview. In the end, this miniature function will act as the library function call to my specific group of data entries.

  In any case, I started to make this purchase all my data entry of cluster and it comes out in a binary file. And then I started the initialization of the handles of labview, allocating memory and begins to write the binary data in the memory and it works for integers (ints), floats, etc., but I'm confused on how it works with table handles!

  Some examples of code:

  Sets the Handle for table 1 d for INT
  
  typedef struct {}
  
  	int length;
  
  	int val [1];
  
  		to access the value in a row-online val [Online]
  
  } Array1dInt, * Array1dIntHandle;
  
  int main()
  
  {
  
  	Array1dIntHandle x = new Array1dInt *;
  
  	(* x) = new Array1dInt;
  ifstream file ('TESTDATAIN.dat', ios: in | ios::binary);
  If (file.is_open ())
  
  	{
  
  		file ((char *) &(*x)-> length, sizeof;)
  
  		file ((char *) &(*x)-> val [0], sizeof (int) *(*x)-> length);
  LabviewSpecificFunction (x);
  
  		leader. Close();
  
  	} else
  
  	{
  
  		< "file="" did="" not="" open!"=""><>
  
  	}
  
  	return 0;
  
  }
  __declspec(dllexport) LabviewSpecificFunction (Array1dIntHandle x)
  
  {
  
  ...
  
  }

  However, my program crashes when the table is nominally big, and it is expected, because if we look at the Array1dHandle, it has allocated only enough memory to 1 item of value! YET, somehow, in its magical and mysterious labview is capable of making val [1] be val [HOWEVERMANYYOUWANT], even if C++ 101 says that val [1] is a constant pointer, and even if I dynamically allocated memory another somwhere, I would never be able to put these data in this round!

  Can you explain, or maybe even write example on how I can fool my program into thinking that the binary code comes from labview, so I can then run my program independent of allowing me to profile the functions inside labview?

  I hope that this question is clear and my sample code is also clear, but I'm happy to answer any questions that relate to this.

  Thank you all!

  I think that I thought about it.

  Array1dIntHandle x = new Array1dInt *;
  int tempsize;
  
  file ((char *) & tempsize, sizeof;)
  
  (* x) = (Array1dInt *) malloc (sizeof (int) + sizeof (int) * tempsize);
  
  (* x)-> length = tempsize;
  
  file ((char *) &(*x)-> val [0], sizeof (int) *(*x)-> length);

  Well enough, you will need to make the handle, and then make a new Array1dInt * for him, then read in the length of the array in a temporary variable. Then use this information to then malloc memoery quantity you need for the table and pass this place on the handle. Now the handle will point to the size of the memory and you will be able to access the memory in the format, you've done the handle. Badabing badaboom

• [HELP] Call library function node...

  I have a DLL that has a function as follows:

  int GetMessageNameNumber (char * messageName [], const int MessageNumber);
  

   

  The function is used thus:

  char * MessageName = NULL;
  
  int MessageNumber = 0;
  
  ...
  error = HL1553API_GetMessageNumberName (& MessageName, MessageNumber);
  

  MessageName will contain the name of the message as a string.

  I saw the Devils own job trying to wrap this in a Labview module.  I have a knot of library function to call the above function, but I'm not sure what to set the parameter "MessageName" also!  I tried array of integers 8 signed bits, adapted to the Type of pointer to data in the table and then passed in an array of strings.  Whatever I do translates into LabView crash.  I know HL1553API_GetMessageNumberName works, because if I call it directly in TestStand it works fine.  I need LabView well!

  Any ideas?

  C a pointer to a string or an array of strings are completely ambiguous.

  char * something = char * something [].

  You can't tell the two apart from the syntax, but only from the documentation or an example of how the function is called. A C compiler treats the equal in terms of access (but a C++ compiler will do a syntactic differentiation when code syntax checking, with the possible result compile warnings when you are prompted to use a sufficiently high level of warning).

  The example shows that it is not a string array gets allocated by the caller and passed to the function, but a string pointer that is passed by reference. So the function will allocate a pointer and return it (a very atypical C practice at least for strings). This automatically raises the question when and how this pointer will be released? The documentation for this function should document the call from Manager memory allows to allocate this pointer and also point to the function to call to release. Ideally the library (DLL) provides an exported function for this purpose.

  Assume that everything I spoke so far is clear and available you need to cheat a bit LabVIEW. You need to configer a pointer size whole that is passed by reference. Now this whole in the diagram IS actually your channel. If you only need to pass this pointer to other library functions call that you're already doing. Otherwise if you need access to the contents of this string from the diagram LabVIEW, you will need to copy the information from this string to a real string of LabVIEW pointer.

  One way to do that is to use the export of the MoveBlock() C function that LabVIEW exports itself. I have explained this several times here on this forum and the MoveBlock research will no doubt find out these positions.

  Another slightly better way is to use the LStrPrintf() function which also exports of LabVIEW. To do this, you configure a library function call as follows:

  Library name: LabVIEW

  Function name: LStrPrintf

  Calling Convention: C

  Thread: both are possible, but the function is thread safe, so just use environment

  return parameter: int32 (there is a possible LabVIEW Manager error code)

  1st parameter: handle string of LabVIEW, passed by value

  parameter 2: C string pointer

  3rd parameter: integer pointer size, passed by valu

  Wire an empty string in the first parameter constant.

  Wire a constant containing the text '%s' without the quotes on the 2nd.

  The pointer to your thread on the 3rd string

  The function will return 0 as a return value and the content of the string on the side of the exit of the 1st parameter or a zero value indicating that a mistake to return back.

• Make sure that wire you all the inputs and outputs of your node library function call?

  This document says "make sure that wire you all the inputs and outputs of your node library function call.

  http://digital.NI.com/public.nsf/WebSearch/7253D2F0D91F68058625752F005AB672?OpenDocument&submitted&&...

  But all the terminals on the right side of the call library node considered "outputs" referred to in the foregoing statement?

  This same document continues to show the right way to allocate memory with this illustration and in the illustration, the right "outputs" are left without junctions.

  

  Am I right in assuming that the only terminals that count as outputs, those who use the code of the DLL (modify) as output?  If it is true, then all other terminals output associated with the values entered alone so don't really account as outputs, correct?

  In the parameter call-library configuration screen there is a "Constant" check box and the help that he wrote "indicates whether the parameter is a constant."  What is this box? for me in the setup of the DLL call

  Finally, assuming that a call from the DLL that is supposed to write in these five outputs, is it legitimate to use constants like this to book a space of memory for the output values?

  

  How about if local variables associated with the output terminals are used instead?

  

  Despite the linked document, it is necessary to connect the corresponding entry for simple scalar output parameters (for example a digital). LabVIEW automatically allocate memory for them. If you do not want the entries for all the output wire anyway, there should not be no difference between a constant and a local variable; I would use a constant to avoid useless local variables.

  For settings that are only entries, there is not need to connect the outlet side. It's a bit simplistic since all parameters are entered only and get one result (other than the return value), you pass a memory address and modify the content to this address, but LabVIEW manages this dereferencing pointer for you. If you want to really get into the details, learn more about pointers in C.

  The "Constant" check box acts as the qualifier "const" on a c function parameter. It tells the compiler that the function you are calling will not change this setting. If you call a function prototype includes a const parameter, then you must mark this as a constant parameter when you configure the call library function node. Otherwise, I wouldn't worry on this subject.

• Return an array of strings of call library function node

  Hello

  I'm having a few problems getting the following work.

  I have a camera from a manufacturer that came with its own .dll and header files. I'm calling the LabVIEW .dll file (2011). In total, there are about 50 functions, and there is a rest that I can't go to work (probably because I understand enough about the topic to interface with an external code).

  The description of .dll is delivered with the following text:

  #define length

  #define MAX_CONFIGURATIONS

  Prototype: int ConfigListGet (char (& sConfigurations) [MAX_CONFIGURATIONS] [length]);

  and the header file with:

  extern "C" __declspec (dllexport) int RepRateConfigurationListGet (char (& sConfigurations) [MAX_CONFIGURATIONS] [length]);

  The function should return an array of strings to the list of configurations.

  The problem I have is that I can not understand how to return the array of strings for the node of the library function call to LabVIEW. I looked a little on the web and the examples in LabVIEW and I can't find anything specific to return an array of strings in this way, so if anyone can point me in the right direction I would really appreciate it.

  Also, if I click with the right button on the node library function call and click on "File Create.c", I would be able to create the prototype of function even that above? I tried this but no luck. Was the closest I came:

  int32_t RepRateConfigurationListGet (char sConfigurations [], uint8_t MAX_CONFIGURATIONS, uint8_t MAX_LEN);

  Thank you very much in advance for any help!

  D

  Hello!

  I tried once using an array of U8, converting it to a string and then split into an array.

  Here is my old piece of code (the split part can be cleaner ;=))

  Kind regards

  Marco

  

• help with call library function node

  I have problem with node function call library that I try to use velleman k8061 dll file to get this working labview

  all I'm trying to get the same problem

  but I chose one to explain it

  SetDigitalChannel
  Syntax
  PROCEDURE SetDigitalChannel (CardAddress: Longint;) Channel: Longint);
  Parameters
  CardAddress: The address of the previously opened card.
  Channel: Value between 1 and 8, which corresponds to the output channel to be resolved.
  Description
  The selected digital output channel is activated.
  Example of
  BEGIN
  SetDigitalChannel (0, 1);

  now, when I try to call the function of library in k8061.dll node and set up 2 a card address and one for the channel

  address of card type: type numeric & statistics: signed 32 bit intger

  channel type: numeric type & data: signed 32 bit intger

  function prototype

  void setdigitalchannel (int32_t, intg32_t channel address);

  I also configure error call library function node checking up

  now that I run it, I get error 1517 produced and tell me this mismatch between the calling conventions?

  problem solved

  thanx

• import the shared library function name change

  Hello

  I used 'Import Shared Library' to create a lvlib, but he changed function name, for example to Z2onj() on(), so created VI does not work.

  It has this error:

  Call library function node "libname.": Z2onj: function not found in the library

  Details:

  The name of the function specified for this node is not found in the library. Click the node to call a library function and select Configure, and then choose the name to function properly.

  How can I solve?

  Thank you.

  Hi Salvo,

  you need to create again the lvlib with the new name.

  Kind regards.

• Loading of the DLL string using the Code Library function node

  I experience now with the element of Code Library function node... what I wanted to do are, for example, I have compiled a. DLL file... which has a function that returns the pointer to string... function looks like:

  / * This function returns a pointer to the character string * /.

  char * pchar (int n)

  {

  char * str [] = {"error", "String1" and "Word2", "3"};

  Return ((n! = 1) & (n! = 2) & (n! = 3))? Str [0]: str [n];

  }

  but when I load into LabView DLL, a part of the chain on the screens to Panel frontal trash... any ideas why?

  p.s. when I do even with integer values... say my job is like int x = 5; Return x; and then I load in LabView to the digital indicator... it works great!

  So any ideas?

  thanx

  Cyrax says:

  I experience now with the element of Code Library function node... what I wanted to do are, for example, I have compiled a. DLL file... which has a function that returns the pointer to string... function looks like:

  / * This function returns a pointer to the character string * /.

  char * pchar (int n)

  {

  char * str [] = {"error", "String1" and "Word2", "3"};

  Return ((n! = 1) & (n! = 2) & (n! = 3))? Str [0]: str [n];

  }

  but when I load into LabView DLL, a part of the chain on the screens to Panel frontal trash... any ideas why?

  p.s. when I do even with integer values... say my job is like int x = 5; Return x; and then I load in LabView to the digital indicator... it works great!

  So any ideas?

  thanx

  You cannot return a pointer to the data stored on the stack. At the time when the function returns, the stack is reset to the State before the call to the function and in a multithreaded as LabVIEW environment probably long reused for other things when LabVIEW gets around to actually copy the returned pointer data.

  Since it is a read-only variable, you could create a permanent memory for string storage by declaring your variable static. This will create a memory area allocated globally for the string data (and also cause a compile error when you try to write in this area somewhere in your code, which is a good thing).

• call library function node to paste files

  Hello, I use the call library function node to paste the text to and from the Clipboard and works well.  Now, I'm trying to figure out how to paste a file from the windows file Explorer.  So if I highlights a file in the Windows File Explorer and press Ctrl-C, how can I use the library function node spit a file path?  It would be even better if I could highlight a bunch of files and then paste a table of paths, but that can wait.  Also, I use a Listbox MC, so I can't use drag-and - event trigger move a control path of the file.

  Also, I use WinXP and LV 7.1.

  Thank you

  Pat

  UPDATE

  I had little time to play with it and really out of curiosity on my part that I have whipped up a simple example to drag and drop from the Explorer in LabVIEW. I wrote the code in 7.1, but I have 7.1 on a virtual machine, and the DragQueryFiles did not work. I don't know if it was due to the fact that I was running on a virtual machine. I did, however, run the code in 8.2 and it works correctly. 8.2, I was able to drag a bunch of files in front of the VI, and the string table fills with file names. I am especially to see if it might work for you. You will need to get the Windows Message Queue library. Simply place the library in the same folder where you unzip the attached file.

• Disable the use of structure in a lead time library function node increases

  I found that if I use a stureture disable to disable one of the outputs of a library function node call, the run time will be greatly increased. Can someone explain this?

  

  You can read this thread and benchmarking, I did there.

  Turn off debugging and check if the loss of performance you MENTION (but not quantified) is still there.

• Call library function node

  When using a call library function node, and the program came out, I get an error "has encountered a problem and needs to close" having to do with ntdll.  It does not stop the program from running properly, but it's annoying.  Any ideas?

  You should NOT specify the full path to a DLL system in the configuration dial the node of the library. This mess something in the newer versions of Windows. Instead just enter the name of the DLL only. It is sort of a bug in LabVIEW not automatically detect the system paths and shorten the path accordingly in itself, but this is how things have been for a long time and you just need to be a little careful.

  Also the return value must be really set up to be an integer of size of pointer, since a HANDFUL is really a pointer under Windows and that the first parameter is also better configured as such. The way you did works very well for LabVIEW 32 Bit but will misbehave in LabVIEW 64 Bit.

• What is the right way to specify the location of the shared library in an a .lvlib function call library function node?

  I'll have a bit of a problem with how to specify the location of library shared in a call library function node it is a VI that is part of a library of LV. Here's a little background which may help.

  I do a lot of measures using spectrometers photo from several manufacturers.  Someone in my company developed a C DLL library, which provides a simple API for all the different spectrometers. To facilitate this DLL to use in LabVIEW, I wrote a .lvlib that wraps all the functions.  When I want to use the API, I simply include the .lvlib file in my project that allows me to drag and drop the wrapper s VI on my block diagram. When I created the .lvlib of VI, I specified the path in the call library node. /. * so it will always look in the local application to the DLL directory when I run.

  The problem is, when I load demand, LabVIEW you asks for the location of the DLL even if it's just there in the local directory! I tried to put copies of the DLL in the directory with the .lvlib, but he still refuses to find the DLL loading.  What I am doing wrong?

  You should in this simple case enter the full path to the DLL by navigating to it. If the DLL is on the same volume/drive that the VI containing the call library node LabVIEW will be internally store the relative path from the VI to the DLL (but still show the absolute path). If you move the DLL and screw together (so the relative location of the DLL to the VI remains the same) LabVIEW will always find the DLL.

  I don't think that the lvlib would add nothing to that.

• When I use the library function node call in real time, is loaded only once for all or load the DLL whenever it is called?

  When I use the library function node call in real time, is loaded only once for all or load the DLL every time when it is called?

  I have a critical application in real time, in which I use a piece of DLL function developed in C++.  It is ok?  Make sure any senior developer?

  Thank you in advance.

  The user interface thread is the thread that is used to update the user interface. It's slow. And it's supposed to be that way because humans are slow.

  The call library function node can be configured as this thread to use in the configuration for it dialog box. Please visit the LabVIEW documentation on how to do this.

• Node function of library under Linux - features not found

  Hello

  I am developing a VI in LabView 7.1 2.6 Linux (Fedora Core 6) that needs to call a library function that I have developed. I believe that there are no errors in the code in the library or in the way the VI went, but LabView or can not use this library. Whenever I open my VI, he asks me to locate my library and when I point the LabView library, it all just cannot open it will ask me where is the library. If I chose to ignore it and continue loading the VI, once I double-click on my node library function and point LabView library error I get 'Can't load/search library' changes to "Library does not have the requested function". I coded the entire library in C and it built as follows:

  GCC-fpic shared - c EncoderLib.c

  LD g o libencoder.so EncoderLib.o - lphidget21

  Here, the - lphidget21 option is to post a link to a library I develop a wrapper of LabView for. This isn't the EXACT method mentioned in "Chapter 6: using external Code in LabView", but it is still close enough. I failed to get my library to compile in a statement. I'm unable to locate the document I'm referring to this time, but I think I got it somewhere on the Web site of NOR. In any case-maybe I'm linking or building this library incorrectly? I checked to make sure that the library contains indeed the function I am trying to call from LabView using "nm" Linux command line function. The result is as expected:
  $ nm libencoder.so
  TRUNCATED IN ORDER TO SEE THE PART IMPORTANT *.
  00000614 T NumEncodersAttached
  0000053 did PollPosition
  0000059b T PollRotations
  000004e8 T SelectAxis
  000005c 6 T SetPosition

  The listed functions are functions that I try to call, so they are definitiely in the library and even for some reson LabView can not find them! I was just tickled pink, if anyone has any ideas on how to solve this problem. If anyone has compiled and used a Linux library function node before, I'd love to hear about your experience and if you have had problems. Someone has to meet this problem before?  Any help is greatly appreciated. Please let me know if I can offer more information.

  Thank you all!

  -Andy

  Hey Charlie,

  Linux is not any sort of error handling capabilities. Thanks for the good suggestion, if. I finally understand it. LabView was very, very unhappy with the function toUpper, despite the fact that he lives in the standard library of C I pulled out the function and the library worked like a charm. I don't know if this is a mistake made by my (standard gcc for linux) compiler or if it is an error in LabView, but anyway it's probably something that users should know. Hope this helps someone in the future.

  Thanks for all the assistance, Charlie,

  -Andy