08-11-2005 11:17 AM
08-11-2005 11:40 AM

08-11-2005 11:56 AM
Hi Celgi,
Are you saying:
Inside your DLL, you call a function with some formal parameter(s), and, one (or more) of those parameters is a pointer(?)
Or, are you saying that one (or more) of those parameters are pointer Variables (pointers to pointers)?
Perhaps a simple prototype (of function) would help illuminate - though, I've no idea where this is going. 🙂
Regards
08-11-2005 11:58 AM
Thanks for your answer.
In fact, the pointer used only in the DLL's function. LabVIEW 7.1 call one DLL's function "Point" with an entry "Mesure IN" and two exit "Error code" and "Mesure OUT".
This function call an other function "wait_point" with a pointer on "Mesure": the value "Mesure IN" is used to find its new value. This new value becomes "Mesure OUT". The function "wait_point" return an error code too.
LabVIEW stop when the function "wait_point" try to modify ou read the value of the pointer.
08-11-2005 12:22 PM
08-11-2005 12:54 PM
Thanks Dynamik and LV_Pro.
I don't really understand the last answer but I'll search if I changed the address of a parameter in my DLL. Thanks ![]()
08-11-2005 02:54 PM
Hi Celgi,
Do you use "Call Library Function" to interface with your DLL?
Here's a pic re: "PASS" and "Data Type" (hope it helps)
08-11-2005 04:12 PM
08-11-2005 07:17 PM
HOLY S**t - I mean, Sacre Blue!
This JPG makes me want to work on problems of my own.
Re: Cluster Transfer - Yes, perhaps it's a data-type SIZE or Cluster-order issue - so many type-defs!
I would print-out the .h files for the C structs, and compare them, element by element, byte for byte, with the LabVIEW Clusters. And, make sure the LabVIEW CLUSTER-ORDER matches the Struct!
Of course, you truely might have some strange pointer problem...
Bon Chance!
08-12-2005 12:56 AM