Hi Yan,
If you are using a driver that is different from your instrument, you are bound to come up with these sorts of problems. I would recommend digging down into the code and see if you can track down where the error is coming from. Since manufacturers tend to keep their API's similar, it may be a matter of changing a few small things to make it compatible. The specific commands that your instrument responds to can be found from it's manual.
I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/ and with the instrument manufacturer.
We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to tr
y developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://www.ni.com/devzone/idnet/development.htm
We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance
An instrument driver is a collection of functions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user.
Hope this helps out!
Best Regards,
Aaron K.
Application Engineer
National Instruments
