DIAdem 2017 SP1 32-Bit Release Notes


Version 17.0.1

November 2017

This file contains information on DIAdem 2017 SP1:


System Requirements

Supported Operating Systems

Notes on DIAdem 2017

Compatibility of DIAdem 2017 and DIAdem 2015

Product Security and Critical Updates

New Features in DIAdem 2017

Availability of the 32-Bit Version of DIAdem

Availability of the Old REPORT Script Interface

Bug Fixes

Accessing the Help

Finding Examples

Automating the Installation of NI Products

Using NI Software with Microsoft Windows 10

Using NI Software with Microsoft Windows 8.1

Legal Information


DIAdem is the National Instruments software for analyzing and documenting data from various sources.

System Requirements

For correct DIAdem performance, the following minimum requirements must be met:


CPU x86 compatible processor, 1.6 GHz or more
Amount of memory 2 GB or more
Hard disk memory Depending on the operating system, up to 2.8 GB free storage space, of which at least 1.8 GB on the system partition
Video card Color depth at least 16-bit (High Color), 24-bit, or 32-bit (True Color) recommended
Screen resolution From 1024x768 with a 100% scaling step

Supported Operating Systems

  • Windows 10 Build 1604 32 or 64-bit (as 32-bit application)1

  • Windows 8.1 Update 1 32 or 64-bit (as 32-bit application)1
  • Windows 7 32-bit or 64-bit with Service Pack 1 (as 32-bit application)2
  • Windows Server 2012 R2 Update (as 32-bit application)1

  • Windows Server 2008 R2 64-bit with Service Pack 1 (as 32-bit application)2

With this release, DIAdem 2017 drops support for Microsoft Windows 7 RTM (with no service pack), Windows Vista, Windows XP, and Windows Server 2003. DIAdem 2017 and later will not install or run on an unsupported OS. You cannot deploy or distribute applications that use DIAdem 2017 to an unsupported OS. Additionally, after installing DIAdem 2017, you cannot use any installers built on this computer with any version of LabVIEW, LabWindows™/CVI™, NI TestStand™, or Measurement Studio on an unsupported OS.

For more information about the changes to our OS support for 2016, refer to KB 79UC78LS, Why Does my LabVIEW, LabWindows/CVI, Measurement Studio, or TestStand Built Installer Fail on Windows XP/Vista and Server 2003?.

1 NI software installs VC2015 runtime and .NET 4.6.2. Windows 8.1 and Windows Server 2012 R2, require Microsoft updates to support these items. Refer to Microsoft KB2919442 and KB2919355 for more information about how to install these updates.

2 NI software is signed with an SHA-256 certificate. Windows 7 SP1, Windows Embedded Standard 7 SP1, and Windows Server 2008 R2 SP1 require Microsoft updates to suport SHA-256. Refer to Microsoft KB3033929 for more infromation about how to install this security update.

Note  DIAdem runs only with restrictions on the N or KN edition of Windows because the multimedia support is missing. You can obtain this as "Media Feature Pack" from Microsoft and install it later.
Under Windows Server 2012 R2 64-bit you cannot play videos in DIAdem VIEW.


Firewall The firewall displays warnings while DIAdem installs and while DIAdem launches, for the following reasons:
The usireg component executes during the installation of DataPlugins. The DataFinder, which you use for searching and navigating in files, then starts. When DIAdem launches, a DNS query determines whether to license locally or whether to use a license server.

If you want to be able to use all the DIAdem functions, National Instruments recommends that you select "Do not block" for all programs listed. This also applies when you want to evaluate DIAdem. Refer to ni.com/info under the info code winxpsp2.

Windows User Rights DIAdem and its components are basically executable under the preconfigured Microsoft Windows user accounts from User upwards. DIAdem must be installed with complete administrator rights.

If you operate various DIAdem versions on one computer, you only have the entire range of functions in each version if you have administrator rights.


  • Internet Explorer from Version 11
  • If you want to display maps in the panels VIEW and VISUAL with Microsoft MapPoint, you must install MS MapPoint version 2010 and later.
  • Recommended:
    - Adobe Reader to display manual files

Notes on DIAdem 2017 SP1

  • If you register a type library in the 32-bit DIAdem SCRIPT version through Script»Type Libraries and specify the associated automation object with the Set statement and the CreateObject function in the script, DIAdem might crash during the autocompletion of the associated objects.
  • As of version 2017, SP1 DIAdem only supports PowerPoint export into the PPTX format and no longer the PPT format. You must convert existing PPT templates into the PPTX format. It is no longer necessary to install PowerPoint for exporting into the PPTX format.

Notes on DIAdem 2017

  • A 32-bit DIAdem 2017 version can be installed in addition to a possible DIAdem 2017 64-bit version and does not influence the 64-bit version. You can execute both versions at the same time and uninstall them separately. However, you cannot drag and drop data channels between the versions or exchange data channels through the clipboard.
  • DIAdem Version 9.0 and LabVIEW Version 7.1, and later versions, use a shared software component that is updated when you install DIAdem. When you uninstall DIAdem, the current version of the shared component remains. This is intentional and has been tested extensively.
    The installation functions were tested parallel to earlier DIAdem versions down to DIAdem 11.0.
  • For the DataFinder in DIAdem 2017, any index files from earlier DIAdem versions must be regenerated. This occurs automatically when you launch DIAdem. Depending on how many files are to be indexed, this may take quite some time.
  • Under Windows 7 or Windows Server 2008 R2, there are issues displaying character strings when printing or exporting to PDF and XPS documents if you control the system via remote desktop. DIAdem prints character strings without or with too little character spacing. This is a Microsoft issue described at http://support.microsoft.com/kb/2768741. There Microsoft offers a solution in form of a hotfix. In case you cannot install this hotfix, you can also work around this issue using the setting Output print data as graphic under Settings»DIAdem Settings»REPORT.
  • It is strongly recommended that you install in the suggested folders, or that you specify the folder exclusively in the path selection dialog box in the setup program. In particular, changing the suggested program path manually in the installation program can cause problems in DIAdem.
  • If you change the size of the text displayed on the screen (DPI scale), for example, from 100% to 150%, under Windows 8.1 (minimum) and you do not restart the computer, display errors might occur in the curve selection in DIAdem REPORT and DIAdem VIEW.
  • When you activate DIAdem, you must create a National Instruments user profile at ni.com. The evaluation period is now 7 days without a user profile. If you create a user profile, this period is extended by 45 days.
  • When loading a DAC block diagram, DIAdem now checks whether the block diagram contains outdated blocks. The block diagram can still run with these blocks, however the outdated blocks are identified with a label. Please replace these by up-to-date blocks because in future versions the earlier blocks will no longer be supported.
  • In order to use the following DIAdem drivers the following NI software components must be installed:
    Driver Components Version
    ADCS Automotive Diagnostic Command Set >= 1.1.1
    DAQmx driver NI-DAQmx >= 9.4
    ECU MC ECU Measurement and Calibration Toolkit >= 2.3.1
    XNET NI-XNET >= 1.3.0
  • The map display in the VIEW and VISUAL panels supports the Microsoft software MapPoint 2010 and later. Microsoft has announced it will discontinue the development and sales of MapPoint by December 31, 2014, which may result in MapPoint not working in future DIAdem versions.
  • The operating systems Windows XP, Windows Vista, and Windows Server 2003 are no longer supported. This results in the following changes:
    • The file Insight.DLL is no longer supplied.
    • Only the IEC card type NI-488.2 is supported.
    • Soft timing is no longer supported. Any block diagrams with soft timing are converted to automatic timing when they are opened.
    • The Spider8 driver no longer supports the LPT1 and LPT2 interfaces.
    • The IEC Bus Interface dialog box was removed [DAC>>Settings>>Single Point Processing>>Interfaces>>IEC-Bus…].
    • The measurement driver types Mode 1 (high speed), Mode 2 (DMA), and Mode 3 (Disk) are no longer on offer in the dialog box of the System Clock block.
  • The menu item "File - Open as VBS DataPlugin..." in DIAem SCRIPT has been removed. The extension VBSD is now applied to new DataPlugins. You can load existing VBS DataPlugins as VBS file and switch to "VBS DataPlugin Syntax" in the menu "File - Change Syntax". When you save the DataPlugin, use the file type VBS DataPlugin (*.VBSD).
  • As of DIAdem 2019, the methods and properties of DataFinderSettings (returned from Navigator.ConnectDataFinder("").GetSettings), including all subobjects, will be supported for My DataFinder only. For DataFinder Server, you must use the DataFinderManager API.
  • DIAdem 2017 is the last version to support the old REPORT script interface. DIAdem 2017 is also the last version available in 32-bit. For more information, please refer to the respective sections in these Release Notes.

  • Very old commands and variables, which have been replaced by new technologies, are marked as obsolete in DIAdem. This means that these commands and variables are no longer supported in one of the upcoming DIAdem versions. On the DIAdem help page DIAdem»Searching for Obsolete Commands and Variables you can find a script which checks your scripts for obsolete identifiers.

Compatibility of DIAdem 2017 and DIAdem 2015

To find information on the compatibility of earlier DIAdem versions refer to ni.com/support under the search term "DIAdem Release Notes".

  • After deleting several channels from the Data Portal interactively or deleting the channels with the Remove for Data method, DIAdem reissues the channel numbers to optimize speed. If you use channel numbers in scripts, you may need to adapt them.
  • As of DIAdem 2017, ANALYSIS functions that used channel numbers in the Description channel property in DIAdem 2015 and earlier versions now use channel names instead.
  • As of DIAdem 2017, ANALYSIS functions generate the result properties at the channels with new names to support the grouping of properties in the Data Portal. The following rules apply:
    • Existing property names are preserved when loading data.
    • ANALYSIS functions only create new property names as of DIAdem 2017. In doing so, DIAdem replaces the corresponding existing property names from earlier DIAdem versions.
    • Scripts and REPORT layouts remain compatible, because as of DIAdem 2017 you can access the properties with the new and the old property names.
    • In order to access the new property names in DIAdem scripts or layouts prior to DIAdem 2017, you must adapt the names in the earlier DIAdem versions.
    • You can find a comparison of the old and the new property names in the help chapter Basics»General»Basic Information»Result Properties as of DIAdem 2017.
  • If you use the ImportAction = "Load" request in scripts, you must change the request as follows: (1 <> InStr(1, ImportAction, "Load", vbTextCompare))
  • With identical configuration, the ReturnType property returned different values for the search without interface to those of a search with interface. As of DIAdem 2017, the ReturnType property only returns one of the following terms: eSearchFile, eSearchChannelGroup, or eSearchChannel. Earlier DIAdem versions may return a different value for the ReturnType property than the above mentioned values. If you use the earlier values of the ReturnType property in scripts, you must replace these values. Replace the deviating values with eSearchFile and remove superfluous text parent and parent.parent from the returned paths of the GetPath method.
  • The LVDataLoad command is no longer available. Use the LVM Dataplugin with the DataFileLoad command and the parameter "LVM" instead.
    The variables belonging to the LVDataLoad command are also no longer available. LVDATAContXAxis, LVDATAATimeAxis, LVDATAFileIs, LVDATAFileExt, LVDATAAppendData, LVDATAReaderRev, and LVDATARefChnMode.

Product Security and Critical Updates

Visit ni.com/security to view and subscribe in order to receive security notifications about National Instruments products. Visit ni.com/critical-updates for information about critical updates from National Instruments.

Availability of the 32-Bit Version of DIAdem

DIAdem 2017 is the last 32-bit version of DIAdem. As of DIAdem 2018, enhancements will only be made in the 64-bit version.

Availability of the Old REPORT Script Interface

The old script interface for accessing REPORT objects through GraphObjOpen and GraphObjClose will only be supported up to and including DIAdem 2017. As of DIAdem 2018, you must use the object-oriented script interface in DIAdem REPORT.

New Features in DIAdem 2017


The icons on the DIAdem interface have been reworked and unified according to the modern design guidelines of National Instruments. With the new symbols in different resolutions, the DIAdem interface automatically adjusts to high-resolution monitors and is therefore simpler to use.

The full screen mode was revised for the display on several monitors.

The different syntax elements in example scripts are displayed in color in the help.

The Calculator was entirely overhauled and can now be used modally. The entered formula is displayed in a graphic. At the touch of a button, calculations can be transferred to the Calculation Manager.

DIAdem was extended with many functions, for example, for number and date/time conversion.

In the units catalog, several units were added to the quantities Volume per time and Mass flow.

DIAdem NAVIGATOR, DataFinder, Data Portal

A function bar for saving and filtering data has been added to the Data Portal.

The properties display in the Data Portal and in NAVIGATOR now displays all properties in groups.


Curves can be moved in x-direction with the mousewheel when you press the Shift key.

You can change the colors and the line width of cursor lines.


The log area has been completely reworked. All input parameters are logged and you can delete and copy the log, and export it as an HTML file.

Many functions now provide return values in form of a collection of channels, to which you have object-oriented access.

The new function Calculate Corridor calculates tolerance bands with a specified distance to the original curve.

The new function Remove Duplicates removes identical values from a channel.

For each rpm value, Pulse Recognition generates an additional time channel that contains the time of the first pulse for each rpm value.

Matrix Interpolation offers a new interpolation process for data in triplets. The process is already used in the 3D display in REPORT.

Smoothing can now be performed with the median as well as the mean value.

The new crash functions Lateral Shoulder Rib Displacement, Lateral Thoracic Rib Displacement, and Lateral Abdominal Rib Displacement calculate the respective characteristic values.


Reports can now be exported as XPS documents with the Microsoft XPS Document Writer.

If you want a PDF output, you can use the default Microsoft PDF printer, which is available as of Windows version 10.

3D axis systems can now display scalable background graphics.

2D tables support automatic row height definition.

When printing and exporting to PPTX or PDF files, you can print all pages of automatically expanding tables.

When exporting in PowerPoint, you can use your own PowerPoint templates.

Copying and Pasting graphics from and to Office products through the clipboard has been improved.

Pasting a graphic with drag&drop automatically generates a graphic object in DIAdem.

You can specify the unit symbol in 2D tables.


The XNET driver also supports CAN-FD and J1939.

The GPS driver supports data in NMEA format through the serial interface.

For an interpolation matrix, the 3D interpolation specifies the z-value for the current x-values and y-values.

The constant provides any number of constants, including physical units.

The Save Data block was extended. The block accepts the measurement time as an alternative to the number of values. When saving to a file, the capacity of the storage medium can determine the end of the measurement. You can now save files that are larger than 2 GB. The memory block can save the measurement values of every trigger sequence in a separate channel group in the Data Portal. In addition, you can define the filename with the path and apply write-protection to the files after the measurement.

You can specify an initialization value for the Signal Copy, which DIAdem outputs until the first calculated value.

The Read Channel block has a Reset input to restart the reading procedure at the specified point of the offset.

The script driver can also write channel properties.

The new driver OBD-II supports the reading out of vehicle diagnosis data.

The new driver OPC-UA connects to the most current OPC communication protocol.

The grid distance in VISUAL is now configurable.


Additional functions were added to the event search, for example, for comparing channels through ChnEventCompareChn functions and for calculating statistical characteristic values through ChnEventStat functions.

In SUD dialog boxes, the control element XTable now supports context menus.

Commands were added to the BarManager in order to make it easier to create menu bars and menu bar items.

A new object-oriented interface enables the editing of properties of Office documents, PDF files, and graphics. You can read and write standard properties and user-defined properties. Therefore you can not only search for measurement data but also for documents in the DataFinder.

The new Tree control enables tree displays in SUD dialog boxes.


DataPlugins can unpack measurement data files from ZIP archives and can automatically delete them again afterwards.

DataPlugins also support UTF8 formats.

Corrected Errors in DIAdem 2017 SP1

The following items are the IDs and titles of a subset of issues fixed in DIAdem 2017 SP1. This is not an exhaustive list of issues fixed in the current version. If you have a CAR ID, you can search this list to validate that the issue has been fixed. The DIAdem Knowledgebase contains a list of fixed issues from earlier DIAdem versions under the search term Fixed Issues.

CAR IDDescription


669278The example for searching for obsolete variables and commands contains German texts in the English and Japanese versions. In the Japanese version of this example some texts are also displayed incorrectly.


639551The Bus Log Converter does not scale the time stamp of GIN multiloggers correctly.
661508When loading, DIAdem converts an implicit numeric channel with 32-bit values into an explicit channel.
645394DIAdem cannot create Excel files when the filename or the group name is longer than 24 characters.


638460DIAdem truncates the z-axis scaling at the right edge of the cascade display.


639568If you assign a value determined by the ChnFind function to a variable in the calculator, DIAdem reports a syntax error.
666353DIAdem writes the results of the two statistics functions - variation coefficient and relative variation coefficient - in the same channel properties.
666682In the calculator you cannot assign values to the properties of known objects, for example the Data object.


509311In a characteristic diagram display of isolines, you cannot create curve labels at the beginning or the end of the curve.
638076If you disable the first curve in a 2D axis system and select the setting "n-Systems" for the axis length, DIAdem displays the other curves incorrectly.
638077DIAdem does not align rotated text correctly when the reference points are different.
638498DIAdem crashes when a very large number of curves are to be displayed in a 2D axis system.
639566The isoline labels for the isoline curve type do not support the color setting "Same Color as Curve".
639844In automatically extending 2D tables, the title field display is too large.
639847If you select "Auto row height" for the "Table length" of a 2D table, DIAdem displays the text with too little room at the table edge.
640540DIAdem does not display the curve end labels of isolines in the characteristic diagram if you select the text color "Same Color as Isoline".
647929DIAdem might crash if you copy and insert object groups and then combine them to new groups.
649391You might not be able to add new curves in the dialog box of a 2D axis system.
653726In scaled layouts, the chart wizard creates an error.
657059If you use the chart wizard, an error might occur.
659562DIAdem might not position the curve of a 2D axis system with the scaling mode "Range and ticks manual" in the center of the axis system.
663019In DIAdem REPORT you can only align main objects with each other.
664109DIAdem calculates the tick interval incorrectly in a 2D axis system if this axis system contains several constants and the last constant is outside the scale.


644037A block diagram that uses a driver and a system clock to operate two output blocks in the foreground and in the interrupt might crash during a measurement.
645127Counter measurements with the NI-DAQmx driver return imprecise results.
648821When you open the DAC dialog box "Save Data", an error occurs if the setting "The capacity of the storage medium determines the end of the measurement" is enabled.


640754If you execute scripts that display a message box step by step in the debug mode, the scripts might not be executed completely.
647022If there are many channels in the Data Portal, the deletion of a large number of channels with the Data.Remove method might be slow.
653814If you edit in the script editor a file saved on a slow network drive, the display of the entered characters might be delayed.
663826DIAdem only uses significant digits when processing Float32 values of the properties of the internal data.
664024The OnFileLoading event is not available in the 32-bit version.
665048In the Analysis Server of the TDM Server no text searches can be loaded.

Corrected Errors in DIAdem 2017

The following items are the IDs and titles of a subset of issues fixed in DIAdem 2017. This is not an exhaustive list of issues fixed in the current version. If you have a CAR ID, you can search this list to validate that the issue has been fixed. The DIAdem Knowledgebase contains a list of fixed issues from earlier DIAdem versions under the search term Fixed Issues.

CAR IDDescription


543644In the English and Japanese versions, some message texts are not translated.
560137When writing TDMS files in a search area of the DataFinder, LabVIEW sometimes creates invalid TDMS files.
567833DIAdem does not execute the start script saved in the desktop file if you double-click a file registered by DIAdem.
572772DIAdem might crash if you open the introduction screen from the ExampleFinder.
581705When loading data with special Data Plugins, the Data Portal is refreshed without prior notice.
582210The crash analysis documentation "Pulse Test" contains a wrong graphic for "High Severity Pulse Corridor".
585387If the GPI function channelExists() is called several times, DIAdem crashes due to an access violation.
601900After implicit waveform channels and implicit waveform time channels have been copied in the Data Portal, the copied channels are no longer waveform channels.
601993After the update of Windows 10 to version 1607, the "My DataFinder" DataFinder can no longer be configured.
604982The channel properties "Minimum" and "Maximum" contain inaccurate values in time channels.
609315When you exit DIAdem, you cannot select the program folder to save the changed files.
613926The "NoValue" value is used as a NoValue substitute value for text type properties. When you access via the Properties <Data> collection, the value NULL is returned instead of the text.
616989DIAdem executes the start script before the commands you specified at the program start behind the /C parameter.


563415If you use a DataPlugin to read time values from an Excel file, milliseconds are missing.
572954DIAdem cannot load data correctly if the associated DataPlugin name contains Asian characters.
574547When saving TDM files with changed file, group, and channel properties, DIAdem also saves mass data when the filename extension of a TDM file contains lower case characters.
575439The Bus Log Converter only supplies channels with one value after the conversion of Vector-ASCII logfiles with text IDs and if "Extended Bit" is set.
576489The Bus Log Converter does not calculate the NoValueKey and Monotony properties while converting data, but when loading the data. This can lead to disproportionately long waiting times for very large TDM files (>5 GB).
576790If a TDMS logfile contains several buslog channels, the start times after the second buslog channel are wrong following the conversion with the Bus Log Converter .
576792For logfiles with multiplexer, the Bus Log Converter sometimes calculates wrong minima and maxima in the time and sequence channel.
583520The Bus Log Converter does not find any extended Ids in the PCAN trace log files.
584817When you use the Bus Log Convertor, temporary files might stay open. You can only delete these files when you exit DIAdem.
586949In the 64-bit version of DIAdem, if you have selected a channel and the channel preview is active, an access violation sometimes occurs if the file is saved several times.
602616Corrupt TDMS index files result in a program crash.
620412The Bus Log Converter does not evaluate the J1939 protocol in Vector BLF logfiles.
623913If you set a filter in the data browser of an ASAM data store, tree node entries sometimes occur n times.


474529If the displayed channel in a 2D axis system contains only one value, DIAdem might display a very large x-area in the 2D axis system.
553769When you transfer a layout from DIAdem VIEW to DIAdem REPORT, errors might occur.
556535When you scale a 2D axis system in percentage, the sub cursors of the curve cursor might be incorrectly positioned.
557289If you create many worksheets, the program might crash.
581516DIAdem does not display constants in the selected color.
594924The "Go to Channel Value / Find Channel Value" dialog box finds only the first value in channel tables which meets the specified condition.
625430If you enable the function "Scroll in Cursor Range", you cannot move the range with the mouse wheel when you press the Strg key.


530862If you select "Store result in original channel" in the "Savitzky-Golay Filter" dialog box, an error occurs.
550041If you execute calculations with registered channels in the 64-bit version, DIAdem outputs many messages in the logfile.
552886If you differentiate non equidistant signals numerically and retain the original length of the channel, the results are incorrect.
554316The commands ChnEventFilter and ChnEventDuration do not function correctly when the x-channel contains date/time values.
555602The first calculation of the two-sided cross correlation in the time range is wrong.
556431The calculation manager may calculate incorrectly if you use symbols in a formula that start with the same character as the strings used in the formula end.
563008In rare cases the non-linear curve fitting crashes.
563294The bit functions do not properly include bit 31.
570116If there is one channel with the length 0 in the list of channels to be sorted, DIAdem sets the channel length of all channels to 0 in the "Sort Channel Values" function.
575981If you use a wrong formula in the ChnCalculate command, this can lead to undefined behavior in various places in DIAdem.
576557The ChnEventDetectionWindow command does not always find all events in a signal when the hysteresis is specified.
576830If a signal in the value range you are searching for only contains NoValues up to the end of the channel, the ChnEventDetectionWindow command only finds one value as the last event.
577056If you use approximation coordinates in 2D axis systems, of which one or more channels do not exist, DIAdem crashes.
578265The ChnEventDetectionSlope command does not generate x-values in the search result. Only one x-value is saved for the first search result, but this value belongs to the last find occurrence.
586785The command ChnEventCreateStatusChn interprets the value 0 for the ChnEventTrueValue parameter as 1.
586810The ChnEventDetectionSlope command ignores the defined hysteresis at the first find occurrence.
591530In the "Order Analysis (Time Domain)" dialog box, the "Set Parameters" button might suggest the value 0 for the step width for the "Reduction according to RPM", which leads to an error in the following calculation.
592318The "Linear Mapping" function crashes if the y-channel has only one valid value and otherwise only NoValues.
613104DIAdem does not always create the result channel correctly when you call the event search functions several times.
613995The calculated amplitude values of the order analysis for Bode display is too large by a factor of four.
616071Sometimes an error occurs in quantity-based calculations.
616854In reducing classification with two x-channels, the function returns the value 0 instead of NoValue in mean value reduction mode for the classes which contain no values.
620429The function "Optimize Data Type" creates an error when the channel length is 0.
628103The resampling function sometimes crashes.
628973If you open the "Sort Channel Values" dialog box, an error might occur.
631128If you use the SCADI interpolation method for a 3D interpolation, you cannot abort the interpolation with the escape key.


252052Worksheet names with Unicode characters create unreadable bookmarks in PDF documents.
534692In the scaled display the values for the height and offset of the y-axis in 2D axis systems are incorrect.
549331When displaying a differential characteristic diagram with enabled boundary curve, the display of the characteristic diagram may be wrong.
551845DIAdem does not remember the deletion of a text list entry from a 2D table when saving or undoing.
554547If you create new curves in polar axis systems and then change the curve type, DIAdem sometimes displays wrong colors in the dialog box.
554548If you delete a channel name in the dialog box of a 2D table, an error occurs in an expanding layout.
563009In a user-defined scaling mode, DIAdem displays a wrong selection list in the dialog box if the referenced user-defined scaling is not defined in the desktop file.
563018DIAdem sometimes does not display individual columns in 2D tables if these columns contain text lists.
563716You cannot hide the symbol field in the legend of a 3D axis system.
566044If you change the name of a worksheet and then move directly to another worksheet, DIAdem displays the wrong content.
566494If you delete the first worksheet in a layout with expansion mode, DIAdem disables the expansion mode.
566964If you use the method Copy for Sheets in a For...Next loop, DIAdem does not copy the worksheet to the expected position in DIAdem REPORT.
569343If you export scaled layouts with changing orientation, DIAdem does not always calculate the margins correctly.
570447If you use a script to create a 2D table with a text list, DIAdem displays this table only briefly when replotting the table.
576825If you select the "Characteristic diagram" display type in a 3D axis system, you cannot enable the "3D-curve" display type afterwards.
582474When you transfer a layout from DIAdem REPORT to DIAdem VIEW, the transferred layout has incorrect axis scalings if the original document contains manual scalings.
582678DIAdem twists the column colors of a 2D table when changing the direction of the table.
585358The curve end label in the 2D axis system is not displayed if you select an end value for the x-axis that is smaller than the greatest x-value.
585359If you create a sub-axis in a 2D axis system, an error might occur.
585364If you create a scaled layout with a portrait format and the page size A4 in a German DIAdem version and open it in an English DIAdem on an English operating system, DIAdem displays the page size "user-defined".
585367If you change a scaled layout to a non scaled layout, the English DIAdem displays the page size "User-defined" in the layout parameters.
585524DIAdem does not apply the color of the curve end label of a 2D axis system correctly if you set the color in the associated dialog box.
586245Sometimes you cannot select the y-axis of the 3D axis system.
590010In 2D axis systems, DIAdem does not use the setting "Label each curve section between NoValues" for the curve end label.
591311DIAdem does not plot a coordinate in a 2D axis system if you select the marker style "None".
591698DIAdem does not display all measurement points in the 3D display type characteristic diagram with matrix data.
592675Curve labels at the end and at the beginning of an isoline are only possible if you select labels on the isoline.
593712DIAdem does not display curve end labels for constants in 2D axis systems.
594138DIAdem displays superscript and subscript text in tables incorrectly.
596956If you use linear interpolation, the surface display is incorrect in a differential characteristic diagram.
597149If you delete a table entry in a 2D table dialog box, an error might occur.
598103If you add a coordinate to a 2D axis system, the automatic scaling of the y-axis sometimes changes.
598229If you abort the configuration dialog box of a 3D axis system, the automatic scaling of axes sometimes changes.
598231If you use the Remove for Sheets method in a For Each...Next loop, an error occurs.
601702DIAdem displays incorrect minimum and maximum values in the contour table of the curve dialog box for a differential characteristic diagram.
601926In the expanding mode, you cannot configure more than 10 list entries without errors in the curve configuration dialog box.
602144You cannot project isolines on all planes at the same time.
603654DIAdem also displays points beyond the differential characteristic diagram.
603806The z-axis label in a 3D axis system is incorrect if the first curve is an isoline.
603807If you select the setting "Upper interval limit" under "Input interval of the palette" in the "Global Color Palette" configuration dialog box, you can only set the value 1.
604481You cannot label the isoline in a 3D axis system only at the curve end.
604669In the object-oriented script interface of DIAdem REPORT, DIAdem allows the assignment of incorrect values for the line type.
605267The characteristic diagram display in a 3D axis system is wrong if you modify the display area for user-defined scaling.
611618Automatic scaling of the x-axis in a 2D axis system with several y-axes is incorrect if no curve is assigned to the first y-axis and a bar display is assigned to the other y-axes.
614388If you select "Only at curve end" for the isoline labels in a 3D axis system, DIAdem does not plot any additional isolines.
614767You cannot use the color palette of a 3D curve in a 3D axis system for the display of markers.
623329If you use events, an access violation sometimes occurs if you export to a PDF file.
623944DIAdem ignores line feeds in the text object if these line feeds are contained in a variable.
626015DIAdem ignores the deletion of text list entries in 2D tables when you save the layout and reload it.
629966You cannot define more than 17 subaxes in the dialog box of a 2D axis system.


544747If binary data is converted with the UDI object, some bytes in the range between 0x80 and 0xFF are incorrectly interpreted, which leads to wrong measurement results.
554507In the configuration dialog box for the DAQ list, the button "Read Event Channels from the ECU" in the ECU MC driver does not have a function.
567224If you connect signals from the same clock system to the remote inputs of the Function Generator, it outputs only NoValues.
573714The blocks "Scatter" and "Video" can be edited with a DAC-Kit license although a DAC Bundle license is required.
574166When the script driver outputs data, the last valid value is transferred to the script instead of a NoValue if the measurement values are invalid.
581689DIAdem can only use one counter for a measurement in an NI-9361 module.
582944Sometimes you cannot select a new x-channel or y-channel in the "Free Linearization through Channels" block.
590332If you specify a unit in the Linearization block, DIAdem does not apply this unit if the driver block connected to the input has its own unit.
594976The BlPinSigCountSet command sometimes displays errors if DIAdem VISUAL is open.
624717If you rename the blocks Trigger Sequence and System Clock, DIAdem does not automatically change the name of the output signal.
629733DIAdem sometimes truncates the decimal places when you use the UDI.Append function to convert binary data into strings.


524131At some places German texts appear in the script editor.
540486The ChnGet command has not been supported since DIAdem 2014. The dialog box templates in DIAdem SCRIPT show you how to create a channel selection dialog box.
542638The identifier 'UseFileList' in the 64-bit version supports an outdated serial evaluation.
545047The functions ChnAreaInsert0 and ChnAreaDel does not function correctly with text channels.
573133After you have executed the ChnResampleFreqBased or the ChnEventCreateStatusChn commands in a script, other ANALYSIS commands in this script may not generate any result channels with waveform properties.
592333Sometimes the FormulaCalc command creates additional channels.
602085The return value of the TextFileSeek function shows an error when you try to position the bookmark on the last row of a text file.
609471The Curve2DPreview control cannot display waveform channels correctly with a logarithmic y-scaling.
619355The AddChannel for Channels method sometimes consumes more storage space than necessary when copying channels.
634544DIAdem crashes if you use the Move for Data method in the debugger.

Accessing the Help

For more information on DIAdem, go to the DIAdem help Help»Contents.

Finding Examples

Use Help»Examples in DIAdem to start the DIAdem ExampleFinder. You can find DIAdem examples in the examples directory below the program directory. You can modify examples to suit your needs, or you can copy and paste parts of the examples into your own files.

Automating the Installation of NI Products

You can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes.

If the NI product you are installing uses Microsoft .NET 4.6.2, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.6.2 separately before you install NI software.

For more information, refer to the following KnowledgeBase articles:

Using NI Software with Microsoft Windows 10

Microsoft Windows 10 is the latest version of the Windows operating system. Windows 10 features significant changes compared to previous versions. Windows 10 combines features from both Windows 7 and Windows 8. Moreover, the operating system introduces several new capabilities. For more information about NI support for Windows 10, visit ni.com/windows10.

Using NI Software with Microsoft Windows 8.1

When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8.

Legal Information


© 2003—2017 National Instruments Ireland Resources Limited. All rights reserved.

Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, This includes photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.

National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.

End-User License Agreements and Third-Party Legal Notices

You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:

  • Legal notice: Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
  • EULAs: EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
  • Information on including legal information in installers built with NI products: <National Instruments>\_Legal Information.txt

U.S. Government Restricted Rights

If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.

IVI Foundation Copyright Notice

Content from the IVI specifications reproduced with permission from the IVI Foundation.

The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.


Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.


For patents covering the National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.