![](/user_photo/2706_HbeT2.jpg)
- •Worldwide Technical Support and Product Information
- •National Instruments Corporate Headquarters
- •Worldwide Offices
- •Important Information
- •Warranty
- •Copyright
- •Trademarks
- •WARNING REGARDING USE OF NATIONAL INSTRUMENTS PRODUCTS
- •Contents
- •About This Manual
- •Conventions
- •Related Documentation
- •Calling Code in Various Platforms
- •Characteristics of the Two Calling Approaches
- •Details of Call Library Function
- •Details of a CIN
- •Calling Shared Libraries
- •Figure 2-1. Call Library Function Dialog Box
- •Calling Conventions (Windows)
- •Parameters
- •Calling Functions That Expect Other Data Types
- •Building a Shared Library (DLL)
- •Task 1: Build the Function Prototype in LabVIEW
- •Task 2: Complete the .c File
- •Required Libraries
- •Task 3: Build a Library Project in an External IDE
- •Figure 2-2. Creating a Project in Visual C++
- •Figure 2-3. Setting the Use run-time library control, Microsoft Visual C++
- •Gnu C or C++ Compilers on Solaris, Linux, or HP-UX
- •Metrowerks CodeWarrior on Power Macintosh
- •Calling External APIs
- •Common Pitfalls with the Call Library Function
- •Incorrect Function Name
- •Data Types
- •Constants
- •Calling Conventions
- •Example 1: Call a Shared Library that You Built
- •Configuration of Call Library Function
- •Create Front Panel
- •Create the Block Diagram
- •Example 2: Call a Hardware Driver API
- •Figure 2-4. VI That Calls Hardware
- •Example 3: Call the Win32 API
- •Table 2-1. Mapping Win32 Data Types to Standard C Data Types
- •Table 2-2. Mapping Win32 Data Types to LabVIEW Data Types
- •Constants
- •Table 2-3. Selected Constants for MessageBox
- •Figure 2-5. Combining Function Constants in LabVIEW
- •Determining the Proper Library and Function Name
- •Unicode Versions and ANSI Versions of Functions
- •Configuring a Call to the Win32 API
- •Figure 2-6. Configuring Call Library Function to call the Win32 API
- •Figure 2-7. Block Diagram for a Call to the Win32 API
- •Figure 2-8. Running a LabVIEW Call to the Win32 API
- •Additional Examples of LabVIEW Calls to DLLs
- •Debugging DLLs and Calls to DLLs
- •Troubleshooting the Call Library Function
- •Troubleshooting your DLL
- •Troubleshooting Checklist
- •Module Definition Files
- •Array and String Options
- •Arrays of Numeric Data
- •String Data
- •Figure 2-9. The LabVIEW String Format
- •Figure 2-10. The Pascal String Format
- •Figure 2-11. The C String Format
- •Array and String Tip
- •Supported Languages
- •Macintosh
- •Microsoft Windows
- •Solaris, Linux, and HP-UX
- •Resolving Multithreading Issues
- •Making LabVIEW Recognize a CIN as Thread Safe
- •Using C Code that is Thread Safe
- •Creating a CIN
- •Step 1. Set Up Input and Output Terminals for a CIN
- •Input-Output Terminals
- •Output-Only Terminals
- •Step 2. Wire the Inputs and Outputs to the CIN
- •Step 3. Create a .c File
- •Step 4. Compile the CIN Source Code
- •Compile on Macintosh
- •Microsoft Windows
- •Solaris 2.x
- •HP-UX and Linux
- •gcc Compiler
- •Step 5. Load the CIN Object Code
- •LabVIEW Manager Routines
- •Pointers as Parameters
- •Debugging External Code
- •DbgPrintf
- •Windows
- •UNIX
- •Passing Parameters
- •Parameters in the CIN .c File
- •Passing Fixed-Size Data to CINs
- •Scalar Numerics
- •Scalar Booleans
- •Refnums
- •Clusters of Scalars
- •Return Value for CIN Routines
- •Examples with Scalars
- •Creating a CIN That Multiplies Two Numbers
- •Passing Variably Sized Data to CINs
- •Alignment Considerations
- •Arrays and Strings
- •Paths
- •Clusters Containing Variably Sized Data
- •Resizing Arrays and Strings
- •SetCINArraySize
- •NumericArrayResize
- •Examples with Variably Sized Data
- •Concatenating Two Strings
- •Working with Clusters
- •Manager Overview
- •Basic Data Types
- •Scalar
- •char
- •Dynamic
- •Memory-Related
- •Constants
- •Memory Manager
- •Memory Allocation
- •Memory Zones
- •Using Pointers and Handles
- •File Manager
- •Identifying Files and Directories
- •Path Specifications
- •File Descriptors
- •File Refnums
- •Support Manager
- •CIN Routines
- •Data Spaces and Code Resources
- •One Reference to the CIN in a Single VI
- •Loading a VI
- •Unloading a VI
- •Loading a New Resource into the CIN
- •Compiling a VI
- •Running a VI
- •Saving a VI
- •Aborting a VI
- •Multiple References to the Same CIN in a Single VI
- •Multiple References to the Same CIN in Different VIs
- •Single-Threaded Operating Systems
- •Multithreaded Operating Systems
- •Code Globals and CIN Data Space Globals
- •Examples
- •Memory Manager Functions
- •Support Manager Functions
- •Mathematical Operations
- •ASCIITime
- •AZCheckHandle/DSCheckHandle
- •AZCheckPtr/DSCheckPtr
- •AZDisposeHandle/DSDisposeHandle
- •AZDisposePtr/DSDisposePtr
- •AZGetHandleSize/DSGetHandleSize
- •AZHandAndHand/DSHandAndHand
- •AZHandToHand/DSHandToHand
- •AZHeapCheck/DSHeapCheck
- •AZHLock
- •AZHNoPurge
- •AZHPurge
- •AZHUnlock
- •AZMaxMem/DSMaxMem
- •AZMemStats/DSMemStats
- •AZNewHandle/DSNewHandle
- •AZNewHClr/DSNewHClr
- •AZNewPClr/DSNewPClr
- •AZNewPtr/DSNewPtr
- •AZPtrAndHand/DSPtrAndHand
- •AZPtrToHand/DSPtrToHand
- •AZPtrToXHand/DSPtrToXHand
- •AZRecoverHandle/DSRecoverHandle
- •AZSetHandleSize/DSSetHandleSize
- •AZSetHSzClr/DSSetHSzClr
- •BinSearch
- •BlockCmp
- •Cat4Chrs
- •ClearMem
- •CPStrBuf
- •CPStrCmp
- •CPStrIndex
- •CPStrInsert
- •CPStrLen
- •CPStrRemove
- •CPStrReplace
- •CPStrSize
- •CToPStr
- •DateCString
- •DateToSecs
- •FAddPath
- •FAppendName
- •FAppPath
- •FArrToPath
- •FCopy
- •FCreate
- •FCreateAlways
- •FDepth
- •FDirName
- •FDisposePath
- •FDisposeRefNum
- •FEmptyPath
- •FExists
- •FFlattenPath
- •FFlush
- •FGetAccessRights
- •FGetDefGroup
- •FGetEOF
- •FGetInfo
- •FGetPathType
- •FGetVolInfo
- •FileNameCmp
- •FileNameIndCmp
- •FileNameNCmp
- •FIsAPath
- •FIsAPathOfType
- •FIsAPathOrNotAPath
- •FIsARefNum
- •FIsEmptyPath
- •FListDir
- •FLockOrUnlockRange
- •FMakePath
- •FMClose
- •FMOpen
- •FMove
- •FMRead
- •FMSeek
- •FMTell
- •FMWrite
- •FName
- •FNamePtr
- •FNewDir
- •FNewRefNum
- •FNotAPath
- •FPathCmp
- •FPathCpy
- •FPathToArr
- •FPathToAZString
- •FPathToDSString
- •FPathToPath
- •FRefNumToFD
- •FRefNumToPath
- •FRelPath
- •FRemove
- •FSetAccessRights
- •FSetEOF
- •FSetInfo
- •FSetPathType
- •FStrFitsPat
- •FStringToPath
- •FTextToPath
- •FUnFlattenPath
- •FVolName
- •GetALong
- •HexChar
- •HiByte
- •HiNibble
- •IsAlpha
- •IsDigit
- •IsLower
- •IsUpper
- •LoByte
- •Long
- •LoNibble
- •LStrBuf
- •LStrCmp
- •LStrLen
- •LToPStr
- •MilliSecs
- •MoveBlock
- •NumericArrayResize
- •Offset
- •PPStrCaseCmp
- •PPStrCmp
- •Printf
- •PStrBuf
- •PStrCaseCmp
- •PStrCat
- •PStrCmp
- •PStrCpy
- •PStrLen
- •PStrNCpy
- •PToCStr
- •PToLStr
- •QSort
- •RandomGen
- •SecsToDate
- •SetALong
- •SetCINArraySize
- •StrCat
- •StrCmp
- •StrCpy
- •StrLen
- •StrNCaseCmp
- •StrNCmp
- •StrNCpy
- •SwapBlock
- •TimeCString
- •TimeInSecs
- •ToLower
- •ToUpper
- •Unused
- •Word
- •Glossary
![](/html/2706/277/html_Wdv5nC5QIH.x6r0/htmlconvd-VvZlG9184x1.jpg)
Chapter 6 Function Descriptions
FGetAccessRights
MgErr FGetAccessRights(path, owner, group, permPtr);
Purpose
Returns access rights information about the specified file or directory.
Parameters
Name |
Type |
Description |
|
|
|
|
|
|
path |
Path |
Path of the file or directory about which you |
|
|
want access rights information. |
|
|
|
owner |
PStr |
Address at which FGetAccessRights |
|
|
stores the owner of the file or directory. |
|
|
|
group |
PStr |
Address at which FGetAccessRights |
|
|
stores the group of the file or directory. |
|
|
|
permPtr |
int32 * |
Address at which FGetAccessRights |
|
|
stores the permissions of the file or directory. |
|
|
Refer to the Pointers as Parameters section |
|
|
in Chapter 3, CINs, for more information |
|
|
about using this parameter. |
|
|
|
Return Value
mgErr, which can contain the following errors:
mgArgErr |
A bad argument was passed to the function. Verify the path. |
FNotFound |
File not found. |
fIOErr |
Unspecified I/O error. |
© National Instruments Corporation |
6-67 |
Using External Code in LabVIEW |
![](/html/2706/277/html_Wdv5nC5QIH.x6r0/htmlconvd-VvZlG9185x1.jpg)
Chapter 6 Function Descriptions
FGetDefGroup
LStrHandle FGetDefGroup(groupHandle);
Purpose
Gets the LabVIEW default group for a file or directory.
Parameters
Name |
Type |
Description |
|
|
|
|
|
|
groupHandle |
LStrHandle |
Handle that represents the LabVIEW default |
|
|
group for a file or directory. If groupHandle |
|
|
is NULL, FGetDefGroup allocates a new |
|
|
handle and returns the default group in it. If |
|
|
groupHandle is a handle, FGetDefGroup |
|
|
returns it, and groupHandle resizes to hold |
|
|
the default group. |
|
|
|
Return Value
The resulting LStrHandle. If groupHandle was not NULL, the return value is the same LStrHandle as groupHandle. If an error occurs, this function returns NULL.
Using External Code in LabVIEW |
6-68 |
www.ni.com |
![](/html/2706/277/html_Wdv5nC5QIH.x6r0/htmlconvd-VvZlG9186x1.jpg)
Chapter 6 Function Descriptions
FGetEOF
MgErr FGetEOF(fd, sizep);
Purpose
Returns the size of the specified file.
Parameters
Name |
Type |
Description |
|
|
|
|
|
|
fd |
File |
File descriptor associated with the file. |
|
|
|
sizep |
int32 * |
Address at which FGetEOF stores the size of |
|
|
the file in bytes. If an error occurs, *sizep is |
|
|
undefined. Refer to the Pointers as |
|
|
Parameters section in Chapter 3, CINs, for |
|
|
more information about using this parameter. |
|
|
|
Return Value
mgErr, which can contain the following errors:
mgArgErr |
Not a valid file descriptor. |
fIOErr |
Unspecified I/O error. |
© National Instruments Corporation |
6-69 |
Using External Code in LabVIEW |
![](/html/2706/277/html_Wdv5nC5QIH.x6r0/htmlconvd-VvZlG9187x1.jpg)
Chapter 6 Function Descriptions
FGetInfo
MgErr FGetInfo(path, infop);
Purpose
Returns information about the specified file or directory.
Parameters
Name |
Type |
Description |
|
|
|
|
|
|
path |
Path |
Path of the file or directory about which you |
|
|
want information. |
|
|
|
infop |
FInfoPtr |
Address where FGetInfo stores |
|
|
information about the file or directory. If an |
|
|
error occurs, infop is undefined. Refer to the |
|
|
Pointers as Parameters section in Chapter 3, |
|
|
CINs, for more information about using this |
|
|
parameter. |
|
|
|
FInfoPtr is a data structure that defines the attributes of a file or directory. The following code lists the file/directory information record, FInfoPtr.
typedef struct {
int32 |
type; |
* system specific file type-- |
|
|
0 for directories */ |
int32 |
creator; |
* system specific file |
|
|
creator-- 0 for folders (on |
|
|
Mac only)*/ |
int32 |
permissions; |
* system specific file access |
|
|
rights */ |
int32 |
size; |
/* file size in bytes (data |
|
|
fork on Mac) or entries in |
|
|
directory*/ |
int32 |
rfSize; |
/* resource fork size (on Mac |
|
|
only) */ |
uint32 |
cdate; |
/* creation date: seconds |
|
|
since system reference time |
|
|
*/ |
uint32 |
mdate; |
/* last modification date: |
|
|
seconds since system ref time |
|
|
*/ |
Using External Code in LabVIEW |
6-70 |
www.ni.com |
|
|
Chapter 6 Function Descriptions |
Bool32 |
folder; |
/* indicates whether path |
|
|
refers to a folder */ |
Bool32 |
isInvisible; |
/* indicates whether file is |
|
|
visible in File Dialog (on |
|
|
Mac only)*/ |
Point |
location; |
/* system specific desktop |
|
|
geographical location (on Mac |
|
|
only)*/ |
Str255 |
owner; |
/* owner (in pascal string |
|
|
form) of file or folder */ |
Str255 |
group; |
/* group (in pascal string |
|
|
form) of file or folder */ |
} |
FInfoRec, *FInfoPtr; |
Return Value
mgErr, which can contain the following errors:
mgArgErr |
A bad argument was passed to the function. Verify the path. |
FNotFound |
File not found. |
fIOErr |
Unspecified I/O error. |
© National Instruments Corporation |
6-71 |
Using External Code in LabVIEW |