06-09-2023 04:38 AM
@Freddy. wrote:
So the only feasible solution currently may be to write another DLL to pass the structure……
That is your conclusion! 😁
I have on occasion gone the path of passing the entire structure into individual parameters through the Call Library Node (and add conditional compile to do the other thing for 64-bit) but yes it is painful and if there is anything else about the API that gets difficult to impossible to handle through the Call Library Node (callback pointers for instance) I always resolve to an additional intermediate shared library.
06-09-2023 06:54 AM
06-09-2023 07:18 AM
I split the elements in the cluster and imported them into the library function... Obviously, this is not correct. Labview still crashes, so how should I modify the cluster for this library function to function properly?
06-09-2023 10:11 AM - edited 06-09-2023 10:14 AM
@Freddy. wrote:
I split the elements in the cluster and imported them into the library function... Obviously, this is not correct. Labview still crashes, so how should I modify the cluster for this library function to function properly?
That is not what I was explaining to be necessary for structures being passed by value.
This is a start of what needs to be done. Sorry for not doing all the nitty gritty work. 😀
06-09-2023 01:28 PM
Could either of these toolkits be an alternative option?
https://www.vipm.io/package/imaginglab_gmbh_lib_yaskawa_robotics_library/
-AK2DM
06-09-2023 05:30 PM
Good morning, I immediately understood your code snippet! I have completed the remaining work. Well done, labview finally stopped crashing and I got the desired return code!
06-09-2023 08:07 PM