Diadem FFT script

Hello
I’m trying to do an FFT and a PSD on some acceleration data that varies from amplitude in (g’s) to zero then to an amplitude.
I would like to remove the part when the data goes to zero then to amplitude before I run the FFT.
I currently do it manually using the band cursor in DIAdem. I’m new to the DIAdem and I was wondering if somebody can help.
Thank you,

Hi DSP_ott,
You can remove the offending values in your channel by using the CTNV function in the calculator:
Ch("YourChannelName") = Ch("YourChannelName") + CTNV(Ch("YourChannelName") = 0 Or Ch("YourChannelName") = AmplitudeValue)
This will replace all channel values equal to zero or AmplitudeValue with NoValue, which will be ignored when computing the FFT.
For more information about working with NoValue in the calculator, please refer to this KnowledgeBase:
Working with NoValues in the Calculator in DIAdem 10.1
Regards,
Message Edited by James M on 06-05-2007 10:57 AM

Similar Messages

Error while runing diadem asynchronous script from labview on dual core processor

Urgent need of some help / advice here!
Single core runs fine... dual core produces error: Error in <XYaxis.vbs> (line: 17, column: 1): Error while opening object. The object currently open has no subobjects. Forgotten ObjClose?
The main software built in labview used for daq and analysis generates a PDF report on completion of a test, utilising diadem. For this I use the diadem express vi in labview to generate a multi page report, whereby I use for loop to iterate an array of channels for each page. This for loop has a shift register too. After each page I run a script to adjust a few parameters like linear/log, begin/end and line thickness using the diadem connectivity tookit. See script below:
Call GraphObjOpen("2D-Axis1")
Call GraphObjOpen("2DXAxis8_1")
D2AxisXDivMode = "linear"
D2AxisXScaleType = "begin/end manual"
D2AxisXBegin = 20
D2AxisXEnd = 20000
Call GraphObjClose("2DXAxis8_1")
Call GraphObjOpen("2DYAxis8_1")
D2AxisYDivMode = "linear"
D2AxisYScaleType = "complete automatic"
D2AxisYBegin = 0
D2AxisYEnd = 0
Call GraphObjClose("2DYAxis8_1")
FOR c = 1 TO CurveNoMax
If D2CurveObj(c) = "" Then Exit For ' c
Call GraphObjOpen(D2CurveObj(c))
D2CurveLineWidth = 0.75
Call GraphObjClose(D2CurveObj(c))
NEXT ' c
Call GraphObjClose("2D-Axis1")
There is also a screenshot of the vi: (script file is generated by the Dscript vi and saved to disk. then path is passed to the diadem script vi.)
What I find is, after the first report page is complete in diadem the second page ALWAYS shows the error as shown at the top. However, on my P4 laptop with single core (no hyperthreading) its runs FINE EVERY TIME with any given number of channels/pages in the report.
My current chain of thought is that the superfast dual core is doing something in parallel therefore not waiting for the previous page to complete or finish closing its object!? however, in my for loop I use a shift register as named before, surely this kind of loop cannot be divided over more cores/parallel threads? as it has to wait for the response of the previous.!?!? Im running LV 8.6 on WinXP for this project and I didnt even think multicore processing for for loops is included in this version.
The other thing is... this script used to run fine on the dual core until I added the last part that uses a for loop to get every line of the graph to be the thinkness I need. Is this for loop the culprit? Can I stop it from executing over multiple cores/threads? I read a post saying that from diadem 8 there was multi core support. this triggered my doubt
As always any comments are most appreciated
AL
:. LV2010 SP1 ... W7 .:
Solved!
Go to Solution.

Hi Al,
I have a theory, but only you can test it. In your VI screenshot, you have the boolean input for the DIAdem Execute Script.vi set to asynchronous=TRUE. My theory says that if you change that boolean (and all others like it) to asynchrous=FALSE that the error will not occur on the multicore computer. The other thing you could try would be to consolidate all REPORT commands that pertain to one REPORT page into a single ActiveX call to DIAdem. In the screenshot below you have at least 2 separate VIs calling DIAdem, so that's at least 2 separate ActiveX calls for one REPORT sheet.
Here's what I think is going on. On a multicore computer there is the potential for different ActiveX commands from LV to DIAdem to execute on different cores, which may result in a timing problem on the DIAdem side. DIAdem 11.x and earlier runs exclusively on 1 CPU, so the incoming ActiveX commands should be sequenced correctly by DIAdem's ActiveX to-do list. Theoretically DIAdem should serialize all the incoming ActiveX commands (regardless of which CPU processed them) in the order that they arrived at the DIAdem ActiveX server(s). On the sending side, LabVIEW's dataflow execution should theoretically guarantee that all the ActiveX requests are being sent in the correct order. But it is theoretically possible that the operating system's ActiveX processing queue might not send all the ActiveX commands to DIAdem in the order that it receives them from LabVIEW-- IF YOU'VE SELECTED ASYNCHRONOUS PROCESSING.
See if these clues help,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

Can diadem run scripts in diadem

I have a script writtem in Diadem that uses config files to load the data and then add it to a report. It then exports the report in a pdf format. I would like to run this script with labview so I can automate this when new log files are created.I have used the report template VI but I have csv files not signal files plus I want to be able to export the reports automatically

Hi chandler,
Don't give up on me just because you've tried the DIAdem Report.vi before and it didn't do what you needed. Like I said, this example tricks the DIAdem Report.vi into doing things it wasn't designed to, like passing a CSV file path and calling a VBScript that can create a multipage report.
The "DIAdem Report Script.TDMS" file is not a data file but rather a parameter transfer file from LabVIEW to DIAdem. The DIAdem Report.vi does NOT have a data file path input, so this is how I'm tricking it into using one-- the VI writes all the info LabVIEW knows and the reporting DIAdem needs to know into this "DIAdem Report Script.TDMS" parameter transfer file. Then when the "DIAdem Report Script.VBS" file is called, the first thing it does is loads the "DIAdem Report Script.TDMS" file and reads off those transfer parameters. In this case what is being passed is just the file path of the data file-- in your case a CSV file.
The DIAdem Report.vi DOES have an input for a REPORT file path, and if you wire up a file path to a VBScript file to that VI input, it will launch DIAdem and run the VBScript you wired up. If that "DIAdem Report Script.VBS" then loads the "DIAdem Report Script.TDMS" file to read off the transfer parameters, then clears the Data Portal and loads the desired CSV data file (that was passed in the transfer parameter TDMS file), THEN calls your reporting VBScript with ScriptStart(), you should have what you want.
This is a non-obvious architecture, but it is robust,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

How can I use the Diadem FFT Analysis GUI to give me multiple outputs given multiple inputs?

I have a few hundred channels I would like to perform FFT analysis on. They are mostly of different lengths, but I know I will have groups of 7 that will have the same number of data points. The default GUI will accept those 7 sets since they are the same size, but it will only give me one output as a combination of the sets. Is there a way to get Diadem to give me an FFT output for each set without having to select each data set individually?

The way it worked with the default channels, I had to make sure I wasn't going crazy because the way you demonstrated worked very well for me. That being said, for some reason what I am doing does not work. I've recently found that it is in changing the details in the GUI that makes my output different than yours. The differences are as follows:
1) I do not use a time channel. That is always left blank.
2) in the 'Window Functions' tab, I change the window type to Hanning
3) In the 'FFT Functions' tab, only amplitude is checked with the properties 'Peak amplitude', No Third/Octave, and Average amplitude is changed to arithmatic.
4) In the 'Time Intervals' tab 'Length/Start/Overlap' is checked, Interval length is changed to 1024, and overlap (%) is changed to 50.
I've also found that changing any number of these details from the default will cause my proplem to crop up. I am fairly sure that most of those options are just as feasibly done to one channel as they are to multiple. Is this a bug, or am I misunderstanding a property of FFT that has gone over my head? Please try changing a few of those properties since it seems like it should work just as well for all the channels as it does for just one, but that doesn't seem to be the case.
Another point of confusion is that while the window previewing the inputs in the GUI will show all the inputs I have selected, the window previewing outputs only appears to preview a single unknown output. That is just a side note though.

How to use OLE to start a Diadem vbs Script, that starts the Measurement

Hi there,
i try to use OLE to start a Diadem Script that start my measurement. I always get the Error-Message "The Measurement can only be startet in the first instance". How can i make this work? At this time i use DDE to start my Scripts and i want to use OLE to get direct Channel Access and to prevent the lousy dde-timeouts.
IDIACommand = CreateObject("diadem.tocommand")
command="Scriptstart etc
IDIACommand.CmdExecuteASync(command)
Thanks
Diademi

Hello diademi!
Depending on a registry setting DIAdem will treat the interface creation in two different ways:
Starting always a new instance of DIAdem and connect to this
Start a new DIAdem if there is no DIAdem already running. Then connect to the started or the already running DIAdem
The second mode will be right for your use case. Have a look at the key 'HKEY_CLASSES_ROOT\CLSID\{285E4FB2-F633-11D1-85DC-008048D9A408}\StartParameter' in the registry. The value 'Intancing' defines the behavior. Search the DIAdem help to get the definition (don't use the help index, it is missing there!).
Matthias
Matthias Alleweldt
Project Engineer / Projektingenieur
Twigeater?

Run diadem and Script automatically with windows

It would be possible to give an exe or something like that, with windows and after execute this, DIAdem automatically run and when Diadem opened, run my script also automatically??
Thank you
Sara

Hi Sara,
You can absolutely run the DIAdem exe automatically from Windows, for example, as a startup executable, Windows Scheduled Task, or batch file.
Using DIAdem, if you want to automatically run a SCRIPT when the application opens, use the Start Script option under Settings » Options » General » Start Script.
If you want your users not to see DIAdem executing, there are a couple of approaches you could take, depending on your desired behavior and comfort with programming. For example, you could:
Call DIAdem programmatically using ActiveX from another language like LabVIEW and choose to hide the environment when running, or
Have DIAdem SCRIPT run a SUD dialog that masks the DIAdem screen and reports a simpler version of information updates to your user, or
Use DIAdem's customization abilities to programmatically hide all Panels and Toolbars, or
Use your script to programmatically switch the screen mode in DIAdem (try pressing Ctrl+U interactively!) while your script is executing.
Good luck!
Derrick S.
Product Manager
NI DIAdem
National Instruments

Anzeigeformat in Diadem 2010 SCRIPT ändern

Hallo,
ich benutze seit einigen Diadem-Versionen ein Script, in dem ich mit
Data.Root.ChannelGroups(1).Channels("Minuten").Properties("displaytype").Value = "numeric"
einen Kanal von Zeit auf Numerisch ändere.
In Diadem 2010 geht das nicht mehr und ich bekomme eine Fehlermeldung:
"Der Eigenschaft displaytype kann kein Wert vom Typ vbString zugewiesen werden."
Ich habe es auch mit
Data.Root.ChannelGroups(1).Channels("Minuten").Properties.Add("displaytype", "numeric")
versucht. Allerdings bekomme ich auch da eine Fehlermeldung:
"Beim Aufrufen einer Unterroutine dürfen keine Klammern verwendet werden."
Wie kann ich das Problem lösen?
Solved!
Go to Solution.

Hallo Ludwig72,
das konnte ich reproduzieren und es verhält sich nicht richtig. Ich habe einen entsprechenden Eintrag in die Fehlerdatenbank gemacht. Die Korrektur wird Bestandteil eines Service Pack bzw. der nächsten Version sein. Bis dahin hilft dir dein Work-Around.
Noch ein Hinweis: Wenn du öfter auf die Eigenschaften oder Einzelwerte des Kanals zugreifen möchstest würde ich mir ein Kanalobjekt anlegen - das ist insgesamt schneller. Beispiel für deinen Work-Around:
Dim oChn
set oChn = Data.Root.ChannelGroups(1).Channels("Minuten")
ChnFormat(oChn.Properties("number").Value) = "Numeric"
Gruß
Walter

DIAdem FFT delta-f

Hallo,
ich hatte bereits eine Frage zur FFT unter DIAdem:
http://forums.ni.com/ni/board/message?board.id=60&message.id=6962&query.id=66517#M6962
Darauf aufbauend:
Als Vergleichskriterium für verschiedene FFT wurde mir nun "delta-f" präsentiert.
Dies soll sein 1 / (N*delta-t) mit N = Anzahl der Stützstellen (Intervalllänge) und delta-t = Abstand zweier Abtastpunkte.
Weiterhin soll ja die Intervalllänge immer möglichst groß gewählt werden.
Wir sind bei unserem Messsystem auf bestimmte Abtastraten festgelegt, z.B. 200Hz, 500Hz, 1000Hz.
Die Intervallbreite, also Anzahl der Stützstellen, bei der FFT muss aber immer 2^N sein, also 512, 1024, 2048 etc...
Wenn ich nun 20 Sekunden messe, habe ich bei 500Hz 10.000 Messpunkte.
Die Intervallbreite muss mindestens 2 x in die Messdatei passen, also kann ich mit einer Intervallbreite von 2048 oder sogar 4096 arbeiten.
Ist diese Annahme richtig?
Dabei ist ja nur relevant, dass durch die Abtastrate und Messdauer eine für die gewünschte Intervallänge ausreichend lange Messdatei entsteht. Die Abtastrate muss nicht ebenfalls ein Vielfaches von 2^N sein, oder?
Welche negativen Effekte können entstehen, wenn die Abtastrate kein Vielfaches von 2^N ist, aber die Messung stets mehrere Sekunden läuft?
Danke,
Heiko

Hallo Heiko,
Die ein- und zweikanalige FFT in DIAdem kann in den neueren Versionen mit jeder beliebigen Anzahl von Stützstellen rechnen. Damit hat sich das Problem mit den Messzeiten erledigt.
Delta-f ist in der Tat sehr wichtig, wenn man Ergebnisse vergleicht. Wenn ein Signal konstant über einen längeren Zeitraum vorliegt, kann man leicht verschieden lange Intervalle messen und FFTs oder Übertragungsfrequenzgänge berechnen. Wenn man solche Ergebnisse vergleicht, wird man feststellen, dass Sinusartige Peaks immer etwa gleich groß bleiben, aber mit größerer Stützstellenzahl schmaler werden. Rauschartige Anteile werden dagegen mit steigender Stützstellenzahl kleiner.
Wenn das Signal unverändert vorliegt, kann man kann also durch möglichst lange Messzeiten eine bessere Trennung von Sinuspeaks und Rauschen erreichen. Wenn man aber an den Rauschanteilen interessiert ist, muß man die Stützstellenzahl unbedingt beachten oder die Funktion PSD (Power Spektrum Density) benutzen. Bei PSD wird durch delta-f dividiert. Nun haben Rauschanteile immer die richtige Größe, Peaks sind dann aber nicht mehr zu vergleichen. PSD ist z.B. für Vergleiche von Filtern oder Verstärkern geeignet, da die Frequenzgänge meist keine Peaks haben. Hier interessiert man sich z.B. besonders für den Verlauf der Rauschwerte.
mit freundlichen Grüßen
Ulrich Bierwisch

Problem in DIAdem DAC Script-processing

Se description and DAC-schema in attachments !
Regards
Henrik
Message Edited by Support on 02-20-2007 01:43 PM

Hi Henrik,
Currently we have no idea why this behavior occurs like you described. That's something we have to look into. But we have a workaround. You can use a separate clock block for each DAC script block. That works fine in our tests. Attached you find your modified example. I hope it can help you.
Greetings
Walter
Message Edited by Support on 02-20-2007 01:43 PM

Controlling dialog boxes in a DIAdem script from LabVIEW

I have a DIAdem script that prompts the user for the data file it will process. The datafile was created from a labview test routine. I can now run the script from LabVIEW using the "DIAdem Run Script.VI", but in the interest of automation, I would like to have LabVIEW place the filename in this dialog. I would like to keep the dialog in the script, since sometimes we run this script manually. (without LabVIEW)
Bill W.

Bill,
Which dialog are you using to prompt for the file name? It
appears that you cannot send any information to the script through the
Run Script.vi. However, you can call automation commands using
the "DIAdem Run Automation Command.vi". If you want to pass data
to the script, then you can set a Global Variable, or a DIAdem Script
Variable. As an example, you could use the global variable, T1,
and send "T1 := 'myfile'". When the script is executed, that
variable will be accessible within the script and it will be set to
"myfile". You could also set the FileDlgName variable to your
file name. Then it may be possible to send those variables to
your dialog so that they are automatically populated.
Good Luck!
Tyler Tigue
NI

Script aus Labview an Diadem übergeben

Guten morgen zusammen,
ich möchte aus LV raus die Datenauswertung automatisieren, mein erstes
Problem ist, dass Diadem das Script von LV übergeben so nicht
akzeptiert, wenn ich es aber in DiademSCRIPT kopiere oder in einer
Script Datei übergebe, läuft es ohne Probleme.
Ich erzeuge in dem Script weitere Känale und möchte diese in LV
weiterverwerten, wenn ich aber das "Import-Channel" VI nutze bekomme
ich keine Daten zurück, egal ob ich den Kanalnamen z.B. Mean oder die
Nummer 17 verwende.
Was mache ich da falsch und wo kann man ein Manual dazu finden, wie es richtig geht?!
Gruss
N.Schnitzler
Solved!
Go to Solution.
Attachments:
DiademScript.JPG ‏126 KB

Hallo N. Schnitzler,
Die DIAdem ActiveX Schnitttelle arbeitet immer noch mit Autosequenz Syntax, also eben NICHT mit VBScript Syntax. Waere es Moeglich, von LabVIEW aus das VBScript zusammenzubasteln, danach an eine VBS Datei zu speichern, dann das eine Befehl "ScriptStart('Pfad\Script.VBS')" an DIAdem von LabVIEW aus (durch ActiveX) zu richten?
Brad Turpin
DIAdem Product Support Engineer
National Instruments

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."

How can I find outliers in a DIAdem report using LabVIEW

I am new to DIAdem and I am trying to take a DIAdem report and find the outliers and mark them with an 'X'. I found an example of this but it uses a VB script. The example has a constant to determine what is an outlier. I need this to be a variable. Thanks for the help in advance.
AJL

Hello AJL,
an easy way to realize your task would be to use the VBS script you allready found.
You can call a VBS with the "Diadem run script.vi". Inside the VBS, just locate the parameter you want to change and replace it with one of the DIadem Variables (for a realvalue you could use R1 for instance). You do not need to declare those internal variables initially, they are part of DIAdem and free for everybody to use. Just make sure it is not used a second time in the script you are calling. Then, prior to running the script you just have to set the respecting variable with the "DIAdem variable set.vi". This allows you to change DIAdem command parameters from your LabVIEW vi.
Both VIs I mentioned above are part of the LabVIEW DIAdem Toolkit. In case you don't have it yet, you can download the functions at
http://digital.ni.com/softlib.nsf/websearch/5121C7F322C9392886256EDF005BB4FF?opendocument&node=132070_US
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany

Diadem Sequence File Name?

Is there a command/variable in Diadem VBS Script that I can use to get the name of the sequence file I am running? This is needed so I can display the VBS script version/script name on the DiaDem Graph so I know what sequence was used to crunch the numbers.
Thanks, Jeff

Hi Jeff,
The name and path of the script file currently running is stored in the variable AutoActFile.
Maybe you need the program revision of DIAdem too: ProgramRevision.
Greetings
Walter

Mathematical functions in Diadem

Can someone tell me how I simply add two channel properties together in Diadem VB script.
Or if I can calculate a new value by adding a variable to a channel property.
The output from the addition I would like to put back into a new Channel Property.
This code does not seem to work.
msgbox ChnPropValGet(1, "maximum") + ChnPropValGet(2, "maximum")
Thanks

You are correct - it looks like ChnPropValGet only shows up in DIAdem 10.1. I use different versions of DIAdem, so often re-create the new functions that I enjoy and register them as a user command (using ScriptCmdAdd). I think something like the function below should give you somewhat similar results. And yes, you should be able to put this value into a channel property by using the ChnPropSet command, and perhaps the ChnPropCreate command, if you want to create a new property. For example, the bit between the dashed lines saves the sum of the maximum values to the variable, "MaxSumVal" and then creates a property for channel #5 called "MaxSum" and sets this value to MaxSumVal. But you could also put the value in an already-created property, but some excisting channel properties are read-only. I hope this is not confusing!
MaxSumVal = ChnPropValGet(4, "maximum") + ChnPropValGet(3, "maximum")
Call ChnPropCreate(5, "MaxSum", DataTypeFloat64)
Call ChnPropSet(5, "MaxSum", MaxSumVal)
Call ChnPropSet(5, "Description", MaxSumVal)
Public Function ChnPropValGet(ChnNum, ChnProperty)
Dim ChanType
ChanType = ChnPropGet(ChnNum, "displaytype")
Select Case ChanType
    Case "Numeric" ChnPropValGet = Val(ChnPropGet(ChnNum, ChnProperty))
    Case "Text"     ChnPropValGet = ChnPropGet(ChnNum, ChnProperty)
    Case "Time"     ChnPropValGet = ChnPropGet(ChnNum, ChnProperty)
    Case Else       ChnPropValGet = ""
End Select
End Function ' ChnPropValGet

Diadem FFT script

Similar Messages

Maybe you are looking for