National Instruments FOUNDATION NI-FBUS Hardware And Software User Manual page 93

For block, VFD, physical device, or link descriptors, the object name may refer to a variable
or a variable list. You normally would use
description of a certain data type.
Refer to Table 6-5 for an explanation of how to use macros to specify the object.
For more detailed information concerning the
Chapter 3, Using ddi_get_item, of the Fieldbus Foundation Device Description Services
User Guide.
After a successful call to
Note
nifFreeObjectAttributes
will not free up memory correctly if it does not perform this operation.
Return Values
E_OK
E_CONFIG_ERROR
E_INVALID_DESCRIPTOR
E_SYMBOL_FILE_NOT_FOUND
E_SM_NOT_OPERATIONAL
E_NOT_FOUND
E_MULTIPLE
E_ORDINAL_NUM_OUT_OF_RANGE
E_OBSOLETE_DESC
E_SERVER_CONNECTION_LOST
© National Instruments Corporation
nifGetObjectAttributes
nifAttributes_t
nifGetObjectAttributes
when it is done using the
The call was successful.
Some configuration information, such as registry information or
network configuration information, is incorrect.
The device descriptor does not correspond to a VFD or block.
The NI-FBUS Communications Manager could not find the
symbol file.
The device is present, but cannot respond because it is at a default
address.
The referred object does not exist, or it does not have object
attributes.
The NI-FBUS Communications Manager found more than
one identical tag; the function failed.
The ordinal number is out of the device range.
The input descriptor is no longer valid. It was closed before
nifGetObjectAttributes
The session established with the NI-FBUS Communications
Manager for this descriptor has been closed or lost.
6-31
Chapter 6 NI-FBUS Function Reference
to read the type
structure, refer to
, your application must call
structure. Your application
attr
completed.
NI-FBUS Hardware and Software User Manual