DASYLab 2016

Version 14.0.0

September 2016

This file contains information on DASYLab 2016:


System Requirements

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

Hardware

CPU x86 compatible processor from 1 GHz upwards
Memory More than 1 GB, recommended 4 GB
Hard disk memory 1 GB free memory space, of this at least 500 MB on this system partition.
Graphics board Color depth at least 24-bit or 32-bit (True Color)
Screen resolution At least 1024x768

Operating Systems

Note  Please note that not all DASYLab drivers support all the listed operating systems. DASYLab does not run under Windows 7 Starter Version.

Note  Please note that you have to be logged onto the computer as administrator in order to install DASYLab and to call up the configurator or to work via the network. If you are logged on as a standard user, you can call up DASYLab. However, DASYLab does not support logging on as a guest.

Note  You may not use any Asiatic characters in the installation path.

New features in DASYLab 2016


New module: State Machine

You can use the new state machine module (control sequence chains) to compile sequences which were previously set up using a combination of action modules, trigger modules, relays and links into a lower number of modules. The operations are considerably more simple to create and to administer since steps can be added, deleted and changed in their sequence inside the module itself.

Whereas all modules were always worked off simultaneously in parallel using the conventional setup of a sequence chain in DASYLab, only the currently active branch is edited in the state machine module. This does not just accelerate the development, but also execution of the state machine requires less computer time and memory during runtime.


Block size

The maximum block size was significantly increased from the previous value of 32768 values per block (32k) to 1048576 values per block (1M) in the current version. The resolution or accuracy has been considerably increase, especially in the case of block-based operations such as an FFT. The user also profits from an improved support for faster measurement technology and the multiplexing of channels has been optimized. A few old drivers ("DASYLab Driver Toolkit drivers") and the time base "Driver" cannot use the new maximum block size and are still restricted to the previous 32k-sized blocks.


Double data type (64-bit)

The internal data format — both for measurement data recording and also for further processing — has been converted from float (32-bit floating-point type) to double (64-bit floating-point type). Even if a wide range of hardware has been supported in the past, this deep-reaching modification through the entire DASYLab structure now enables you to use the capabilities of modern high-resolution measuring hardware with a considerably increased accuracy.


File format: TDMS

DASYLab 2016 now supports the TDMS file format (TDM Streaming) so that measurement data can be recorded and processed using other programs. TDMS also stands out thanks to the fact that different data channels can be saved here with differing speeds and channel types.


File format: DASYLab

The DASYLab file format (file extension DDF) also has also been given an extension so that large data blocks and measured values can now be saved with double accuracy. You can now choose to save DDF files in the "traditional" format from DASYLab 13 in order to guarantee compatibility with older DASYLab versions. However, the restrictions imposed by older DASYLab versions continue to apply in this case: the block size is at most 32768 and the data type is float (single precision, 32-bit).


Reading TDM and TDMS files

DASYLab 2016 can now read in TDM and TDMS files. This increases compatibility with other products. If you wish to evaluate measured values both using DASYLab and with other programs, you now only require one format.


Python: Update to Version 2.7.10

The integrated Python environment in DASYLab 2016 has been updated from version 2.6.5 to version 2.7.10. In addition to a range of detail improvements in language and error correction, you can now also access a wide range of Python modules which were not yet or no longer supported in Version 2.6.5. You can find details on the website at https://hg.python.org/cpython/raw-file/v2.7.10/Misc/NEWS.


System Information

The system information you accessed over Help»About has been extended. Especially the details about the operating system and the computer have been amended. The report you accessed over Help»Report was revised and user information was added.


Saving of layouts as image by action

For all image formats this functionality was supplemented by a scaling option which appears as an additional parameter in an action module's configuration dialog. Without additional scaling (at factors 0 and 1) the image will be saved at the size of the display DASYLab was started on. Earlier versions of DASYLab saved the images with wrong dimensions. Especially with print layouts, this led to very bad results in small formats.
The scaling differentiates between 3 ranges for the scaling factor (all values outside this range will be treated as 1.0):

  1. 0.125 ≤ parameter value ≤ 8.0
    The parameter value is interpreted as multiplier.
    For example, if you set the parameter value to 2.0, the saved image's height (width) is twice as high (wide) as the display's height (width) DASYLab 2016 was started on.
  2. 150 ≤ parameter value ≤ 1200
    The parameter value is interpreted as DPI size.
    For example, if you set the parameter value to 300, the image's resolution will be 300 DPI — irrespective of the current screen resolution set in the control panel of the Windows operating system.
  3. 1280 ≤ parameter value ≤ 20000
    The parameter value is interpreted as number of pixels for the image's width.
    The calculation retains the aspect ratio of your display.
    For example, if you set the parameter value to 1920, the image's resolution will be 1920x1080 — provided that your display has an aspect ratio of 16:9.

Time bases

With DASYLab 2016, two additional time bases have been introduced: the so-called virtual time bases. These are used as a reference to real time bases and simplify uniform allocation of certain hardware time bases (which are not "drivers") to the data-creating modules (for example, a Generator or Slider).

The behavior of automatic block sizes has been changed. The "automatic block size" is no longer a power of two, it is now 1/10 of the set sampling rate.

The time base dialog has been reworked. Selection of the time base now takes place in a list which can also display longer names of time bases completely. This now makes it more simple and clear when selecting a specific time base to change its parameters.

For modules that generate data the time base presetting has been changed to DASYLab. For historical reasons, in previous DASYLab versions the time base Driver was preset. Modern DASYLab drivers which are created using the Extension Toolkit can provide their own time base.


Regrouping and extension of DASYLab's Global Settings dialog


Improvements for multi-screen operation

When using multiple screens with DASYLab, we recommend a simple monitor configuration with:

Other configurations do work much better than in DASYLab 13, but might result in unexpected behavior — especially different zoom factors for different screens (new notebooks with high resolution very often have zoom factors other than 100%). These effects relate to the support of Windows 7 in most cases.

Note  Please keep in mind that changing the zoom factor of a screen needs a shut down of DASYLab, log off / log on to Windows and restart DASYLab again to take effect in DASYLab.


Miscellaneous improvements


Compatibility with older DASYLab versions

Due to extensive changes to the data format, block sizes and memory management, all modules from third-party suppliers which use the Extension Toolkit for implementation have to be adapted for DASYLab 2016. Most hardware manufacturers which offer their own DASYLab drivers will provide new driver versions for the release of DASYLab 2016. Needless to say, the drivers supplied with DASYLab 2016 have been updated for the release.

Older drivers which still use the Driver Toolkit (these are available in menu Measurement»Select Driver...) are not affected by this and also function with DASYLab 2016. However, these drivers cannot use the changes introduced with DASYLab 2016: greater accuracy and increased block size.


Driver Development

The following drivers are new or have been revised. Refer to the driver help sections for a detailed description of each extension.


Fixes issues in DASYLab 2016

The following list contains descriptions of the issues fixed between DASYLab 13 and DASYLab 2016.

ID Caption Description
2110 Bitmaps on buttons of Switch modules If images for buttons are stated using global strings, the images are not displayed when loading the worksheet.
The issue has been resolved.
3361 Create missing folders DASYLab was unable to create files and directories, if the target was accessible via a network path: //servername/share/folder/file.ext. The issue has been resolved.
Note  The currently logged on Windows user that launched the DASYLab application, needs to have granted privileges to create files and directories at the given location on the network.
3426 Error in flip-flop module If the hold time was stated in seconds and the value was read from a global variable, in rare situations that could cause a crash of the application.
The issue has been resolved.
--- Visualizationn of global variables and strings The text for a variable's name (and description) can have a length of 19 characters. The texts are now no longer abbreviated to a fixed length by two points.
--- Slow loading of worksheets When loading a worksheet with Y/t Chart modules the x-axis was drawn at wrong positions. The loading of worksheets was considerably delayed when the worksheet used numerous Y/t Chart modules.
This error has been resolved.
--- CAN driver and CANdb files in frame mode If signal configuration took place using a CANdb file, the interpreted values were incorrect. The correct results were supplied during manual configuration (without using a CANdb file).
This error has been resolved.
--- Incorrect calculation of available memory DASYLab detected the available memory incorrectly, so that the results were sometimes wrong on 64-bit operating systems.
This error has been resolved.
--- Error message "Display time is too large" The error message is now only shown once and no longer for each of the module's channels. Additionally, the automatically determined value is now rounded off to prevent repeated display of the same message.
--- DAQmx Counter Input Upon entering a timeout the specified replacement value was not properly output from the module.
This error has been resolved.
--- Error in Polar Plot module If the block size of the current data was larger than the block size at the time of the module's creation, it could cause crash.

 

Known issues

The color sonogram and the waterfall presentation in the Y/t Chart module do not harmonize very well with the introduced larger block sizes. If you exhaust all potential offered by DASYLab 2016 here, the execution of a worksheet could be considerably slowed down.

 


 

Copyright

© 2016 National Instruments Ireland Resources Limited. All rights reserved.

Under the copyright law, this publication may not be reproduced or transmitted partially or completely in any form, electronic or mechanical, without prior written consent by the National Instruments Corporation. 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:

Trademarks

LabVIEW, National Instruments, NI, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. You can find additional National Instruments brand names in the Trademarks at ni.com/trademarks.

Other product and company names mentioned herein are trademarks or trade names of their respective companies.

Patents

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