Diadem report generation

Hi,
I want to generate test reports automatically, so I chose using DIAdem as a report engine. But I am stuck at a point. Appreciate any help.
In our reports we need these fields: 2D string tables / 2D Axis Systems / Text Parameters
I started with DIAdem Report Express VI, but I stopped using it when i found that its impossible to transfer string arrays from LabVIEW to DIAdem. So I found Connectivity VIs. I had no problem with generating 2D tables and 2D axis systems. But I couldn't find any way for transfering texts.
I know it could be done with scripting or using ActiveX, but they have a huge API to learn.
What is the easiest way to transfer 2D string table and simple text from LabVIEW to DIAdem.
Thanks
Emre

There is a way to send text data. I use the following file. On the VI menu Connectivity-Diadem-Automation data- "Diadem variable set” Then select the text for the polymorphic version. Jim
C:\Development\LabVIEW 2009\vi.lib\addons\DIAdem\DIAdem.llb\DIAdem String Variable Set.vi

Similar Messages

Diadem report generation from LabView: textbox, textobject, table

Hello everybody,
I'm trying to generate a report from LabView and want to use DIAdem reports as templates because they easy (I thought) to configure and design.
Well, I managed to include several pictures and textboxes that I can fill dynamically with the information I want using the reort generation vi, but I ran into some problems when it gets into detail:
I also need to include a bunch of statistical data in the report together with the name of the variable. e.g. it's supposed to look like this:
testname:

duplicate

Difference between diadem and LabVIEW Report Generation Toolkit

I want to expand LabVIEW's reporting capabilities. Can someone tell me what the difference is between DIAdem and the LabVIEW Report Generation Toolkit for Microsoft Office.

Hello Mr Bean,
There are several major differences between the two solutions. I'll try and outline them as good as I can ...
The biggest different is that LabVIEW and its toolkits are programming tools and DIAdem is a ready to run application.
The LabVIEW Report Generation Toolkit basically provides an extensive library of VIs that allow you to connect LabVIEW to the MS Office library and create and edit reports in Word and Excel.
DIAdem is a stand alone application that was designed to post-process data from various sources. The tools included in DIAdem are:
1. NAVIGATOR: Allows you to import data from files (ASCII, binary, Excel, etc.) as well as DataBases (SQL/ODBC, Citadel, ASAM, etc.). The unique DataPlugin technology available within DIAdem allows you to import vitually and data file by creating a DataPlugin that describes the data format and gets linked to DIAdem. More information at: http://www.ni.com/diadem/dataplugins.htm
2. VIEW: Graphical and Numerical data inspection tool. Use cursors to zoom and scroll through your data, edit your data graphically and numerically and compare different tests.
3. ANALYSIS: DIAdem has a wide range of analysis functions, ranging from simple functions like integration and differentiation to FFTs, Order analysis and 3D data analysis.
4. REPORT: The DIAdem REPORT tool allows you to create reusable report layouts that can contain multiple axis systems (2D, 3D and polar plots) as well as tables (2D and 3D) and variables. The REPORT tool generates templates that can be usedwith multiple data sets due to the inclusion of automatic (or manula if required) scaling as well as extensive use of variables for annotations. Finished reports can be exported to printers, graphics files, the Windows Clipboard, HTML pages and PDF files (PDF writing is build into DIAdem, no extra software required). Using Scripts, it is also possible to create Word, Excel or Powerpoint reports from DIAdem automatically.
5. SCRIPT: The DIAdem scripting tools allows users to record macros or write scripts that automate complete sequences, for the import of data, via extensive analysis, to creating a publication ready report. Scripts can make reports "intelligent" by modifying the appearance of a report based on the data or calculation results that are going to be displayed in the report.
I recommend you check out the following link for more information: http://www.ni.com/diadem/
DIAdem is an extremly powerful tool for report generation. I am leaving to go on a business trip to Asia, but I would be more than happy to give you an Web presentation on DIAdem after I have returned. We could use your data and create a DIAdem report Script together online. My Email address is [email protected] and I will be back the week of Thanksgiving.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

DIAdem Report express VI works only with a single sheet template??

Hi,
I'm very new to Diadem and I'm using the 2011 evaluation version to try a report generation of LabView data (2013 version, evaluation also). I'm using the "DIAdem Report" express VI to generate a 2 pages, quite simple report; the first page has to contain some pictures and free text to be compiled with Labview strings, and the second page has to show an XY chart. The goal is to export in PDF file format.
Creating two separates TDR report models for each page and calling two instances of the DIAdem Report, the report is generated correctly with the expected value in two separate pdf files. If I'm using a report template with the two previous pages loaded in two sheets, the text value and the XY data are not loaded in the PDF file, causing a two pages empty export (only images, default text and chart border are visible).
I'm missing something? Attached a TDR file that reproduce the malfunction.
Many thanks in advance.
Solved!
Go to Solution.
Attachments:
1+2.TDR ‏59 KB

WorldTraveler
When I have a report that has multiple pages (Over 5) I like to use one tdr file for each of the pages, and then use the report append feature to make a resulting tdr and then a PDF.
(Search for report appending)
I make one cover tdr and one summary.tdr file, and then work to try to make the other sheets as reusable as possible. That way I can build each resulting large TDR from a appending of as many smaller tdr files as needed. This really cuts down on the maintenance time for reports, and results in large PDF at the end, so the users do not know the difference.
Paul

Report generation with excel (picture)

hello,
I need to insert pictures into excel. I have already printed the report generation toolkit for microsoft office and downloaded Picture_To_XL_(6i). But I have nothing to do the report : for in instance write jpeg file (excel).vi,read jpeg file (excel).vi, read png file(excel).vi...
Where can I finf this ? I have 3 Cds with labview:Labview 7 express, national instruments device drivers and DIAdem.
I have download an install update bur does not work.
How can I do?
thank you to help me
labview 7.0

You can get an excelent Excel Active-X control from the gentleman at the following e-mail address:
[email protected]
Also, I have included a PDF description of the item. It is for sale, but it is CHEAP, and well worth the low asking price.
Attachments:
excelocx.pdf ‏248 KB

.tdms report generation with .pdf format

Hi,
My problem is a kind of report generation problem.My data logging format is .tdms format and i use tdm file viewer function to view my datas but i didnt use tdm data report generation function.How can i use this function with my code.Actually i want to print automatically like pdf format...
Attachments:
ustalt.vi ‏62 KB

kacco wrote:
Hi Yye,
İ use diadem and labview 09. I know diadem is very good solution to view data but i want to print automaically.My data type is .tdms(test data management system) if u look my .vi you can understand.
ı want to print aoutomatically with my channel and group.
I can see from your code that you are a beginner. Your coding style is very Labview no-no. But well every Labview pro have some time been a beginner I have some problems understanding or grasp the essence of your problem. Can you post your failed attempt to use rapport generation. It would help in the understanding of your problem.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Open vi error for report generation toolkt

Originally it works fine.
Now I upgrade to win7, LV9 and office2010.
To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
But still got the error as attached.
Any suggestion, thanks.
Attachments:
ss.png ‏184 KB

1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

Report Generation: New Report.vi

Running applicaion in development mode works fine.
After compiling however I get Error 7: Open VI Reference in New Report.vi
Why am I getting this error?

Has the version of Office on your machine changed since you installed the Report Generation Toolkit? The VIs will become broken if the ActiveX interface changes, and this can happen when the Office version changes. I recommend uninstalling and reinstalling the toolkit. Also, what version of Report Generation Toolkit are you using? The latest version is 1.1.1.
-D
P.S. - I'm going to respond to your other thread that you started with a link to this one. Instead of creating multiple messages on the same question, just wait for a response to your initial thread.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Report Generation Toolkit Error (undefined erro)

Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
Any ideas?
nrp
CLA

nrp wrote:
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
Was it the first time you attempted to write the table to that spreadsheet?
Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
- Partha
LabVIEW - Wires that catch bugs!

Report Generation Exe Error

Hello,
I am using LV 8.6.1 with the 1.13 report generation toolkit and I am having problems getting my built exe to work. I am trying to open an excel template and populate it with new data. I have broke the vi down to just opening excel - opening the template and then fill in some data. But at this point excel does not open at all. And naturally everything works fine in the development environment.
Error Code: -2147352573
Member not found in NI_ReportgenerationToolkit.lvlib:
Excel_open_workbook.vi
NI_Excel.lvclass: new reportsubvi.vi
I read a few help pages that said to add \vi.lib\utility\NIreport.llb and LVclass directories to the project folder and add them to the always include section of the build. But no luck so far.
Side question: The machine I want to use this on has 8.6.1 Full which does not have the extra excel functions that my developer has. Is there a way to install the DEV report generation toolkit in the full version? Then I would not need to build an exe.
UPDATE: I just tried the exe on a different machine that has a developer suite installed and it worked fine. So I guess I need to find out what else I need to add to the build to make it work.
Message Edited by _Bryan on 06-16-2010 11:58 AM
Solved!
Go to Solution.

There should be some info on this in the KB.
But first you should make sure that your version of the report generation toolkit actually supports excel 2000 (which is 10 years old)
That should be in the release notes of the toolkit
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Report-generation vi problem

On a Windows XP system using the "Text Report Example" vi, the (read) report property node item "TextFont" (stdole.Font) at the beginning of the "Font Style" vi which is a part of the "Set Report Font" vi is returning this error:
"-1073741819 Unknown System Error in Font Style.vi->Set Report Font.vi->Easy Text Report.vi"
Any suggestions as to a cause and cure?

This Knowledge Base from NI's website actually deals with this problem. The fix depends upon whether or not you have the Report Generation Toolkit for LabVIEW. There are fixes for whether or not you have the Toolkit. Hope this helps.
J.R. Allen

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

Hi everybody,
I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit. My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
"Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi" That is the exact wording, even with the weird punctuation and capitalization.
The first occurrence of the error is not determinate. Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up. Once this error occurs, I must quit LabVIEW to resolve it. If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs. Excel_Open.vi is another.
These logging VIs have worked just fine until upgrading to Excel 2007. I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1. I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support. However, even after upgrading, I'm still getting the same errors. I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application. The error occurs both in the LabVIEW IDE and in the built application. Does anybody out there have any idea what I can do to fix this? I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
Thanks,
Phil
Solved!
Go to Solution.

Hi Christian,
I do not see that exact option listed, do you mean "user interface"? I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller". Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
Thanks,
Phil
Attachments:
VI_properties.png ‏15 KB

Report generation for FPGA VI

Hello..
I want to include the number of resources used by FPGA (LUTs, slices, blockrams etc) in my report generation.
After compilation is completed, a window showing these resources will occur. But, how can I add this compilation report in my report generation...
Please let me know..
Thanks
Prashanth
Solved!
Go to Solution.

Hi
I made a small code which helps you achieve this functionality.
Hope it helps!
In this code: I read from "toplevel_gen_xst.log" file generated for the project; search for the string "Device utilization summary" and extract the part of interest Now you add this extract to your report compiled using report generation toolkit.
regards,
Ravi.
Attachments:
image.jpg ‏60 KB
FPGA Utilization.vi ‏10 KB

Diadem report generation

Similar Messages

Maybe you are looking for