Writing waveforms to file

[Will.D]

Well I do appreciate your trying to help that's for sure.

Here's something out of the help file..."file path specifies the file where the waveform is located. If you do not wire this input, LabVIEW displays a non-native file dialog box instead of a native file dialog box."

It doesn't cite a reason, and going through the vi's I'm not sure why it does, but this is the way it works on mine!

I have another method though, so I'm using that, I just don't understand why this one won't work...

Thank you again for your help (both Lynn and tbob)

[johnsold]

I missed that part about the non-native file dialogs. Since it is documented as working that way, I suspect that your only option would be to re-write the VI using a file function which observes the native dialog option. If you decide to try that save a copy of the VI to a location outside vi.lib and then modify the copy. You never know what other vi.lib VIs may use that as a subVI. If you modified the vi.lib version, it would get "reset" the next time you did an upgrade to LV.

Lynn

[tbob]

The non native file diaglog is because of the Open Create Replace WDT ArrayDlogFile.vi being used instead of the traditional Open/Create/Replace File.vi.  (Look inside the Write Waveforms to File block diagram).  The difference is that the traditional Open/Create/Replace File uses a file reference for a byte stream type of file.  The WDT Array version uses a file reference of a datalog file type.  The two file types are different and must have differences in the way they are referenced.  Also, because of the difference in referneces, instead of using the traditional Write File and Close File, special vi's called Write WDT Array Dlog File and Close WDT Array Dlog File are used instead of the traditional Write File and Close File.  Therefore you are stuck with using the non native file dialog.