Jump to content
News about the LabVIEW Wiki! Read more... ×

hippo Th

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0

About hippo Th

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2017

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. hippo Th

    implementation of driver files (.dll) - How???

    Wow, that's a huge amount of input. :-) Thanks to all. So how to build up a single CLFN is partly clear. With wizard import of the function from .dll with .h-files, I still strugling. The wizard in LV partly recognized some functions from the .h-file, but not all (see picture). It depends which .h-file I choose. At the end, no fuction was usable. I allready tried to include in an .h-file the command #include "fileX",... . But with no sucess --> LV crashed. In the docu is explicit written that you can develop your own driver. So it should work. I suppose, it probably will be written indirectly in the docu - maybe via the examples. Logical thinking. --> try & error. When it makes sense to work with callback function? Only, when I need this optional part of function? As I understand you all correct. The .lib-file is importand for the .dll. Is there a way to work with the .lib file in LV - 3third party software? (attached) The .lib-file can be loaded on two ways: (1) By calling LoadLibrary()/GetProcAddrss() or (2) by linking the import library. But both ways are senseless for LV. The full/complete .h-file is nice for me as LV developer. But not necessary, when I have the docu with the description of function for the .dll. With the .h-file and the wizard, I can simple generate all functions automatically at once. With the docu I have to programm every function node according the description on my own. cifX32DLL.lib
  2. hippo Th

    implementation of driver files (.dll) - How???

    Hi Shaun, What does CLFN stand for? I know, that this is/was wrong. But, I do not see any other possibilty in LV. Therefor my upper questions. Where and in which form I get the Handle parameter? Thanks. I am partly aware of this. 😕 But first, I want to "run" a single function - and then I would go further. Step by Step I was already looking for a header file and also a library file. But nothing fit so far. With the .lib-file I orientated myselfe here: Will I usually get this header or .lib file from the manufactor or is it secret? Alternativ, the manufactor offers their own software with a huge software package (about 900MB). But I don't know, how to implement their own software to my test bench with LabVIEW. Attached I added all .h and .lib - files from their software package. .h_and_.lib-files.zip
  3. Hello togehter, ich want to implement my first driver file (.dll) in Labview. As hardware for the driver file, I use the card "cifx 50e-dp" from the company Hiltscher. Attached is the documentation with a screenshot, the driver (win10 & 32bit) and an example-VI with my example function "xChannellORead" with the driver file. I hope, that in the documentation are all necessary information. :-/ Unforteunatly is it not working how it should be. How must the VI be configurated? How are the correct settings/arguments in the Call Library Function? see --> configuration --> parameters Until now, my VI is not executable. Which name(s)? Which type(s)? Which data type(s)? .... Which calling convention? Try & error, if LabView crash? Are the names/arguments inlet or outlets? How can I reconize it? I would be happy about every note/impuls/advise. Best regards Thomas test.vi cifX API PR 04 EN.pdf cifX32DLL.dll
  4. hippo Th

    OOP - change status of VI in OOP

    Thank you very much :-)
  5. Hello, attached/below are two connected VI's. 1. What does the symbol mean in the red square? 2. How can I change the status on the second VI to the first one? In my opinion the both VI's should be the same one - except in one detail. But I don't know these detail. :-( Thomas
×

Important Information

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