CVI™, FieldPoint™, LabVIEW™, National Instruments™, and ni.com™ are trademarks of National Instruments Corporation.
Product and company names mentioned herein are trademarks or trade names of their respective companies.
This document contains important information about using the FieldPoint software with National Instruments application development environments. Please read this document completely before using the FieldPoint software.
Supported Operating Systems
You can run the FieldPoint installer on the following operating systems:
Windows 7 (32-bit and 64-bit*)
Windows Vista (32-bit and 64-bit*)
Windows XP SP2(32-bit)
Windows Server 2003 R2 (32-bit)
Windows Server 2008 R2 (64-bit*)
The FieldPoint installer does not support Windows 2000/NT/Me/98/95 or the Windows Server non-R2 editions.
Operating system versions marked with an asterisk (*) will run within the 32-bit emulation layer, Windows on Windows (WOW64).
New in FieldPoint 6.0.8Support for LabVIEW 2010 SP1FieldPoint 6.0.8 Bug Fixes
The following items are changes from FieldPoint 6.0.7 to FieldPoint 6.0.8
[tr][/tr]
Bug ID
Fixed Issue
#237610
cFP TC-125 does not allow higher speed the 1 Hz.
#253527
Fieldpoint I/O Point Controls give an browse dialog error when built into LV 2010 and FP 6.0.7 executable.
#246287
Fieldpoint incorrectly reads 0 without error or warning.
Known Issues in FieldPoint 6.0.8cFP-180x User LED Is Inaccessible through Serial Port
The cFP-180x User LED channel is accessible only through an Ethernet connection. You cannot read or control the User LED through a serial connection.
Remote I/O Error Reporting May Not Match Host VI Error Reporting
A VI running embedded on an RT controller may report errors for remote I/O that do not match the errors reported by the same VI running on a host computer. For example, if an AI channel is out of range, an FP Read running on a host computer reports an Out of Range error. The same VI running on an RT controller returns channel-specific error A or B. Refer to the Attributes, Ranges, and Commands topic of the FieldPoint LabVIEW Interface Help for information about error messages (channel status). Doing remote I/O over serial may result in an Unknown Tag error (32812) if initialization with the module fails.
Upgrading FieldPoint RT Controllers to LabVIEW Real-Time Module 8.5.1, 8.6.1, 2009 SP1 and 2010 SP1
The cFP-22xx controllers require LabVIEW Real-Time Module 8.5.1 or later. The cFP-21xx controllers require LabVIEW Real-Time Module 8.0 or later. National Instruments recommends LabVIEW Real-Time Module 7.1.1 for use on the [c]FP-20xx controllers. The [c]FP-20xx controllers do not support LabVIEW Real-Time Module 8.6 or later. Some features of LabVIEW Real-Time Module 8.x require more than 16 MB RAM, and the [c]FP-2000 and some other [c]FP-20xx controllers have only 16 MB RAM. Use the Remote Systems Install Software Wizard in MAX to install LabVIEW and FieldPoint software on FieldPoint controllers. For more information about memory and storage requirements of different LabVIEW versions, go to ni.com/info and enter the Info Code rdlrmf.
LabVIEW Real-Time and FieldPoint Software on FieldPoint RT Controllers
For information about which versions of the LabVIEW Real-Time Module and FieldPoint software components on the FieldPoint RT controller are compatible with each other, go to ni.com/info and enter the Info Code fpswlist.
MiscellaneousNI-FieldPoint 6.0.X supports the following LabVIEW Versions:
This table shows only major versions but includes all maintenance releases.
NI-Fieldpoint
Supported LabVIEW Versions
6.0
7.1/8.0/8.2/8.5
6.0.1
7.1/8.0/8.2/8.5
6.0.2
7.1/8.2/8.5/8.6
6.0.3
7.1/8.2/8.5/8.6
6.0.4
7.1/8.2/8.5/8.6
6.0.5
8.2/8.5/8.6/2009
6.0.6
8.2/8.5/8.6/2009
6.0.7
8.5/8.6/2009/2010
6.0.8
8.5/8.6/2009/2010
FieldPoint IAK Configuration File Included in Application
With FieldPoint 6.0.2 or later, you can include FieldPoint configuration files in the data directory of a LabVIEW application. Check Include hardware configuration files on the Advanced tab in Application Properties to use this feature. The built application will use the IAK configuration file in the data directory instead of the IAK file registered with the system.
Which IAK file LabVIEW uses for a VI depends on the type of VI, whether or not the VI is part of a LabVIEW project, and whether or not the VI has been built into an executable. The table below describes which IAK file is used in each case.
Type of VI
VI in a LabVIEW Project
VI not in a LabVIEW Project
VI built into an EXE
Polymorphic FP Read, FP Write and FP Write/Read
IAK file associated with the Project
Most recently opened IAK file
IAK file distributed with EXE
FP Get Configuration.vi
IAK file associated with the LabVIEW Project
Most recently opened IAK file
IAK file distributed with EXE
Legacy VIs (FP Open, FP Create Tag, FP Close)
Most recently opened IAK file
Most recently opened IAK file
Most recently opened IAK file
Support for Measurement & Automation Explorer (MAX) 4.5 or later to Delete Disconnected Remote Systems
To delete a disconnected remote system, right-click Remote Systems in MAX and select Delete Disconnected Systems. Offline FieldPoint systems with saved configurations will not be deleted.
Creating a FieldPoint Distribution Kit
If you are deploying a FieldPoint executable built with LabVIEW 8.0 or later, you can include FieldPoint 5.0 or a later version in the installer. You also must copy the .iak file associated with the project to your application.
To create a FieldPoint executable using LabWindows/CVI, you must include FPCVIMgr.DLL in the distribution kit. By default this file is installed in the \WINNT\system32 folder for Windows 7/VISTA/XP.
The .iak file created in MAX also must be included with the FieldPoint distribution kit.
FieldPoint OPC Server
The latest FieldPoint OPC server supports version 2.04 of the OPC Interface Specifications.
NOTE: The return value for tags of type VT_BOOL has changed from +1 to -1 (0xFFFF - VARIANT_TRUE) to comply with the OPC specifications. All discrete input and output items (except the "All" item) for FieldPoint channels are defined to be of type VT_BOOL. If you have an OPC application that checks for data values strictly equal to +1 for discrete items, change it to check for -1 or for a non-zero value (recommended).
楼主
