LabVIEW
Calling Advantech shared library SUSI4 on a single board computer. Help please!
Solved!
I would actually prefer to use the import shared library wizard so it will wrap all of the functions but I get this.
Hi Andrew,
With regards to simply using the call library function node, there is a tutorial on the community page that gives you step-by-step instructions on how to use it for calling simple DLLs. This can be found here:
However, it seems you want to use the Import Shared Library Wizard (ISLW) instead to call the DLL. As the errors you generated show, some of the definitions are missing in the header file (I'm assuming Susi4.h is the one you are adding to the ISLW). This is because of the two header files you have, OsDeclarations.h and Susi4.h. In order to get past the functions missing issue you are facing, in the previous window there would be a section to add preprocessor definitions:
Since the definitions required are in the OsDeclarations.h file you would have to add the following in the Preprocessor Definitions:
int8_t = char; int16_t = short; int32_t = int; uint8_t = unsigned char; uint32_t = unsigned int; uint16_t = unsigned short
That should allow you to then use the functions.
Kind Regards,
Jeneni
But beware! The wizard can't do magic despite its name. The C header file is notoriously inadequate to capture all aspects of calling a function. And the DLL itself contains no information at all other than the function name, that the wizard can use. The header file provides the bare minimum for a C compiler to create the necessary machine code to call a function but relies heavily on the programmer to know HOW the function needs to be called. Most of this knowledge has to be gained from reading the documentation of the function, looking at sample code that uses the function and often simply trial and error, not until it doesn't crash anymore, but until it works truly correct under heavy test conditions.
The Import Library Wizard is not a programmer but simply a program, which can not know all these things, so a real programmer understanding both the C programming specifics as well as the way the particular function needs to be called has to validate each and every function after the Import Library Wizard did its work. Just running the Import Library Wizard and hoping everything is fine, is like creating a time bomb that will likely go off at the most painful moment in your project.
