We are writing IVI drivers now, I wonder how can we get this test utility
(for IVI
driver testing for compliance with the spec) from your place.
chen ning
Easbeacon Test Systems Co.
"Dan Mondrik" wrote in message
news:506500000005000000B9270000-986697009000@quiq.com...
> I assume that what you are trying to do is to ensure that no VISA I/O
> calls get made when your driver has an invalid parameter. Using NI
> Spy will show you what calls are made, as you know.
>
> What you might want to do is to configure NI Spy to start up with
> capture enabled and have it log to a file; then you can visually
> inspect the log file later. However, take note that the log file will
> get huge quickly.
>
> Another option might be to manually disconnect the device
(eg, the MXI
> cable)after viOpen; this assumes that you are doing all your invalid
> parameter testing at one point in time but it may not work for all
> buses.
>
> If you are writing an IVI driver, we do have a test utility for IVI
> driver testing for compliance with the spec, and for some other
> structural tests.
>
> Dan Mondrik
> Senior Software Engineer, NI-VISA
> National Instruments