Header image
 
Control Prototyping
 
    Home  || Products  || Support  || About Us  || Contact Us  
   
 

Software Downloads

CalVIEW

Drivven's calibration toolkit for LabVIEW (see product page)

CalVIEW 1.0 for LabVIEW 8.2.1 (13 Mb) (build 950)

CalVIEW 1.1 for LabVIEW 8.5 (12.2 Mb) (build 1151)

CalVIEW 1.2 for LabVIEW 8.5 and 8.5.1 (20.5 Mb) (build 1854)

(updated 8/19/2008)

If you are installing CalVIEW on a machine which does not already have LabVIEW or the LabVIEW Runtime Engine, then you will also need to install the LabVIEW Runtime Engine (see link below) from the National Instruments website.  Be sure to install the properly targeted version of the Runtime Engine for the CalVIEW version you are using.

Activating CalVIEW

After installing CalVIEW, select "Activate CalVIEW" from the CalVIEW Help menu and follow the instructions.  All installations of CalVIEW require an activation code to function.  Development seats of CalVIEW, which allow the user to modify CalPoints, have an associated licesne fee (see product page).  If 3 or fewer seats are required for the purpose of a calibration/user interface to a pre-compiled application, then there is no license fee.

LabVIEW Runtime Engine

LabVIEW 8.2.1 Runtime Engine Standard (70 Mb)

LabVIEW 8.5.1 Runtime Engine Standard (100 Mb)

You only need this if you are installing CalVIEW to a machine which does not have LabVIEW installed.

Patches

LabVIEW 8.5 FPGA Interface Patch 12/06/2007 (Not Required for 8.5.1)

Replace the existing VI located at:
\Program Files\National Instruments\LabVIEW 8.5\vi.lib\rvi\Bitfile\Public\nirviGetControlsFromBitfile.vi
with the included VI of the same name and restart LabVIEW.

This patch corrects a problem associated with not being able to read/write FPGA controls and indicators when the undocumented dot and group notation is used in top level FPGA applications. An error occurs when attempting to read/write the first control/indicator in the tabbing order of the FPGA front panel.

Drivven uses the dot and group notation in the FPGA because the RT access time to each individual
control/indicator is about 1/4 the access time when performed via clusters.