exporting data

[aputman]

---

@yazan206 wrote:

the only way to export data from labview is to excel. 

---

Where did you read that?  It would be a terrible decision on NI's part to only allow export thru Excel.  CSV is not an Excel file.  Neither does "Write to Spreadsheet File" (or "Write Delimited Spreadsheet") refer to Excel.  CSV is a comma separated values file (text file) that is quite often, and wrongly, confused with an Excel spreadsheet.  Excel and most other math based programs know how to export and import CSV files (Labview included).  You should not need Diadem unless you are dealing with gigabytes worth of data (and even then, I'm not sure if Diadem will help).  At that point, you may be running into OS file size limitations.  

[crossrulz]

---

@yazan206 wrote:

but the only way to export data from labview is to excel

---

Where did you get that thought?  As already stated, use the Write To Delimited Spreadsheet to save the data to a CSV file, which is a format of a text file.  Matlab can inport that.

I am really confused why you need Excel to act in the middle.  If you want to view the data, just use Notepad or Ultra Edit.

[yazan206]

how do i wire the write delimited spreadsheet? 

Cheers

[yazan206]

I have recently started using labview so I dont have much experience in using it 

[aputman]

Ctrl + H will bring up the context help.  Read thru the documentation, give it a whirl, and report back with any problems you encountered. 

Spoiler

This may be a bit obvious but the filetype and extension should be .csv (which stands for COMMA separated values).  

[aputman]

You might also want to look at the top of the forum and go thru some of the recommended LabVIEW training resources.  

[yazan206]

[GerdW]

Hi yazan,

still no VI attached…

- You might wire a file path to the WriteFile function to avoid stalling your loop with dialogs…

- You might NOT wire a buffer size at DAQmxTiming function. Read it's help!

- You might have DAQmx do the file saving (to TDMS) on its own using DAQmxConfigureLogging. It's explained in the LabVIEW help and example VIs!

- When nothing else helps (which I doubt for your application) you still can implement a consumer-producer scheme to decouple DAQ from file saving…

[yazan206]

i have managed to figure it out and make it work, however, it is only recording the values as big as my samples per channel, for example my samples per channel is 3000 so it saving the first 3000 values and disregarding the rest, how can i remove that restriction? 

Cheers

[GerdW]

Hi yazan,

for example my samples per channel is 3000 so it saving the first 3000 values and disregarding the rest, how can i remove that restriction? 

So your waveforms contain 3000 samples and all of them are saved!?

Which restriction do you want to remove - when all of your samples are saved???

Generic suggestion:

When you have problems with your VI you should attach your VI with your message!