Udi autosequence diadem 9.1

Hi
Updating from Diadem 7 .1 to 9.1 with DAC bundle (because 7 does not work with windows xp) I was expecting that my old autosequences would still work and that I would not have to convert them to the .vbs format.
However when attempting to run my auto sequence I get the message 'Undefined Command - UDIOpen('COM', 'COM1')' .
If I convert to vbs, the UDI parts just have question marks inserted in front of them - the only reference in the help files is to tell you to look on the internet.
Is this function no longer supported in autosequences, if not, where are the help files and examples of the new method - all I can find is a pdf document on the web site.
Version 9.1 does not seem to have much in the way of examples at all, to find an example of error handling I had to download a demo of version 10.
The version 9.1 example of error handling uses the instruction 'autoignoreerror' but then in another place says that it is no longer supported.
It was bad enough in version 7 when I had to convert help files from german to english using a translation program to get information on the UDI now it is not mentioned at all.
What goes on ?

Hi Nick H,
DIAdem, from version 8.1->9 started moving more towards VBS rather than AUT, and this trend has continued and will continue for all later versions.
We still provide an AUT script reader, and a utility to convert AUT to VBS, however as you have found this is not a perfect process.
I have done an internal search for UDIOpen and have found some results for you.
The file GFSSTD2.DLL which contains the UDI functionality is not registered. To register it close all DIAdem windows, go to Menu --> Settings --> GPI-DLL Registration and add the DLL which is stored in the DIAdem main directory. Because of TLS (Thread local Storage) problems in Windows and because this UDI commands are based on an old technology we didn't register the GFSSTD2.DLL by default. IN VBS it is better to use the UDI object.
So in DIAdem 9.1 you need to close down the navigator and then go to Settings >> GPI-DLL
Click "Add" go up one level in the windows dialog box and select GFSSTD2.dll click OK and then close out of the GPI-DLL window DIAdem will ask you to save click yes and restart DIAdem.
You can also add this functionality in DIAdem 10.
Close all windows (Navigator will stay open)
Go to Settings >> Options >> Extensions >> GPI Extensions
Click "Add" go up one level in the windows dialog box and select GFSSTD2.dll click OK and then close out of the GPI Extenstions window DIAdem will ask you to save click yes and restart DIAdem.
Hope this will help you run your AUT files.
Regards
JamesC
Applications Engineer
NIUK & Ireland

Similar Messages

GPIB driver for NEC omniace RA1100

Hello,
I want to control a NEC datalogger omniace II RA1100 via GPIB. Does anybody know where I can get the LabView driver for this instrument?
I didn't find them neither on ni.com nor at the NEC website.
Many thanks in advance,
Magnus

Hallo Jens,
kann es sein, dass die Schnittstellenparameter nicht gesetzt sind? Die Parameter für die Schnittstellen werden in der Datei GfSUDI.UDI im DIAdem Programmverzeichnis verwaltet. Falls die Datei nicht existiert, kann die im Attachment vorhandene UDI-Datei in das Diadem Programmverzeichnis kopiert werden. Die Adresse und der Kartentyp müssen mit der Karteneinstellung übereinstimmen.
Ich hoffe das hilft weiter.
Gruß
Walter
Attachments:
GfSUDI.zip ‏1 KB

Frequenz Analyser 1250 Solartron

Ich möchte mit Diadem 8.1 den Analyser 1250 von Solartron steuern und Daten auslesen. Ich habe eine GBIP-Karte von NI im Rechner und kann über den Measurement Explorer den Analyser ansprechen. Wie kann ich über Autosequenzen von Diadem aus das Gerät ansprechen?

Gerätesteuerung kann in DIAdem mittels der UDI Schnittstelle erfolgen.
Diese Schnittstelle besteht aus einem ActiveX Objekt, welches entweder
im Modul DAC in einem Script DAC Block aufgerufen wird oder direkt aus
einem VBS. Erstellt wurde die Schnittstelle für ersteren Fall, daher
wird auch nur dieser in der Dokumentation beschrieben.
Universal Device Interface (UDI) in DIAdem DAC
Die Befehle, welche zum Gerät gecshickt werden müssen, um es zu
konfigurieren und Daten abzuholen können Sie dessen Beschreibung
entnehmen.
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany

How do I create a subaxis in DIAdem GRAPH using an autosequence?

I am creating graphs in DIAdem REPORT using an Autosequence (3 graphs and text). This is to prevent anyone from changing the format of the report, which is why I am not simply loading an existing layout. My question is how do you add a sub-axis to a 2d Axis system? I can tell the curves in the axis-system that they belong to subaxis 2, but the subaxis doesn't exist so the curve is not displayed.
How do I create the new subaxis?
Thanks, Jeff

Hi Jeff,
Unfortunately this is a gap in our function set for GRAPH objects. I have been told by the developers that there is no VBScript-level function to create a Y axis programmatically. Your only option as far as I know is to have several copies of the same report layout saved off with different numbers of Y axes. As you accurately pointed out, once the Y axis exists, you can programmatically associate various curves with it or edit its properties.
Sorry for the bad news,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

Error Occuring While Processing Data With DIAdem 8.1Exception EAccessViolation in module ntdll.dll at 000111DE. Access violation at address 7C9111DE in module 'ntdll.dll". Read address 37363430

Hello,
We are having an issue running Diadem 8.1 on a new HP XW 9400 with Windows XP SP2. 3 errors have been occuring with frequent crashes, they are:
1) "1Exception EAccessViolation in module ntdll.dll at 000111DE. Access violation at address 7C9111DE in module 'ntdll.dll". Read address 37363430.
2) The instruction at "0x7c9111de" referenced memory at "0x352e302d". The memory could not be "read".
3) ---Error--- DIAdem
Error in Autosequence - processing in line: 74 (IARV_VAR_GET)
Runtime Error while executing command "Iarv2Txt$ := FR(T9,L1)"
Error type: ACCESS VIOLATION
Error address: 000101DE
Module name:ntdll.dll
We are using the same scripts and version 8.1 on a variety of Dell desktop computers (W2K and XP SP2) without any issue, looking for suggestions as this affects no other software on the HP XW 9400 other than DIAdem. Appreciate any suggestions.
Message Edited by swillh on 06-25-2007 08:55 AM

Christian,
I will answer your questions in the text below. Thanks for your help.
Hi swillh,
I also would like to help you.
Unfortunately, The reported access violation in the central Windows ntdll.dll is very unspecific.
May be the following questions will help you to provide me more info.
1. You mentioned that the aut's and - I think - also the accessed text file reside on a server.
Is there a stable network connection?
The server can sometimes be a little slow but the connection is good. This computer is using the same connection that the prior computer utilized without issue.
Are the files accessed by multiple clients simultaneously?
It is possible that more than one computer can be accessing the same file, but again, this has never been an issue. We are reading the files only, not writing to them.
The processing routines we are running have used for over 5 years without any issues until adding this computer.
Is the text file read by one client while another client is writing the same file?
No, files are "read only"
2. Have you already tested opening the file with the FileOpen command before calling FR?
Yes
Do you see any chance to convert the aut to a vbs file? This gives you more alternatives in accessing text files.
3. What do you mean with "processing ATD's with 30 or more channels of data"? Where is the relation between ATD files and data channels?
Processing Crash Dummy data with file sets low in channel count (15 channels) result in successful processing without any crashes or access errors. When processing dummies with more than 20 channels we sometimes encounter these issues. The higher channel count may be the only common factor I can find in these faults.
Steve
Message Edited by swillh on 07-09-2007 08:44 AM

Is Full Automation Possible In DIAdem V9.1?

Hi all
I wonder if i can fully automate my DIAdem V9.1 application.
Here's what i have at the moment:
From time to time a wIndows application writes a new datafile containing ASCII data to the PC's harddrive.
The files are named 00001-Date.daf, 00002-Date.daf, 00003-Date.daf... and so on.
The .daf file is nothing exotic, it's simply an ASCCI file containig data for two channels. I use the extension .daf only
to get a unique file extension.
Then i doubleclick on the DIAdem icon.
I have modified the destination path of the icon in this way:
"C:\Programme\National Instruments\DIAdem 9.1\DIADEM.exe" "/CScriptStart('"E:\DIAdemWork\Manni01.vbs"')"
DIAdem starts, and runs the Manni01.vbs script.
The script will open a FileNameGet dialogue, and the user has to select one of the .daf files.
The selected .daf file will automatically be imported, displayed and analysed.
This works fine, but, as you see, the user has to select the file to be imported.
Since this has to be done inside DIAdem, it cannot be automated further.
It would be much nicer, if the name of the file to be processed could be transferred to DIAdem as
a program start parameter, similar to the name of the starting script.
The other application could then start DIAdem with this filename as a parameter. DIAdem could
process the datafile and NO user interaction would be required to select the file.
As a nice side-effect, a simple double-click on a .daf file in windows explorer could also open
DIAdem and automatically process the data.
How can i transfer a filename to DIAdem at startup?
Note: The filename must be recognizable in the autostart script, and there must be a way
to examine IF a file was given as a parameter.
Manfred

Hi Manfred,
Here are a couple of hacks you might be able to put together to get to where you are trying to get: First it is possible to hack the registry to start the program you want to start when a file with a given extension is double clicked from the explorer. Second it is possible to set a variable in DIAdem from the comand line.
Hacking the registry (You should only do this if you really know what you're doing. Just playing around could really mess up your system.)
1.) Open regedit.
2.) Go to HKEY_CLASSES_ROOT and create a key called ".daf". Set its value to anything you want -- I suggest "daffile"
3.) Also in HKEY_CLASSES_ROOT create a key called "daffile" (or whatever you chose in step 2 for the value).
4.) In the new daffile key create a key called "shell".
5.) In the new shell key create a key called "Open" (or whatever you want). The name of this key will be used by explorer in the context menu item for files of this type.
6.) In the new Open key create a key called "command".
7.) Set the value of this key "command" to the startup command for DIAdem. Using the start up string you suggested below, this would be "C:\Programme\National Instruments\DIAdem 9.1\DIADEM.exe" "/CScriptStart('"E:\DIAdemWork\Manni01.vbs"')"
In the command key, %1 can be used to represent the file that was clicked. You could theoretically set a DIAdem variable to the file name using this fact. The command line argument would probably look something like /CT1:=%1. (in the old AUT autosequence syntax.) Then you can access the variable that you set using this in your script. I haven't tried the command line out, so you'll probably have to tweak it a bit. I'm pretty sure you can send two commands in the command line.
The drawback to this approach is that it will probably always start a new DIAdem and not open your file in a DIAdem which is already open.
Hope that helps,
Myrle
P.S. Have you considered writing a VBS DataPlugin to read your file format? Simple ASCII files are usually dead easy to write DataPlugins for. Then you could use the file system inside of DIAdem to browse, and drag and drop from the Navigator into the Portal would automatically work. The documentation for the DataPlugin API can be found here: http://www.ni.com/diadem/dataplugins.htm
For tips and tricks on creating VBScript DataPlugins go to http://dataplugins.blogspot.com.

VIEW in diadem 9.1

Hi
Is it possible to use VIEW programatically in the old .aut language in diadem 9.1, I've tried using record mode but this just seems to record the .vbs code which won't work as an aut file. There is nothing in the help files regarding this.
I would normally convert to .vbs but this is a minor change to an old autosequence and I want to avoid having to go through a lengthy re-validation process if convert everything to vbs.
Any help appreciated
Nick

Hello Nick!
As I know it is not possible to script the object orientated new VIEW interface out of AUT scripts.
A solution to your problem might be to insert the VBS Code inline in your AUT. This is possible with the command 'ScriptStatement'.
E.g. ScriptStatement('MsgBox(now)') will show a VBS MessageBox with the current time. You can insert your VIEW manipulating script line by line in your AUT with this command. Not really good to read but I think it will work.
Hint: The strings have to be enclosed in ' because in the VBS code you must use "!
Matthias
Matthias Alleweldt
Project Engineer / Projektingenieur
Twigeater?

Generating a data channel in Diadem 6.0

I would like to generate a data channel to represent a x/y curve. e.g.:
x: 0.1/0.2/0.3/0.5/0.9
y: 1/3/10/11.5/15
How can i do this and how can i use these datas in different autosequences?
The next question is: how can i control with these datas an analog output?

Hi,
If the values you would like to generate are equidistant or can be build with a mathematical algorithm you can use a lot of different DIAdem functions like CHNGENVAL, CHNSPLINEXYCALC, CHNMAPLINCALC etc.. But in your case I can't see something like this, so you must set each value in the channel (see example below)
ChnAlloc('TestChannel', 5);
chd(1, 'TestChannel') := 0.3;
chd(2, 'TestChannel') := 1.2;
chd(3, 'TestChannel') := 2.8;
chd(4, 'TestChannel') := 3.3;
chd(5, 'TestChannel') := 3.7;
To use this in different Autosequences store it as a separate file and call it with the command AutoInclude.
With the Block DAC->Simulation inputs->Channels you can read any DIAdem channel and use it to set the output values.
I hope this will help you a little b
it.
Greetings
Walter

Saving subblock diagrams in Autosequences

How can I export a subblock diagram in the *.sub-format in an autosequence?
I've used the SCHEMEEXPORT command, but it saves the whole of the DAC plan and not just the subblock.

Greetings "th",
The SchemeExport command in DIAdem will indeed save only the HIGLIGHTED subset of your DAC block diagram, but if you have not manually selected a section of your code with your mouse, then it defaults to saving the entire block diagram.
Every single action or state of the DIAdem environment has a corresponding variable or autosequence command which can be accessed programmatically. This is one of those cases where the command is very unlikely to be useful in an autosequence, since it was specifically intended for interactive execution. The one case where I could imagine this still working, is if you released the user to the DIAdem DAC window in InterationON mode. Then the user could select a region of the DAC block diagram and press the I
nteractionOFF button to allow the autosequence to continue.

Labview-diadem empty report, please help

Hi,
I'm running labview 8.0 vi that calls a report made with Diadem 10.0.
I use the Diadem Report control to invoke the Diadem Report, passing channels and some texts as parameter.
Really my vi works,..., but if i make an executable file, the report appears but without the channels data nor texts.
Any idea ?. It's possible that the SP1 for Diadem solves the problem ?
Thanks a lot.

LabVIEW comes with several DIAdem autosequences and built-in layouts
that are used by the Express VI. In a LabVIEW development system, they
are located in .vi.lib\Platform\express. In a built application, the
autosequences (*.vbs) are expected to be in the same path as the
LabVIEW-built EXE file. If you are using built-in layouts (which I
understand you don't), these layouts would be expected in a subpath
called .\templates.
The problem here is that LabVIEW does not automatically include the
autosequences and/or layouts with source distributions, built
executables, installers and such. You should be fine after manually
adding these files to your build specification:
.\vi.lib\Platform\express\PicExport.vbs
.\vi.lib\Platform\express\UpdateGraph.vbs
Hope that helps,
Herbert

DataSetComments in DIAdem Report 8.1 vs 9.1

We are migrating from DIAdem 8.1 to 9.1 and are a bit confused about "DataSetComments".
In 8.1 we use an autosequence in DAC to feed DataSetComments in a standardized way for every measurement. In the Report template (*.LPD) the DataSetComments is viewed for each DataSet (= *.DAT-file !)
In DIAdem 9.1 this 1-to-1 relationship between DataFile and DataSetComments seem to be changed ?! (DataSets now include 1..many Files/Groups)
How to re-use our "File-based" DataSetComments in DIAdem Report 9.1 (*.TDR) ?
Best regards
Henrik

After some more Trial-and-Error I found that it works as expected if/when Data Portal is Empty when the DAT-file is opened, then the DataSetComments is set from the file as in 8.1.
Obviously I had some Channels already in the Data Portal when my DAT-file was opened before, then the DataSetComments from the DAT-file is not available. Lesson learned !
I tried the DataSetGroupCopy command anyway, and then I had new problems.
Check Attachment for details ...
Regards
Henrik
Attachments:
2005-04-13 DataSetGroupCopy.doc ‏752 KB

Does diadem 8.1 support serial communication at a baud rate of 115200?

Same question in English.
Regards

Hallo,
das ganze geht mit dem Script-Dac Treiber und der UDI Schnittstelle. In DIAdem 8.1 muss eine dll (gfsvbsdr.dll) registriert werden, damit der Script-DAC Treiber dann verwendet werden kann. Dort lässt sich dann im Script die Baudrate programmatisch verändern. Hilfe und eine Beschreibung dazu finden Sie unter:
http://digital.ni.com/public.nsf/websearch/BEF723E4698914DA86256FD30053397F?OpenDocument
MFG
Rebecca Fox
National Instruments, Germany
Rebecca Fox
Applications Engineer
National Instruments

Input ascii file to diadem with ascii-import filter

Hello,
i want to import an ascii-file to diadem7.02 and want to save it as an .DAT-File.
i do this with Fileload and with the ascii-import filter. My problem is, when i want to record a autosequence, and i open the ascii-import filter und push the Ctrl-A key, it doesn´t record this window in the autosequence.
Is this unpossible in DIAdem or have anyone a solution for it.

Thank you Brad for your help,
but this solution is only for Diadem 8 and i have version 7.02.
I have hardly experience in Diadem 8 and nothing in vbs-programming so i had to solve this problem in Diadem 7.
Attachments:
BZE_fb2_001_3.zip ‏1 KB
asciidef.stp ‏1 KB

"Diadem command line control"

I have a report format that I wish to use many times with different data files. Does diadem support command line arguements so that i can startup diadem and pass it the report format and data file names i want it to use.

Hi GRD,
You can indeed start DIAdem with parameters, which Otmar is quite right in saying are usually built into a Windows shortcut, though you can just as easily issue them from the command line. The most useful of these is the "/c" parameter to run a DIAdem command immediately after launching DIAdem. If you have all your commands built into a VBScript, you can run all of them with a single parameter by referencing the VBScript, as follows:
diadem "/cScriptStart('VBScriptPath')"
The extra "" quotation characters surrounding the /c parameter enable your path to have spaces in it (i.e. 'Program Files'). If you do not have your commands in a single VBScript, you can queue up multiple /c parameters to be run sequentially after DIAdem start up.
Note that the syntax for these command parameters follows the old "autosequence" syntax from DIAdem 7 and prior versions, for example, the "/cScriptStart('VBScriptPath') command uses '' quotation characters and has no "Call" statement.
For the specific case of wanting to load a data file and a report layout file into DIAdem 9.1 just after launching it, use the following parameters:
diadem "/cDataFileLoad('DataFilePath')" "/cPicLoad('ReportLayoutPath')" /cPicUpdate
Note that if your path starts with the standard DIAdem path that you can use the "." character to quickly communicate this fact. If, for instance, your files were in the DIAdem user directory, you would use the following parameters:
diadem "/cDataFileLoad('.\user\dat\DataFileName')" "/cPicLoad('.\user\gra\ReportLayoutName')" /cPicLoad
Hope this helps,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

Probleme beim Initialisieren des UDI Objekts

Ein schönen guten Tag,
ich habe seid 3 Tagen schon das Problem, dass ich kein UDI Objekt initialisieren kann. Denn beim Starten des Scripts kommt jedesmal dieser Fehler, obwohl ich schon alles mögliche ausprobiert habe (aus Hilfe, Board und E-Book "Script-DAC-Treiber Beschreibung"). Also zur Erklärung: Will einen GPS Empfänger (VBox) über Seriellem Anschluss in DIAdem View anzeigen lassen und beim Initialisieren des UDI Objekts tritt halt dieses hier auf.
Zu dieser Zeile:
Set objUDIM = CreateObject( "DIAdem.SFD.UDI" )
kommt jedesmal dieser Fehler:
Fehler: UDI: Es ist ein nicht näher spezifizierter Fehler aufgetreten.
(Die Variable wurde auch vorher artig mit Dim angelegt)
Also ich versteh nur noch Bahnhof. Da in allen Hilfen und E-Books immer eine ähnliche Version des Anlegen eines neuen Objektes zu finden ist, würde ich mich um Hilfe sehr freuen. Habe auch schon überlegt ob es an der Evaluation Version liegen kann, die jedoch noch 19Tage Testdauer hat. Also würde mich über jeden Tipp freuen.

Hallo RainerH,
ich denke nicht, dass es daran liegen kann. Denn hab vorhin das auch mal mit einem Excel Objekt oder DiademToCommand Objekt probiert. Wollte wissen ob die wenigstens gehen. Aber leider Fehlanzeige, bei diesen beiden Sachen kam dummerweise genau der gleiche Fehler. Also vermute ich das dort beim anlegen irgendetwas nicht funktioniert. Aber werde nochmal alles durchstöbern ob vielleicht doch schon etwas die Schnittstelle belegt.
Und erstmal danke für den Tipp, vielleicht werd ich ja doch noch fündig.

Udi autosequence diadem 9.1

Similar Messages

Maybe you are looking for