LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error Code -200294

I am getting Error Code -200294 back from a DAQmx Start Task.vi  The program runs fine when I am running in the Labview Environment but as soon as I run the .exe that I built with the application builder, I get this error on startup.  I'm using Labview 8.5.1  The explanation of the error "Not enough samples were written to satisfy the initial data transfer request condition." doesn't make sense (to me at least) since I shouldn't have generated any samples at the Start Task point.  Any ideas?
0 Kudos
Message 1 of 5
(3,532 Views)
Can you post your code?
 
I did a search on the error code and it yielded a description which didn't make much sense.  They proposed changing the order of the physical channels.  Do you have more than 1 physical channel setup?
 
R
0 Kudos
Message 2 of 5
(3,507 Views)
You could enable debugging when you build your application to see what is going on inside it too.
0 Kudos
Message 3 of 5
(3,503 Views)
I have eight channels set up for the analog input.  All are 0-20 mA inputs on the same NI 9203 module.  I have tried the debug mode for the .exe but so far have had even more perplexing results from that.  The code was executing in the loop after the error for the start task without any error indicated for a little while then the modal form with the error message came up and I was never able to clear it.  Clicking on the continue button had no effect.  Clicking on the X form close button indicated that I was clicking on it but the form never closed and I was never able to do anything to get back to the program except Ctrl-Alt-Del and stopping the program.  Of course this closed it and that was it.  I will try to work with this some more since I have never used the debug mode in an .exe before and know little about it.  There might be a better choice of options that I need to select to keep control of the process.
0 Kudos
Message 4 of 5
(3,493 Views)
I have fixed my problem and the program runs now!!  The solution doesn't seem to have a lot to do with the symptom though.  My application loaded a scalefactor file when it started up.  I used a check of the current path to the program and stripped it once to get the subdirectory and then appended the scale factor file name and loaded.  I had forgotten about needing to strip this path a second time when it became a *.exe  I had also forgotten to connect the error line from the load file vi so I was not aware that the scalefactors were not loading.  When this was corrected, everything worked fine.  Since I only use the scale factors to multiply the results of the DAQmx inputs, I have no idea why I got this particular error message.  I fully appreciate a host of other error messages that I might (should) have received but not this one.  In any event thanks for trying to help me.
0 Kudos
Message 5 of 5
(3,468 Views)