LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

problem writing to excel file using report generation toolkit

hello everyone, i have this report generation toolkit... and i want to output DAQmx Analog I/P data on to an excel sheet. the DAQmx is programmed to collect 

data at 3samples/sec. however, when i see the excel file that Report Generation Toolkit generates, the time stamp is updated every second instead of every 0.33sec. 

 

can anyone please help me?  i am using the MS Office Report Express VI. 

 

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 1 of 16
(4,110 Views)

can anyone please help me out on this?

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 2 of 16
(4,093 Views)

CrackJack,

 

When you look at the excel file, do you see consecutive timestamps with the same exact value?  As if they were rounded off? 

0 Kudos
Message 3 of 16
(4,087 Views)

Wayne, please see the attached file  for the output.. i am outputting a DBL from the DAQmx Read.vi

i can post the block diagram, only thing its very messy.. but i will do that.

 

however, more info about the block diagram... what i am doing is indexing the DBL data into an array inside a while loop. after the while loop terminates, this entire indexed DBL array is

passed into the MS office Report Generation.vi

 

is it because I am producing DBL format data from the DAQmx Read.Vi that i do not have any time information on the excel file?

 

I am sorry if i sound too messy

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 4 of 16
(4,080 Views)

Post your code.

0 Kudos
Message 5 of 16
(4,071 Views)

Try using a waveform instance of the DAQmx Read.VI instead of the DBL.  The double does not have a timestamp associated with it.  The waveform data type contains the dT and the timestamp associated with each sample.  So what you were probably seeing with the Excel file is the index of the array followed by the DBL information associated with that array. 

Applications Engineer
National Instruments
0 Kudos
Message 6 of 16
(4,070 Views)

@All, I got rid of the express VI, decided to work on the custom low level VIs instead. however, i have a new problem now... 

 

I have a case statement wherein, the user selects if he wants to start generating a report. once the program enters tat loop, the program speed reduces! 

 

can anyone please tell me why is it happening? i ahve attached the vi... also another question.. in this VI, i am capturing the unwanted data into the graph as I am indexin the graph input. how can i make a logic 

 

that the graph captures the data only when I am switching the CREATE REPORT button (which is in the while loop). is there a way that I can append the data to the graph without creating a new graph every iteration? please let me know

thanks

Now on LabVIEW 10.0 on Win7
Download All
0 Kudos
Message 7 of 16
(4,046 Views)

Try using a producer consumer loop with an event handler.  There is a template VI in LabVIEW for a producer consumer loop, have the boolean in the producer loop in the event and then your other code in your consumer loop.  The producer creates a queue that will send to the consumer and the consumer will only run when you need it to, instead of every iteration.  Hope that helps.

Applications Engineer
National Instruments
0 Kudos
Message 8 of 16
(4,035 Views)

ok, vl try that out.. any idea why the WHILE loop slows down when i enter into CASE statement?

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 9 of 16
(4,023 Views)

A case structure can be very processor intensive and you seem to have a lot going on in that case so that would do it.  The while loop has to wait for the case to finish to keep going.

Applications Engineer
National Instruments
0 Kudos
Message 10 of 16
(4,014 Views)