Chapter 6
NI-FBUS Function Reference
NI-FBUS Hardware and Software User Manual
6-30
ni.com
nifError_t
nifGetObjectAttributes(
nifDesc_t ud,
NIFB_BLOCK_INDEX_SUBINDEX(char *blocktag, uint32
idx,
uint32 subidx),
nifAttributes_t *attr)
nifError_t
nifGetObjectAttributes(
nifDesc_t ud,
NIFB_NAME_SUBINDEX(char *name, uint32 subidx),
nifAttributes_t *attr)
nifError_t
nifGetObjectAttributes(
nifDesc_t ud,
NIFB_BLOCK_NAME_SUBINDEX(char *blocktag, char
*name,
uint32 subidx), nifAttributes_t *attr)
Input
ud
The descriptor (of any type if by name; VFD or block if by index).
name
Name of the object you need the device description attributes of,
in
BLOCKTAG.PARAM
form. To specify a structure element by
name, specify the name in
BLOCKTAG.STRUCT.ELEMENT
format.
Refer to Table 6-5 for an explanation of how to use macros to
specify the object.
Output
attr
Object attribute values read from the DDOD (Device Description
Object Dictionary). The type
nifAttributes_t
consists of a
data structure including a type code which selects from a list of
structures, one for each type of object. Other information,
including whether individual attributes were successfully
evaluated and whether individual attributes are dynamic (meaning
they could change) also is provided. The structure is too long to be
included in this chapter. You can find it in the NI-FBUS
Communications Manager header files.
Context
Session, block, VFD, physical device, link.
Description
The NI-FBUS Communications Manager reads the device description object attributes
identified in the call from the DDOD associated with
ud
and returned in
attr
. Notice that the
object attributes describe certain characteristics of the object, but do not contain the object
value. The device description object attributes also differ in content from the FMS Object
Description of the object.
