LabVIEW Virtual Instruments

A library of National Instruments(R) LabVIEW Virtual Instruments for Pyramid Technical Consultants, Inc. products. The library is for use with LabVIEW 8.0 or later.

The library interfaces to an intermediate Microsoft(R) .NET layer (Interpreter.dll and dependency PTCScreenControls.dll), that then interfaces to the Pyramid Technical Consultants, Inc. win32 C++ class library, PTC_Controls32.dll. These DLLs require the .NET framework v2.0. This is included on all new Windows PCs, or you can download it from the Microsoft website here.

The installer will install all files to a directory in your Program Files folder called "Pyramid Technical Consultants, Inc\PTC_ControlsLV LabVIEW Library", with subdirectories for the library files and the reference documentation.

The release covers the A500, I200 and I3200 products. Pyramid recommends the IG2 software for new projects that use Labview. See links to .vi files in individual product download screens for examples using IG2 connection.

The utilities vi packages provide support for LabVIEW developers creating serial ASCII connections to Pyramid devices. Use the terminal mode package if the device uses or is set to terminal mode (gives "OK" response to valid commands). Use the non-terminal mode package if the device is set to standard SCPI mode (no response to valid messages unless they are queries).


Firmware version numbers and release dates are normally included in the file name as follows: (ProductProcVeryymmdd.extn). Product is the product type, such as M10, Proc is the embedded processor target for the code (PIC microcontroller or FPGA), Ver is the version number, and yymmdd is the release date (year-month-day).

G2 products with A60 processors use a single integrated firmware release zip file that combines processor application and operating system code, plus FPGA codes. The PTC DiagnosticG2 program uses the zip file directly - there is no need to unzip it before uploading.

Firmware and host software is generally backwards-compatible. Where earlier hardware is incompatible, an alternative version is provided. If you have a complete Pyramid control system with customized firmware for your application, you should contact us before attempting any upgrades. If you need more information about compatibility, please contact