DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

user variables

I'm still stumped as to how to create text fields to contain test information. I would like to have a text field that I can copy and paste onto each sheet of my 30 page report. This text field would some how be tied to user variable, "serial_number" so each test I run I only need to change the "serial_number" value.

Would it be easier to modify my VI to include test information in the data array and try to extract the value from there?

What am I missing?

thanks
0 Kudos
Message 1 of 9
(5,081 Views)
Hi Zilla

Attached is an example program that I hope helps illustrate how to attached user defined information on each page of a report.

Unzip the attached and run the script "TestInfo.VBS" from DIAdem 9.0.

Let me know..

Regards

Tom Ferraro
DIAdem Product Manager
512-683-6841
0 Kudos
Message 2 of 9
(5,080 Views)
Tom,

With help from your examples I was able to figure out how to set the "T values". At least I can get some reports going by running a little script, setting the "T values" and then creating my reports.

In the near future I will need to re work my VI that generates the test data, perhaps I should reserve the first column for UUT infomation, input this info at that time and then extract this info using some type of DIAdem script. Are there some examples somewhere of this?

I'm supprised to find out that DIAdem is so script oriented. I picked up LabView pretty quick, but feel lost in DIAdem.
0 Kudos
Message 3 of 9
(5,079 Views)
Hi Zilla

How are you saving your data from LabVIEW and which version of LabVIEW are you using?

There are several options to save UUT inforamtion in a datafile that LabVIEW writes. If you do this then you do not need to use the script I sent you.

If you could briefly explain how you are using LabVIEW and DIAdem, I might be able to prescribe a few more alternatives.

Look forward to hearing from you

Tom
0 Kudos
Message 4 of 9
(5,079 Views)
The test console I'm using has LabView 6i. Right now all the vi does is record and display data from 9 Channels. Data is saved in .xls format, and I use Excel to create ploted data charts. The charts are then printed, scanned and saved as .tiff files on a server.

Problems:

(1) I had to limit my sampling rate due to the length of the test (3 hours) because of Excels file size limits.

(2) I had to run the test in 2 parts because of Excels file size limits.

(3) I could not e-mail Excel data plots due to the file sizes

(4) Excel was very slow in loading and working on the large file sizes.

(5) It was a waste of time plotting, printing, and then scanning to .tiff files my test data, when there was software availble that would allo
w (a)faster sample rates, (b) the test to be run in on sitting and (c) be able to create charts and save the charts as .tiff files. This is why DIAdem was purchased.

The plan is to now sample 3 channels at 1500 sps and 6 at 50 sps then create charts with DIAdem. Each page of the report, will need UUT info, page x of y etc. I expect each report to be apx 40 pages. I hope to be able to bundle each page of the report into a multi page .tiff file that can be moved to a server for storage.

Thanks.
0 Kudos
Message 5 of 9
(5,080 Views)
Hi Zilla,

It sounds like you have very good reasons for switching from Excel to DIAdem. Are you really saving to an *.xls file with LabVIEW or to a tab-delimited text file? I didn't know LabVIEW 6 could write to an Excel file directly.

Anyway, I'd recommend that you use the LabVIEW-DIAdem Connectivity VIs (free download) to write a DIAdem DAT file directly from LabVIEW. You can save descriptive information for the whole test and on a per-channel basis into the DAT file, and DIAdem will immediately interpret the information correctly. If you want to have a particular test property show up on each of 30 pages, though, you will still need to put a text box on each page with a reference (PropertyName = @PropertyValue@) t
o the test property in question, but no VBScript would be required if the property is automatically loaded from the DAT file.

So, you can get this toolkit from the following NI download page (version 2.0 works with LabVIEW 6.0):

"http://digital.ni.com/softlib.nsf/websearch/394875DE259B217A86256D28004059FE?opendocument&node=132070_US"

Let me know if you have additional questions,
Brad Turpin
DIAdem Product Support Engineer
National Instruments
0 Kudos
Message 6 of 9
(5,079 Views)
You can always create a user variable, serialnumber_ and get the information into it from your "UUT Info" Channel. E.g. serialnumber_ = CHDX(line,channel). Then you can make a text field in REPORT with the text @serialnumber_@. Then in every REPORT chart this @serialnumber_@ is replaced by the value.
0 Kudos
Message 7 of 9
(5,079 Views)
I save data as a .xls file, but most of the time when I go to review the data Excel sees it as tab-delimited text.



This would be fine. I will get the toolkit and try working with DAT files. I'm still not sure how to arrange the data via LabView.

Do put my Property Values in a Columns or Rows?
Can you view DAT files with NotePad?
Can I convert .txt files to DAT files?
Would this be easier with LabView 7.1? I'm hoping to get my 6.0 upgraded soon.

I would like to get some of my bugs worked out here in the office before I go down to the test console. If I can convert my data to .txt a
nd edit in where the Property Values would be then I can create a Report template...

thanks for the support.
0 Kudos
Message 8 of 9
(5,079 Views)
Hi Zilla,

There are LabVIEW VIs in the toolkit that write DAT files based on the 2D data array or 1D waveform array you pass it, plus additional descriptive information in arrays of clusters. So once you have the information you want to record in LabVIEW variables, it's a simple matter to pass those to the VI that creates the DAT file for you. Then those parameters are automatically understood and loaded into DIAdem along with the bulk data.

The DAT file format is really 2 separate files. The *.DAT file contains ASCII header information, basically all the descriptive parameters you passed in arrays of clusters, plus information on how the bulk data is stored (data types, start position, etc.). The second file is usually a binary file-- the toolkit VI will create a file storing all the values as DBLs with the file extension *.R64.

You can look at the *.DAT file with NotePad, but the parameters are identified by numeric keycode, so it's not immediately obvious to a new person what the information in that file is, and there's definitely no bulk data in there.

You can convert *.txt files to DAT files, but you need to read the *.txt file into LabVIEW, then map the items of interest, including the data array, to the inputs of the VI that writes the DAT file.

Creating DAT files is about the same in LabVIEW 7.1, but LabVIEW 7.1 natively writes TDM files with it's "Storage VIs". These TDM files are similar in concept to the DAT files described above, as they are the newer standard DIAdem files. DIAdem 8.1 and earlier versions preferred DAT files, but DIAdem 9.0 and later prefers TDM files (though it reads DAT files, and always will). So if you do upgrade to LabVIEW 7.1, I would recommend using the storage VIs that come with it to create TDM files, with no toolkit download necessary. You will find the storage VIs much more user-friendly to the LabVIEW mindset.

But as far as DIAdem is concerned, whether you use DAT files or TDM files, the benefit you get from using either is the same-- all the descriptive data set and channel properties will be automatically loaded from the file and displayed in the Data Portal. These properties will also be easily accessible everywhere else in DIAdem-- including in a text box on all 30 pages of your report.

You will find examples of writing DAT files in the 2.0 toolkit (LabVIEW Connectivity VIs), and if you upgrade to LabVIEW 7.1, you will find examples of creating TDM files in the example finder of LabVIEW.

Brad Turpin
DIAdem Product Support Engineer
National Instruments
0 Kudos
Message 9 of 9
(5,079 Views)