08-29-2011 03:43 PM
Oh, and also I've found this as a option : I connect path -> convert to string -> to DLL as CString.
08-30-2011 09:52 AM - edited 08-30-2011 09:53 AM
Ok - some news. I've tried possible solutions posted in this thread, but nothing worked. The situation is :
DLL function :
void LV_setVoltages(char fileName[],double vlt[]) { readDmc(fileName); //functions from linked DLL setVoltages(vlt); dmcFree(); };
I put probes in LV and it seems that LV is working ok - the arguments are passed as I wanted them to be. Then I debugged my code in VS. The fileName is ok, but the vlt array is wrong. There were two scenarios :
1. When I set the array in LV as follows vlt = [1,m,n,...,y], VS sees an addres -since it is a pointer with the value of 1. Logical since the pointer's value equals 1 as I recall.
2. When I set the array in LV as follows vlt = [0,m,n,...,x], VS sees an addres -since it is a pointer with the value of 0. That I can not explain.
m,n,y,x are random figures <-1,1>
My question is - does LV have any issues with FTDI drivers ? When I connect the device, LV crashes and hangs, when I run the VI without the device plugged in - it runs ok with the issues I wrote above.