Error 1097 when calling void **

[rolfk]

And what does this header file define? You may have made the wrapper worse than the function you wrapped if you are not very careful. Generally the way to create a wrapper is rather the other way around.

Study the API and the data you need to pass to the DLL, decide how to represent that in LabVIEW in the most easy way. Then create your VIs and place the Call Library Node by configuring the parameters and connecting all the LabVIEW terminals to it. Then right click on the Call Library Node and select "Create .c file". LabVIEW will create a C file that contains an empty function definition and any parameter datatypes as it needs them to be compatible. You can do this for multiple Call Library Nodes and copy the resulting C code from each .c file into a new C source file and start filling in the functions without modifying the function prototype or any of its parameter datatypes unless you know exactly what you are doing and stringently match every such change with an according modification to the relevant Call Library Node.

This way you can skip the Import Library Wizard which despite its name can't do magic, and importing DLL functions based on only a header file completely correct is simply magic. The C header file does NOT contain enough data to make such an import fully automatic. That is simply the nature of the C syntax, which was never designed to be a fully describing interface definition but only define the absolute minimum for a C compiler to create some hopefully working code (if the programmer was very careful and didn't make any errors).

Generally speaking if you write wrapper DLLs you do not want to create structures to pass to and from LabVIEW to the wrapper but simple skalar dataypes, and array and string pointers as parameter. Clusters/structures are a sure way to make your life more difficult unless you know exactly what you are doing.

[Wangky]

Thank you so much! I'll try it later. （＾ω＾）

[ganjbakhsh]

Hello,

Currently, I am actively engaged in a project involving the SensTech "xdas V3" board. As part of the process, I am working to extract decoded data from the board. In the documentation provided by the creator, reference was made to an XAPI Python class, although no pre-prepared version was included for use.

I am reaching out to inquire if you happen to have access to the XAPI Python class mentioned. Specifically, I am looking for version XAPI-2.0.20 or any updated versions. If you possess the class or have information on where I can obtain it, your assistance would be greatly appreciated.

Thank you in advance for your time and support.

[ganjbakhsh]

Hello,

I hope this message finds you well. Currently, I am actively engaged in a project involving the SensTech "xdas V3" board. As part of the process, I am working to extract decoded data from the board. In the documentation provided by the creator, reference was made to an XAPI Python class, although no pre-prepared version was included for use.

I am reaching out to inquire if you happen to have access to the XAPI Python class mentioned. Specifically, I am looking for version XAPI-2.0.20 or any updated versions. If you possess the class or have information on where I can obtain it, your assistance would be greatly appreciated.

Thank you in advance for your time and support.

[rolfk]

I have no experience with that XAPI interface at all and can't help you. And this is not a Python support board either. I recommend you to search on a Python dedicated forum if you can't get more information from the manufacturer of your hardware.