Report generation write to file at interval

Hi,
I am using the report generation toolkit to write data to an excel sheet. I am recieving a lot of data but only want to save the data to the excel sheet every minute. I have found threads about doing this with the Write to Measurement Express VI but I am not using that and am unsure how to translate that code to something I could use. Any ideas? I have tried using a case selector around all of the report generation VIs but that doesn't seem to work...
Any help is appreciated!

Nice, can you help  kmarcella work that into his code?
Well, the example that I post shows the Big Picture for doing what KMarcella wants to do, namely collect data periodically (like once a minute) and write all of the data, presumably one Excel row at a time, to an Excel Workbook.
The Original Poster has the best understanding of the details of the task, but here are some suggestions that should help him (or her!).
Divide the task into phases.
Initialization Phase -- set up DAQmx channels, define timing parameters, open Excel Workbook.
Loop (repetitive) Phase -- take a single reading, write a single row (or rows) into Excel, and wait for the next point.
Finalization Phase -- close DAQmx, save the Excel Workbook and Dispose Report.
Note that these phases are illustrated in the example -- there's stuff before the loop, the loop, and stuff after the loop.
Strive for compactness and simplicity.  Try to fit it on a single screen (1280 by 1024) -- use sub-VIs where necessary to "encapsulate" (or "hide") the Messy Details.
Try to not use Express VIs.  For example, a simple Wait to Next ms Multiple is much simpler, more compact, and intuitive than Elapsed Time.  You are to be commended for using DAQmx calls directly.
I am completely befuddled by your use of the Dynamic Data Type.  It looks very complicated, lots of extra wires, bloating the Block Diagram.  It might be necessary (only you know the requirements of the task), but I suspect there is a simpler solution that works with the arrays of data directly.
However, that raises another question as to the nature of the data being collecting and the data being saved.  I notice that you are sampling M channels, N samples (I don't know what M and N are),  Am I correct that you are sampling way more points than you are writing to Excel?  If you are only doing one write a minute, are you sampling faster than 1/minute?  What are you doing with the other points?
The reason for the previous question is that my model of your task might be wrong!  I'm assuming (and my code does this) that you sample periodically (one sample at a time) and write each sample to Excel.  On the other hand, if you are sampling frequently and writing infrequently (say, sampling at 100Hz, maybe displaying the data, and writing a "representative point" every minute), then my model, with the writing in the same loop as the sampling, should probably be replaced with a Producer/Consumer pattern, where you "export" a point once a minute to a parallel "Write-to-Excel" loop.
Another possibly-helpful example is one I posted here about a year ago.  If you go to the Search box and type the word Revised, the first entry that pops up should be my earlier post.  I think it's a snippet -- try it out and adapt it to your problem (as far as formatting and structuring the page).
Bob Schor

Similar Messages

  • Report Generation to PDF File Fails

    Has anyone else encountered anything like this. I have a report (Oracle Reports 10g) that's fairly straight-forward; the query basically joins a couple of tables and utilizes maybe a dozen Function Columns. For smaller units within my organization it works fine. I can generate the report for on-screen display or generate it as a .pdf file. If I select a larger, more complex unit on the parameter form, it will still generate the report on-screen just fine in 15-20 minutes; however, it will not generate to a .pdf file. I don't get any error messages, the Report Progress window just sits there for hours and hours, even over night.
    Any suggestions?

    Hi,
    Run it to paper layout and check how many pages it generate.
    Go through this link
    Reports Builder and rwrun.exe hang on pdf creation

  • Problem building applicatio​n using Report Generation Toolkit, LV 2011

    I'm using LabVIEW 2011 under Windows 7.
    I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
    Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
    I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
    In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
    So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
    The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
    When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
    Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
    VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
    I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
    Thanks very much,
    mws
    Attachments:
    Test-App-Build.zip ‏336 KB

    Hi again,
    If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
    The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
    When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
    When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
    In the development environment, the whole thing runs with no problems.
    Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
    I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
    Thanks very much for any help!

  • Report Generation Toolkit - Write cells to already open Excel file.

    Greetings,
    Does anyone know a way to write numeric cell values to a worksheet in an Excel
    spreadsheet that is already in memory using the Report Generation Toolkit?
    I've found that if the spreadsheet is already in memory and the user has made
    changes to it without saving the changes, when LabVIEW opens the reference to
    the report, the user’s changes are overwritten if they have not been saved
    since LabVIEW opens the last saved version of the spreadsheet.  I'm aware
    that there is a setting to "display alerts" to the user but I'd
    rather not do this.  I would like simply to obtain a reference to the open
    spreadsheet without re-opening the spreadsheet file.
    Thanks in advance!

    Space_Flight wrote:
    > Greetings,
    > Does anyone know a way to write numeric cell values to a worksheet in an Excel
    > spreadsheet that is already in memory using the Report Generation Toolkit?
    >
    > I've found that if the spreadsheet is already in memory and the user has made
    > changes to it without saving the changes, when LabVIEW opens the reference to
    > the report, the user?s changes are overwritten if they have not been saved
    > since LabVIEW opens the last saved version of the spreadsheet.&nbsp; I'm aware
    > that there is a setting to "display alerts" to the user but I'd
    > rather not do this.&nbsp; I would like simply to obtain a reference to the open
    > spreadsheet without re-opening the spreadsheet file.
    >
    > Thanks in advance!
    Space_Flight:
    I do not believe this is possible to do with the report generation VIs
    (although I have VERY little experience with these. If you really had
    to do it this way, you could use activeX controls to manually right
    values to cells in an open excel spreadsheet, but this can get rather
    cumbersome. Are users changing the values in the spreadsheet while
    your program is running? Is there maybe a way around this?
    -Ray

  • Report generation vi's-save report to file.vi

    I am a new user of LabVIEW. I'm using the Report Generation Toolkit VI's to do some customized reports.
    1. how can I stop the report from popping up on the front panel when I initialize the report to be done. I know you can use "minimized" but that takes a few seconds to minimize and I would like to NOT see the report I'm generating pop-up at all.
    2. I want use this customized report and constantly be saving data when a reset button is pushed. That is save the time stamp, the change in data etc on a continuous basis in 1 folder. Right now when I use the "Save Report to File. Vi" it over writes the previous data saved and all that data is lost. I need to be constantly saving all the data generated to be able to look back at it.
    Thanks.

    Hi shaef,
    Which version of LV and Report Generation Toolkit are you using?
    Assuming you are using LV 8.5 and RGT 1.1.2, then the attached screenshot should offer some help.  Basically, you need to wire in the existing file as your template in order to not just overwrite the old data.  You also need to make use of the series of 'Append' VIs that are in the toolkit.
    Let us know if this works for you,
    David_B
    Applications Engineer
    National Instruments
    Attachments:
    2008-03-23_165242.png ‏5 KB

  • Problems in using Application Builder to Build a exe file with Report generation Toolkit

    Hello,
    It's my first time to build exe. But I have Problem  when the VI have Report Generation toolkit VI.
    It's no problem in VI Format , But It can't work when I build as EXE format
    Can Anyone help me, and state step clearly in how to  solve the problems?
    Thank you!!

    If the code works OK in the development system but not in an executable there are a few things you can check. The two most likely causes are:
    There is an error occuring that your code isn't reporting.
    There is a file path that under the executable isn't valid.
    First make sure that all the error clusters are daisy-chained together in the subVI that you wrote to create and populate the excel file. Next make sure that the end of that chain goes to an indicator on the VI's front panel.
    Second, make sure there are indicators on other key parameters like the path the file is trying to write to.
    Third, temporarily modify the VI properties of that excel IO VI to open it's front panel when called, and rebuild your application. The next time you run the application the front panel will open when you try to write to the excel file and you should be able to see what is happening.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • How do I save a Report to file using Report Generation vi's?(not HTML)

    Hi,
    Sorry about re-stating the problem.   I am using the Report Generation vi's to create a report. There is an option to save HTML reports to file, however I must use Standard Report because I need to print in Landscape mode. HTML reports will not print in Landscape. One of the requirements is to save the report to file on the hard disk. I have tried to use the standard Open File and Write File vi's. A file is created, but the report is not saved into the file. How do I connect a report so that it will be saved in the file? I already tried simply wiring the report refnum into the data input of the Write File vi.
    I have attached an example of my code.
    I am using V7.1 Full Version.  I have V8 available if that is any help.
    Any ideas?
    Thanks,
    Chris
    Attachments:
    ReportExample.vi ‏52 KB

    I did find this KB: How to Save Standard Reports?
    Attached is an example of how to do this.  You will have to relink the subVI's or else you will have a broken arrow. One is in LV7 and the other is in LV8
    Message Edited by Sam R on 12-15-2005 02:25 PM
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~
    Attachments:
    Standard_to_HTML_LV70.zip ‏23 KB
    Standard_to_HTML_LV80.zip ‏29 KB

  • Creating new file using report generation express vi

    Hello,
    In my application, I need to write certain data in excel sheet. For that I created an excel template and I used the express vi in report generation toolkit to save the appropriate data in appropritate columns. I need a new file created everyday by that day's name and write the data to it rest of the day. I am having problems creating new file using this express vi. I tried using the low level vi's but not been able to it properly.
    Attaching my code and excel template.
    Please help.
    Thanks!
    Solved!
    Go to Solution.
    Attachments:
    excel write2.vi ‏119 KB
    Book2111.xltx ‏8 KB

    r_te wrote:
    The thing is everyday there cannot be a file provided.
    Sure there can.  Don't you see the input on the Express VI for a file? "Path To Save Report" is the name of the input you want.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • LabView Exe Applicatio​n file not launch Excel applicatio​n for report generation

    Dear All,
    I created one LabVIEW application file for report generation (using Excel Template).
    While I run the program in programming mode it works well and create the report file in the specified path.
    After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
    Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
    Give me the solution.
    Thank You
    Jegan.

    Hello,
    Most likely you are encountering a problem of stripping and/or building paths.  Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like.  If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
    I think this will bring some clarity to the issue!
    Best Regards,
    JLS
    Best,
    JLS
    Sixclear

  • Report Generation tool kit for MS office (Opening an existing excel file and appending to the bottom)

    I don't have any problems creating and filling an excel sheet with data. I use the New Report.vi, Easy Title.vi, and Easy Text.vi to create the file. I then save and dispose properly.
    What I don't seem to be able to do is open the exsting file and append data to the end of the sheet.
    Thanks in advance for your help.
    todd

    Hi Todd,
    You can do this by creating a new Excel report with the existing excel file path wired to the "template" input. Then use "Excel Get Last Row.vi" (located under Report Generation\Excel Specific\Excel General) to obtain the location of the last row. Then use that location to input new data into the file.
    Hope this helps,
    Dan

  • Report Generation Toolkit files in incorrect location after installing deployment

    TestStand 2010 SP1 + LabVIEW 2011 + Report Generation Tookit
    After installing a deployment, the location of NI_Excel.lvclass is expected to be at ...\VIs for <project name>\SupportVIs\Excel\NI_Excel.lvclass (see attachment)
    but the path of the file is located at ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
    In the deployment image, under the target folder, the file is in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
    and the lvproj finds the file.
    The lvproj in the installation finds the file in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
    Renaming the folder from data to Excel fixes this problem.
    Has anyone else run into this problem?
    Attachments:
    Report Generation Toolkit Error.png ‏15 KB

    I am facing the same issue when I create the TS deployment through utility using TS2012.I thought of adding the file to the Teststand workspace and give the destination in to supportVIs directory.But even tthat didn't worked as it was copying all excel vis in to two locations.
    Even adding the Directory path in to TS search directory options  to "\data folder"  is not resolving the issue and LAbVIEW Vis are not able to locate it.

  • 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

    @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
    Attachments:
    Untitled 7.vi ‏75 KB
    Untitled 7.JPG ‏99 KB

  • File Dialog and Report Generation Toolkit

    Hi,
    I designed a VI for an electrometer calibration and it works quite well The only problem I have is the following:
    I used the Report Generation Toolkit to put the measurement data in an Excel file. When I run the VI I'd like a window to pop up to define the location and name of the Excel report file. If these two things are done LabVIEW should create the specified Excel file and run the rest of the code.
    So i tried this with the "File Dialog" Vi and all the needed low-level File I/O VIs and it worked.
    But when i connect the "File Dialog" VI with the "New Report" VI of the Report Generation Toolkit I get an error message.
    Is there any solution to get this file dialog pop up window with the Report Generation VIs?
    thx for any help...!
    Message Edited by Flea on 12-15-2005 03:58 AM

    Wow, thanks for your fast and very helpful reply devchander!
    I already tried this and it works fine
    thx!

  • Unable to write an image to excel with report generation toolkit

    I am unable to write an image to excel with the report generation toolkit. The VI works fine for word, but when I select Excel the speadsheet pens but remains blank.

    Ranjeet
    I am using Labview 2013 or 8.0, but here is an image of the very simple test VI.
    Regards
    Steve

  • Excel data write using report generation vi's

    I can read data from an excel sheet but can not figure a way to write data to specific cells using the LabView report generation vi's.

    In the "Excel Easy Table" VI you can specify where you want a table to be placed by wiring a value to the 'Start (0,0)' input. If you want more control than that you will have to open the "Excel_Insert_Table" vi and modify it. It is located in the _exclsub.llb library. I highly recommend making a backup copy of this llb before modifying any VI's in it.
    Chris_Mitchell
    Product Development Engineer
    Certified LabVIEW Architect

Maybe you are looking for

  • Clarification needed in the Fault Handling Framework(Error Hospital)

    Hi, I need some clarification on Fault Handling Framework... Scenario: My BPEL Process is Asynchronous.(10.1.3.3.1) and I tryed to invoke the another BPEL Process( which is used to select the Fname from the table using DB Adapter) . In the Main BPEL

  • Measuring Point Status.

    Dear All Consultants, I have scenario for warranty services, so I define master warranty with to conditions “years - kilometer reading”. The problem is while assigning master warranty to equipment master system gives me this error {could not determin

  • PeopleSoft 8 column Trial Balance for Chile

    We have a requirement for a 8 column Trial Balance for Chile. Is there anything delivered in PeopleSoft? If not has anyone developed an sqr for Peoplesoft like this? Thanks, Ken

  • Smoothing Options in FCPX Stabilization

    Can someone please tell me what the SMOOTHing options refer to? There's Translation, Rotation, and Scale. I can't find anything online or in help videos or aticles referring to what each option corrects. For what motions do you use each one? I have a

  • ICal event reminders/alert not showing up

    Some of my events that are marked for a reminder/alert are not showing up on my computer however, they are showing up on my iPhone