H5Labview and 1-D arrays

The current version of h5labview 2.7.3.112 can completely crash Labview 2013 SP1 when using 1-D arrays.

What I do to fix this is insert the “Build Array” into my 1-D array just before it hits HDF5 Write Data. On the Read Data, to get a 1-D array again, you can use Index Array with the first row index input as 0.

HDF5 in Labview 2013

There is steady development of the h5labview package, allowing use of many common HDF5 read/write features from Matlab.

0) install VI package manager
1) download and install the latest SHARED HDF5 library from http://www.hdfgroup.org/HDF5/release/obtain5.html#obtain
get the appropriate operating system and 32 or 64 bits according to your Labview install 32/64 bits, not the OS.
2) copy the files hdf5.dll, szip.dll, zlib.dll from
c:\Program Files\HDF_Group\HDF5\1.8.13\bin to
c:\Program Files\National Instruments\LabVIEW 2013\resource

3) download latest .vip file from http://sourceforge.net/projects/h5labview/files/
this will open in VI Package Manager

If you get an error upon installation complaining about PostInstall.vi, try rebooting once.

reference: http://h5labview.sourceforge.net/?faq

LabVIEW Shared Variables through Windows 7 Firewall

Getting the LabVIEW 2011 Shared Variable Server to work through Windows Firewall on Windows 7 x64 will require allowing the following programs to pass through the firewall:

C:\Windows\SysWOW64\lkads.exe
C:\Windows\SysWOW64\lktsrv.exe
c:\Program Files (x86)\National Instruments\Shared\Tagger\tagsrv.exe

Note: even when using LabVIEW 64-bit, the directory for tagsrv.exe is still under the x86 Program Files.
Note: For LabVIEW 32-bit, the lkads.exe and lktsrv.exe will be under c:\Windows\System32\

Also, you must allow the following ports through Windows Firewall:
TCP: 2343, 59110-59115
UDP: 2343, 6000-6010

For the TCP ports, you must open one port above 59110 per “per application,”–by opening 59110-59115, we assume that no more than 5 applications are running concurrently.

LabVIEW 2011 64-bit (on Windows 7 x64) installation

LabVIEW 2011 has only a few toolkits that work as a 64-bit installation on 64-bit Windows 7. You can see the list of the supported LabVIEW 64-bit toolkits at:

http://zone.ni.com/devzone/cda/tut/p/id/10383

With regard to Device Drivers, the same Device Drivers DVD or download (4.8GB) is used for 32-bit and 64-bit LabVIEW. When you start the Device Driver installation, you will be prompted for each available items whether you want 32-bit or 64-bit.

National Instruments notes that you can install both 32-bit and 64-bit LabVIEW on a Windows 7 x64 system, and virtually all toolkits are said to work for a 32-bit LabVIEW install on a Windows 7 x64 (64-bit) system. There is said to a bit a of a performance penalty for using 32-bit LabVIEW on 64-bit Windows 7, due the Windows on Windows (WoW) emulation layer, but I haven’t yet found any benchmarks supporting what the difference is. Perhaps something I’ll post on in the future.

LabVIEW 2011 Device Drivers installation (unzipping) issues

The built-in ZIP-file decompression of Windows 7 x64 does not seem to be able to handle the 4.8GB download of the LabVIEW 2011 Device Drivers–the ZIP decompression crashes after several minutes.

I have found that the free, open-source (FOSS) 7-Zip program handles such large (>2.1GB) ZIP files easily, unzipping this large 4.8GB file in about 3 minutes.

www.7-zip.org