What DLL are you calling? Is this DLL something that you wrote? What programming environment did you make the DLL? Are you getting an error when you download a VI with this DLL? What is happening?
In general, a DLL will work in RT if that DLL does not make any unsupported Windows API calls. If you have CVI you can develop a DLL using the build option to make it compatible for RT. This will inform you if you are making any unsupported calls.
My interest is in building a stand-alone application or an exe file. The DLL was generated using Visual C++. It works alright off-line. I just want to build an exe with the DLL included so I can run it on the CVS or any other platform. Do I need to copy the DLL to the CVS? What if the platform does not have sufficient storage media?
"jdigiova" wrote in message news:5065000000050000000F8A0100-1079395200000@exchange.ni.com... > What DLL are you calling? Is this DLL something that you wrote? What > programming environment did you make the DLL? Are you getting an > error when you download a VI with this DLL? What is happening? > > In general, a DLL will work in RT if that DLL does not make any > unsupported Windows API calls. If you have CVI you can develop a DLL > using the build option to make it compatible for RT. This will inform > you if you are making any unsupported calls. > > Joe D. > National Instruments
I assume you do not need to register this DLL and you are specifying it by path from your Call Library Node. You can ftp this DLL to the CVS and put it into the directory that is referenced by the path in your Call Library Node. Or you can include the dll as a support file when you are building your executable. This will put the DLL in the LabVIEW Data folder. Your path in the Call Library Node should point to this folder.
One very important note is that the DLL cannot have any calls to unsupported WinAPI functions. So even if you are able to call the DLL it may not run in a Real-Time environment.
