Hi everyone,
I contact ou because I have a problem with my experiment composed of: a laser providing an analogic signal, a connection bloc with the input from the laser on ACH0, then a cable to the NI-DAQ PCI card inside the computer, and finally LabView 8.02. First, I already developed many applications for LabView with other models of acquisition card nd that is the first time that I see the following problem. I developed a very simple program to make the acquisition of the analogic signal from the laser via the acquisition bloc. Here is a screenshot of the main part of the program:

The error I get is the following:
"La fonction DAQmx - Attendre la prochaine horloge d'échantillonnage a détecté qu'une ou plusieurs horloges d'échantillonnage ont été manquées depuis la dernière fois qu'elle a été appelée ; ceci signifie que l'horloge d'échantillonnage est trop rapide pour votre programme.
Pour corriger cette erreur, ralentissez l'horloge d'échantillonnage ou modifiez votre application pour qu'elle soit assez rapide pour l'horloge d'échantillonnage. Une autre solution consiste à définir la propriété Convertir les erreurs en mises en garde à Vrai puis à traiter la condition de mise en garde de manière appropriée.
Nom de tâche : _unnamedTask<2>"
Here is a rough translation in english:
"The DAQmx function - wait sampling clock detected that one or several sampling clocks have been missed since the last time it was called, this means that sampling clock is too fast for your program. To correct this mistake, slow down the sampling clock or modify your application to make it fast enough for the sampling clock. Another solution constits in define the property <<convert errors in warnings>> to <<true>> and then treat the warning condition in an appropriate manner.
Task Name: _unnamedTask<2>"
The questions are the following:
1) What is exactly a sampling clock?
2) This problem never occured before, than after several weeks, it occured from time to time randomly, and now it happens every time I launch the program ! Can the card be damaged? I precise that the program has recently been tried on two different computers, with a LabView version updated. Drivers are up to date too.
3) The fact that the problem occured from more and more often makes me think that my program, which is very basic, cannot be the cause. Is that correct from the screenshot I provided?
Thank you by advance for your help, and tell me how to do to replace the card if it's damaged and covered by the warranty.
Sincerely,
Julien