12-30-2005 09:49 PM
12-31-2005 04:16 AM
This thread contains already a related answer and explains what a sys driver is. While you could theoretically use the Call Library Node to call all the necessary Win32 API kernel functions to connect to a device driver, this would be very cumbersome and not doable without a real good understanding about C programming. Writing an interface DLL instead won't need more C programming knowledge at all but will give you a clean interface to that device driver which eventually could be used in other programming environments as well.
逍遥浪子 wrote:I have some question about USB communication: I want to make my VI communicateTI-DSP by USB, now, the driver of USB on DSP have done, and there are a testprogram writen by VC and a driver fold(with a .inf and a .sys files), when Iinstall the driver and run the test program, the driver program on DSP runregularly. And then I want to program a VI which have the same function as thetest program, so I unload the driver on PC firstly, then install the DSP inNI_VISA according to "Using NI-VISA 3_0 to Control Your USB Device - Tutorial -Instrument Drivers". When I sent the standard control request using the VISA test panel, the status below happened. I don't know what wrong with my step.Dev Phase Data Info Time Cmd.Phase.Ofs --- ----- ------------------------- ------------- ----- ------------------ 15 CTL 80 06 03 00 - 00 00 04 00 GET DESCRIPTR 5.2sc 56.1.0 14 CTL 80 06 03 00 - 00 00 04 00 GET DESCRIPTR 11us 57.1.0 14 USTS 00 00 01 c0 canceled 2.0sc 57.2.0 15 USTS 00 00 01 c0 canceled 5us 56.2.0 PS: the software I use to capture the data is BUSHOUND1、Do I have to install the .sys driver file in VISA? How can I install the driver file without losing the device in MAX?2、 Someone told me it must be done by calling .dll fies in LV, but I want to know if LV can program the function directly without calling .dll file?