Report Generation VIs

Can VIs on the "Report Generation" palette in LV 8.6 be used or do they require that an additional utility be purchased?
Thanks,
Chuck M.
Solved!
Go to Solution.

Good Afternoon Chuck,
The NI LabVIEW Report Generation Toolkit for Microsoft Office is an additional package that needs to be purchased and activated before being used. Seeing the "Report Generation" palette and sub-VIs on your Functions palette simply means that the toolkit is installed; it does not guarantee that you can use them.
To confirm that the Report Generation Toolkit is activated (and useable), open NI License Manager, navigate to the Toolkits branch under your version of LabVIEW, and confirm that "Report Generation Toolkit for Microsoft Office 1.1.3" has a green box to the left of it.
If the box to the left of the name is not green, it means that particular product is not fully activated. To activate, right-click the name, and click Activate. Follow the on-screen instructions to activate. If you believe that you have purchased this Toolkit and are unable to activate it, please go to www.ni.com/ask to create a phone Service Request. An Applications Engineer will help you activate your product.
Regards,
Charlie Piazza
Staff Product Support Engineer, RF
National Instruments

Similar Messages

Report generation vis are not running in exe

HI
Im using report generation vis for create a excel report.Its not working in exe.Even i included the Nireport.llb in
(C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility)to my project.wat to do?
kavi
Solved!
Go to Solution.

Hi kavi,
did you get some warnings while building the application?
See this link:
http://digital.ni.com/public.nsf/allkb/2AE85CF95217E60786257540000D818C
Mike

Generate report using Word Report Generation VIs error

When I Generate report using Word Report Generation VIs ,the error is generated.
This is my Vi
can somebody tell the error reason?
The attaché is Vi (one is 2011,other is 8.6)
Attachments:
report-8.6.vi ‏16 KB
report2.vi ‏33 KB
template.doc ‏40 KB

Hi Ben64
Thank you! The problem is solved.
BUT when I use the Word Easy Graph vi ,the result is
I want the Graph (curve),like as:
How Can I do get the picture.
I have other problem. I want to get default name for the new word file.
liang

Difference in the appearance of HTML vs. Standard reports generated with the Report Generation VIs?

When I generate a "Standard Report" (to a printer or PDF) with the attached code, the output looks like this:
If I instead use the same code to generate an HTML report, the output looks like this:
Can anyone explain why the HTML output has had the extra spaces stripped out of it?
Is there anything I can do to prevent it from happening?
VI is attached (LV v11.0.1f2) but this is what it looks like...
Attachments:
Print Test.vi ‏47 KB

SteveBale wrote:
If you look at your html source the spaces are there. The problem is the way html is rendered it removes the spaces. You will either need to add in <pre> </pre> tags to tell the browser to include those spaces, or insert the string   which the browser interprets as a single space.
Regards,
Steve
OK, thanks. I guess I'll end up living with it the way that it is because
using either method seems to also have the side effect of causing the output to become double-spaced and
the only reasonable place to implement the change (so that it did not also impact the "standard report" output) would be within the report generation VIs and I'd rather not be modifying them.

Report generation VIs in Labview 6.1

Hello,
I am havinf problems with using Labview 6.1 VIs for report generations. The VIs provided by Labview are not executable! It seems as if they had internal errors, non fixed errors. Moreover, I am not able to open the diagram because it is password protected. Does someone know if there is any patch to fix this or the reason why these VIs don't work?
Thanks a lot!
Regards,
María

Hello Maria,
are you using the report Generation Toolkit for MS Office or the standard vis that LabVIEW provides for report generation?
If you use the Office toolkit, this may help:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c8888a9a74e75c4786256cda00694a1e?OpenDocument
If not, this may also help:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/9acb175f6de483ae86256b2200776b8b?OpenDocument
In any case, WHAT I WOULD TRY FIRST is to do a Mass Compile of the folder where the report vis are located.
Here you can see what this does and how to perform it:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/654877e62a97b72986256c95006f9b24?OpenDocument
One last question...are you having trouble only
with executables or also during development?
Regards,
JorgeM.

Word report generation VIs are not found.

Hi,
I've installed LabVIEW 6.1 followed by installing Report Generatio Tool set, but I don't find word specific VIs and excel specific VIs on Function Palatte. Could u plz. let me know what I m missing there.
Regards
GNS

GNS,
Which version of the toolkit did you install?
Do you see the Report Generation Toolkit listed under the Add/Remove Programs in control panel?
If you have multiple versions of LabVIEW, check in which folder did the toolkit get installed.
Can you find word and excel llbs under ...\LabVIEW 6.1\vi.lib\addons\_office directory?
If these VIs didn't get installed, you should check the version (LabVIEW 6.1 needs toolkit version 1.0.1) and reinstall the toolkit.
If you do have these llbs, try to manually edit the palettes and add new subpalettes linked to these menu files:
LabVIEW 6.1\menus\default\excel.mnu and
LabVIEW 6.1\menus\default\word.mnu
Check out the following KnowledgeBases as well
"Palettes Not Populating" Error with the Report Generation Toolkit 1.0 for Microsoft Office and LabV...
Installing the Report Generation Toolkit on Multiple Versions of LabVIEW
Zvezdana S.
National Instruments

Report generation broken VIs in LV2009

Hi,
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Utility\NIReport llb has 2 VIS "Get modified data" and "Set modified data" which are used by Report generation tool kit .
I installed LV2009 in which "Get modified data" and "Set modified data" are not present. When i installed report generation toolkit then, the report generation VIs in "LV2009\vi.lib\addons\_office" VIs are broken because they are search for above mentioned VIs.
Report generation 1.1.1 is what i am using.
Please suggest me a solution.
Regards,
Muthuraman S
Message Edited by Muthuraman on 10-29-2009 01:10 AM
Regards,
Muthuraman

yes might be, why don't you use the report generation toolkit along with the developer suite.
because same thing happened to me when i installed Report generation 1.1.1 with LabVIEW 8.6, then installed Version 1.1.2 which was along with developer suite.
Regards
VIsuman

Error Showing While Using Report Generation ToolKit VIs

Hi All,
           When I use report generation VIs Like Excel Easy Tables its showing following errors and i am not able to contiune using the same,
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\utility\NIReport.llb\Set Report Font.vi
    - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
    - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
what might be the issue, i am using LabVIEW 8.2

Hi,
In
LabVIEW 7.1 and earlier, subVIs could be kept in memory by wiring a
constant to a Case structure and placing the subVI in a case that would
not be executed. For example, you could wire a True constant to the
Case structure and place a subVI in the False case of the Case
structure, and LabVIEW would load the subVI along with the calling VI.
However, from LabVIEW 8.0 onwards, the case structure is optimized to remove code that is not going to be executed. Changing the
constant to a control ensures that this VI behaves as it did in LabVIEW
7.1 and earlier. If the intent is not to keep the subVIs in memory, you
can change this control back to a constant by right-clicking the
control and selecting 'Change to Constant' from the shortcut menu. The
proper way to keep a subVI in memory without calling it is to use a
Static VI Reference.
Good Luck!
Warm regards,
Karunya R
National Instruments
Applications Engineer

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

Report Generation & image

Hello,
I have been using Report Generation VIs to print Control/Indicator (Front Panel)icons on Word Document. The only issue is that it is so white that it blends with the background (example attachment below). Any suggestions.
Also, how can I use Report Generation VIs to print items (i.e. case structure and the items within it) from Block Diagram into Word Doc.
Thanks.
Attachments:
DocumentPicture.doc ‏24 KB

To answer your second question about inserting a Block Diagram image into your report, one way to do it would be to use a VI Invoke Node with the method Block Diagram >> Get Image Scaled to output Image Data for your Block Diagram (or whatever VI's Block Diagram you wire the VI refnum in for). Then use Draw Flattened Pixmap to change the Image Data format into a picture format that you can wire to a picture control. Then create a reference for this picture control and wire it into the Report Generation Toolkit VI called Append Control Image to Report. That will accomplish what you want.
I'll attach an example below, but unfortunately I only have the Report Generation Toolkit installed for LabVIEW 8 right now. I'll also paste the image below so you can get an idea of what I'm doing.
Message Edited by Jarrod S. on 04-14-2006 01:27 PM
Jarrod S.
National Instruments
Attachments:
ReportGenBD_Example.vi ‏20 KB
Screenshot.JPG ‏57 KB

Report Generation: what determine row height?

When using the standard report generation vis, and I append a table, what determines the height of the rows? You can set the column width, but even down into all the vis, I don't see any way to control this.
This is in Labview 8.5.1
Message Edited by remenakb on 04-21-2008 12:53 PM
Brad Remenak
Certified LabVIEW Architect

I have a Zebra printer I am trying to print to and it seems like the row height is determined from just the text length. Even if the column width is plenty wide enough. But if I send it to a regular Canon printer the table seems to print fine.
Brad Remenak
Certified LabVIEW Architect

Report generation tool kit not printing

I had the report generation tool kit version 1.01 for some time but never used it. I was comfortable with printing front panel vi 's.
But now I installed it on my computer with a windows 2000 and LabView 6.02 .
I created an application (executable) that will print (using the report
genartion tool kit). The application works fine in my development computer
(win 2000).
When I installed it on another computer with a win 2000, it prints as
expected
but when I try to exit I get a message from windows that the application is not responding (I have to go to task manager and terminate the application).
Both computers have word and Excell installed
I installed the application on a third computer (win 2000), but this com
puter does not have word or excell installed. The application does not print the
portion of the software that uses the report generation tool kit, but it can print the front panel of vi's (set to print an end of excution).
In all 3 computers, I have runtime engine 6.02 installed. My vi is simply
the example vi ""Sample test report.vi"", but customized to my application, printing standard report.
What is happening ?

Based on what you sent, the version of Excel and Windows that are being used is a non issue since none of the code makes any calls to either one. They all refer to the older version of the report generation VIs that use NI's proprietary report generator.
I can think of two explainations. First, you aren't using what you think you are. Second, NI retained the same VI names when they went to the Word/Excel version of the generator, and I am linked into the old version.
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

Problem building application 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 with excel 97 Graphing issue

I am trying to set-up mu data output to use the report generation Vis. However I am running into a problem when trying to update 2 graphs on the same sheet in Excel.
My set-up is:
Windows XP
Office 97
LabVIEW 7.1.1 with the Office toolkit installed
I noticed that I can write to the first Graph and update it without issues, but once I try to update the second I get error -41105 stating that MSGraph is not installed.
I did notice that if I set a break point between the Excel Quit Graph.vi and Excel Update Graph.vi if I click the mouse within excel in removes the highlight border from the first graph, the I continue and it works fine. For some reason LabVIEW is not releasing that Graph to be able to select another.
I tried to write data to a cell after quiting the graph and then selecting the second graph but that is not working either although it does work manually.
Next I may try a Macro but I would rather not have to do that.
Any suggestions?
Jeff
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

Well after some debugging I found it. Apparently for Excel 97 only there is a problem that when you qiut MSGraph it may not save properly so the VI had the Quit Property removed.
I have added it into my code and it seems to work and will see how well it does and if I run into any problems.
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

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!

Report Generation VIs

Similar Messages

Maybe you are looking for