01-12-2007 09:05 AM
I must be missing some concept or something (or I'm just dense...) This is the problem:
1. I installed NiDAQ 7.4 on a clean system. The software using the CWDAQ 6 ActiveX control works fine, it reports 12 channels (I'm using PC-DIO-96). I do not use any configuration files in the Measurement & Automation Explorer, I just installed and it works.
2. I then installed NiDAQ 8.3 on the same system. The software using the NiDAQmx dll works fine. Any software that uses the CWDAQ 6 Active X control reports there are 0 ports available on the card and fails.
3. The Measurement & Automation Explorer shows both a NiDAQmx device and a Traditional device. Both sets of test panels work. Again, I do not use any configuration files in the Measurement & Automation Explorer, I just installed and it works.
I do not need to convert NiDAQ Traditional to NiDAQmx because the NiDAQmx works fine. What I need to know is if it is possible to have 1 program use the CWDAQ ActiveX control to access the card, then quit that software and run some other software that uses NiDAQmx and have it access the same card? I don't see any functions to assign ports to the legacy card, I can't delete the NiDAQmx device, and I'm not using any config files.
Thanks for your patience
Matt
01-12-2007 09:55 AM
01-12-2007 10:05 AM
01-12-2007 10:50 AM
01-15-2007 09:01 AM
Thanks for your tremendous patience. Unfortunately, resetting the device didn't change anything. I reset then ran the demo digital input app, no ports. I reset then rebooted, still no ports. FYI, I am making sure the device number in the CWDAQ control is 1.
I'm not sure how to call Init_DA_Brds (VB says its an undefined function even if I add the NiDAQmx reference), but doubt it would help anyway since it should already have been called when the control was loaded.
Thanks again
Matt
01-15-2007 10:58 AM
01-19-2007 08:52 AM
Ding, ding ding! We have a winner! The first command in that kb article solved the problem. Now all 12 ports show up in the CWDAQ object. Just for posterity: it was a clean install of W2K with all current patches, VB6 sp 6a, nidaq mx 8.3, nidaq traditional 7.4.
Thanks to everyone for helping to solve the problem!
Matt