interface error 10459

[B2]

I'm rerunning old program in Visual Basic to do DAQ through PCI6115. I know it works 3 month ago but at this time it cannot configure due to an interface error. Following is an error message.

Runtime error '10459'
Configuration channels
The NI-DAQ DLL could not be called due to an interface error.

In MAX(Measurement and Automation Explore) I can read data in test fanel. Would you let me soon what I should do? Thanks.

[bilalD]

Hello

I have seen a problem that occurs sometimes where having MAX and VB open at the same time causes a problem like this. If you go to the property pages from your device, in the Channels tab, when you go the drop down list to chose the list of devices installed on your system you will notice they will be empty.

Try closing MAX and VB and open up VB and try again. Check to see if your device shows up in the drop down list. Thats how the problem usually goes away for me. Worst case, I just reboot.

I hope this helps

Bilal Durrani
NI

[DVAZNA]

I get the same error as described in inital post, but the reply does not fix it for me.

I am using DAQPad-6020E (BNC) and PCI-6503 with VB6 SP6

I am trying to use the 6020 as Traditional NI-Daq and the 6503 as DAQmx. We have legacy code for the 6020 which would be a hastle to change, and I wrote some nice code for the 6503 which I don't want to revert to traditional, so I have both drivers working at the same time. This works fine on other PCs.

My problem is that only one or the other will function at once in my VB6 program. By default, the DAQmx will work fine but when I try to configure the Traditional it gives me the exact message in the original post. I can fix this error by stopping the service called National Instruments Citadel (or stopping the process called nimxs.exe or something like that, won't come back until I reboot). If I do this, the device will show up in the CWAI object in VB, but my custom VB control which has the DAQmx libraries inside it will not work. If I start up Citadel again, the DAQmx driver will work, and we are back to square one with the Traditional (not working and not displaying DEV1 in the property pages of the CWAI).

I have had this problem or one like it on the other PCs (with almost exactly the same hardware and software setup) but I don't remember how NI helped me to get it working. If anyone has any ideas, all the help I can get would be greatly appreciated. Thank you.

Dan