Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

No NIDAQmx 7.3 support for PCI6602 in LabVIEW 7.1?

Hello.
I have installed LabVIEW 7.1 Full Development System (German Version), NIDAQ 7.3 (including Traditional NIDAQ and NIDAQmx) and a PCI6602 Counter/TimerBoard. The Operating System is WindowsXP with SP2. When I open the Measurement & Automation Explorer and expand "Devices and Interfaces", the PCI6602 is listed under "Traditional NIDAQ Devices", but does not appear under "NIDAQmx Devices", although both drivers are installed. This is confirmed in "Control Panel>>Software" where all NI components are listed. These are the following:

LabVIEW 7.1 (Deutsch)
LabVIEW Run-Time Engine 7.0
LabVIEW Run-Time Engine 7.1
Measurement & Automation Explorer 3.1
NI-DAQ 7.3, Traditional
NI-DAQmx 7.3

Also, the PCI6602 is l
isted in the "Device Manager" and confirmed to work properly.
But starting the DAQ Assistant in LabVIEW, choosing "Counter Input" and "Period" displays the message that no supported devices could be found.

Why is the PCI6602 not listed in the MAX under "NIDAQmx Devices" and why can't the PCI6602 be detected by the DAQ Assistant?

Thanks for help!
0 Kudos
Message 1 of 4
(3,612 Views)
Hello,
the PCI 6602 is supported by DAQmx since 7.2. Maybe the Service Pack 2 is responsible for this behavior.Because of the Firefall a lot people have problems with there Hardware. Check the configuration of the Firewall.
0 Kudos
Message 2 of 4
(3,611 Views)
Hello.
The firewall is not active.
I had installed LabVIEW 7 Express and uninstalled this evaluation version before I installed LabVIEW 7.1 Full Development System. Could it be that my problems result from conflicts between these different LabVIEW versions? Maybe there are registry entries left...

Now I installed all components under WindowsXP SP1 and the PCI6602 is detected properly. I'd like to know whether the problems are caused by SP2, software conflicts between the LabVIEW versions or anything else.
Thanks!
0 Kudos
Message 3 of 4
(3,611 Views)
I think SP2 is responsible. We now about a lot of problems concerning SP2, so I recommend you to use just SP1
0 Kudos
Message 4 of 4
(3,611 Views)