We have two identical test systems that have been using the NI DAQPad-6508 for some years now.
Recently both systems have started showing the same problem - the 6508 is becoming inaccessible via LabVIEW.
Closing LabVIEW, power cycling the 6508 and then re-running the application fixes the problem.
This then lasts anything from 10 minutes to a day or so before the problem reoccurs.
One of the systems is showing the problem much more than the other - some 80% more.
The system is running on XP with the following software:
| Name | Version | Description | Path |
|---|
| CVI Run-Time | 7.1.1.350 | CVI Run-Time engine | C:\WINDOWS\system32\CVIRTE.DLL |
| NI-DAQ | 7.4.1f4 | Data Acquisition Software | C:\Program Files\National Instruments\NI-DAQ |
| NI-DAQmx | 8.0.0f0 | NI-DAQmx Device Driver | C:\Program Files\National Instruments\NI-DAQ |
| NI-488.2 Software | 2.24 | Controller & Analyzer Software | C:\Program Files\National Instruments\NI-488.2 |
| LabVIEW | 8.0.1 | Graphical Programming for Measurement & Instrumentation | C:\Program Files\National Instruments\LabVIEW 8.0\labview.exe |
| Advanced Signal Processing Toolkit | 7.5.0 | Advanced Signal Processing Toolkit | C:\Program Files\National Instruments\LabVIEW 8.0 |
| Database Connectivity Toolset | 1.0.132 | Database Connectivity Toolset | C:\Program Files\National Instruments\LabVIEW 8.0 |
| Express VI Development Toolkit | 1.0 | Express VI Development Toolkit | C:\Program Files\National Instruments\LabVIEW 8.0 |
| Internet Toolkit | 6.0.0 | Internet Toolkit | C:\Program Files\National Instruments\LabVIEW 8.0 |
| PID Control Toolset | 6.0 | PID Control Toolset | C:\Program Files\National Instruments\LabVIEW 8.0 |
| Sound and Vibration Toolset | 4.0.49153 | Sound and Vibration Toolset | C:\Program Files\National Instruments\LabVIEW 8.0 |
| VIAnalyzer Toolkit | 1.1 | VIAnalyzer Toolkit | C:\Program Files\National Instruments\LabVIEW 8.0 |
| LabVIEW Run-Time | 6.1 | LabVIEW Run-Time Engine | C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\6.1 |
| Measurement & Automation Explorer | 4.0.0.3010 | Use Measurement & Automation Explorer to manage your National Instruments products and services | C:\Program Files\National Instruments\MAX\nimax.exe |
| NI-USI | 1.0.2 | NI Universal Storage Interface | C:\Program Files\National Instruments\Shared\USI |
| NI-PAL Software | 1.10.0f0 | NI-PAL Library for Windows | C:\WINDOWS\system32 |
| NI Spy | 2.3.0.49152 | Monitors National Instruments API calls | C:\Program Files\National Instruments\NI Spy\NISpy.exe |
| TestStand | 3.5 | Complete Test Executive Environment | C:\Program Files\National Instruments\TestStand 3.5\bin\seqedit.exe |
| NI-VISA | 3.4 | Virtual Instrument Software Architecture | C:\WINDOWS\system32\visa32.dll |
| visa32.dll | 3.4.0.49152 | VISA Library | C:\WINDOWS\system32\visa32.dll |
| NiVisaServer.exe | 3.4.0.49152 | Remote NI-VISA Server | C:\VXIPNP\WinNT\NIvisa\NiVisaServer.exe |
| NIvisaic.exe | 3.4.0.49152 | VISA Interactive Control Utility | C:\VXIPNP\WinNT\NIvisa\NIvisaic.exe |
| LabVIEW Run-Time | 7.0 | LabVIEW Run-Time Engine | C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\7.0 |
| LabVIEW Run-Time | 7.1 | LabVIEW Run-Time Engine | C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\7.1 |
| LabVIEW Run-Time | 8.0.1 | LabVIEW Run-Time Engine | C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\8.0 |
The device remains within device manager and MAX.
I have tried removing the driver and then letting it re-load after re-starting the PC - no luck.
Any ideas what may be causing this problem?
Your help would be appreciated.
Message Edited by AndyVessey on 12-03-2009 03:49 PM
