As it states in the LV RT User Manual - Appendix A (7.0) you might get more info on ni.com/info with info code RTDRVS.
What kind of instrument/io-/bus-cards are you using?
As I thought the VI calling the DLL would download the dll to the RT target automatically when run the VI. However, there are probably some restrictions (e.g. Call Library Nodes that access an operating system API other than Pharlap).
In the 7.0 release notes it is mentioned: When building a start-up application that uses shared libraries (DLLs) with the LabVIEW Application Builder, LabVIEW opens the DLLs Used by Application dialog box and lists the DLLs used by the application. Some DLLs might report the following error:
Target OS fails to load this DLL
Ignore the warning and click th
e OK button if you already transferred the DLL to the RT target. If you have not transferred the DLLs to the target, FTP the DLLs to the /ni-rt/system directory of the RT target.
Note as well:
Why Does My DLL Call Cause My LabVIEW Real-Time VI to Fail to Download?Let us know.
Roland
PS: These are links to start with.
Developing a LabVIEW Real-Time Driver for a PXI or Compact PCI DeviceConfiguring LabVIEW Real-Time and NI-VISA to Recognize a Third Party DeviceUsing VISA to Write Drivers Supported in LabVIEW Real-Time for Thi
rd Party PXI Cards.Programming for the LabVIEW Real-Time Module Using LabWindows/CVI