Error Code 100 <not a path> for Write to measurement file

[sharmishtha]

Hi

I am getting error code 100 <not a path> from my write to measurement file, in the slave loop of my VI. I have no clue why this should happen as I am supplying a perfectly valid path. Could someone please take a look at my VI and help me out? 

[altenbach]

What's the value you enter in the path control?

(The browse option should be "existing folder", you currently have it on "existing files or folders")

[sharmishtha]

I enter a directory name; and the directory actually exists on my hard drive. 

[altenbach]

Place an indicator after "build path", run the VI, turn the indicator into a constant (right-click terminal...change to constant, now containing the generated path), and attach the VI once more. What is your OS?

[sharmishtha]

Hmmm interesting...the browse option has always been existing files or folders..and its never shown this error before. Anyway, I'm still getting the error even after I change the browse option to existing folder. Plus the error is happening from the Write to Measurement file.

Thanks a lot for taking a look by the way..

[sharmishtha]

OS is Windows VISTA

[altenbach]

I don't quite understand your code, because you are not actually writing anything using the express VI, but simply use it to generate successive filenames. Can you probe the file output there?

[sharmishtha]

Well, I do that because, as you might have noticed I have two different slave loops: one for channel control, which basically detects if there has been any change in the push button on the front panel, and every time the button goes from off to on, generates a new file name. I dont know if there is another way to generate successive filenames; the write to measurement VI seemed easily configurable that way, which is why I am using it, without explicitly writing anything using it. 

The other slave loop is to acquire data at a rate determined by the "time between acquisitions" control, from the DAQmx channel, and actually write the data using another write to measurement VI, to the filename supplied from the previous iteration. It is at this VI that my Error Code is getting generated. 

I guess this is a sort of a weird way to generate data, but my specs require me to detect changes in the boolean push button and generate the successive filename immediately, which is why I couldn't find any other way of implementing this other than the master-slave framework. 

And yes, I probed the file output at various points and there are all correct upto the point where the time-control slave loop takes in the filename input. After that, the Write to measurement VI just generates an error code, apparently out of nowhere. 

Thanks a lot for your help.....