Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 200279... help!

Please help me someone... I am having trouble with error 200279. I know there are many discussion threads on this but these seem to contradict sometimes, and none of them have solved my problem.
 
I am especially confused as to the reason of the error because my program initially worked perfectly without displaying this error and could take the values I entered (namely sample rate = 10000 Hz and samples to read 1000), but then upon neatening the program by including sequence structures and subvi's, this error displays almost every time. This baffles me because I did not change the wiring of the read part at all, but added a subvi for the setup and spread the set up part and the looping part across two windows of a sequence structure.
 
I based the read part of my code on the LabVIEW example called "Cont Acq&Graph Voltage - Int Clk - Timed Loop.vi".
 
I have included my program despite it having many of my own subvis and sensor read setup vi which is relevant. I know that a simplified version would run fine so there is no point in sending it. I would gladly send coding if someone really wants me to send them all my subvis but my code uses many addons and a webcam as well so it could get a bit tricky!
 
Please could someone give me some pointers as to why this error is suddenly occurring! I am losing all hope!
 
Thank you very much, Rebecca Battye
Download All
0 Kudos
Message 1 of 2
(2,952 Views)

Hi there,

After what you have said I would say that the extra programming you have done since it all worked uses up CPU time and therefore slows down your computer.  The only way around this is to either refactor your code so that is works much quicker, or to increase the number of samples you read from the card each itteration.

Where abouts is the program throwing up this error?  Does the timed loop itterate a number of times or does it drop out on the first itteration.

Try placing itteration counters on the timed loops.  It may be that you start the input task and then wait 4 seconds before you read the first set of results. (You have a 4 second delay in the first sequence and there is no way of knowing at the moment which vi starts at what time.)  I would make sure that you wait 4 seconds and then run the setup vi just in case.

Hope this helps and if you have any more questions then by all means just post back.

 

Thanks

AdamB

Applications Engineering Team Leader | National Instruments | UK & Ireland
Message 2 of 2
(2,932 Views)