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

Chapter 6 NI-FBUS Function Reference
When the NI-FBUS Communications Manager interface receives an alert, the
parameter is filled in with the information about the
aldata
form of
aldata->alertData
aldata->alarmOrEventName
caused the alert.
and the block of the alarm, respectively.
nifWaitAlert2
alert was received. Note that this is a separate step from alert acknowledgment, which must
be carried out for alarms using
If you have multiple threads waiting to receive the same alert, the NI-FBUS Communications
Manager sends a copy of the alert to all the waiting threads. Your application must ensure that
only one thread acknowledges any one alarm with a call to
abort a pending
The
alertType
or
ALERT_STANDARD_DIAGNOSTICS
nifAlertData2_t
typedef struct nifAlertData2_t{
uint8 alertType;
char deviceTag[TAG_SIZE + 1];
char blockTag[TAG_SIZE + 1];
char alarmOrEventName [TAG_SIZE + 1];
uint8 alertKey;
uint8 standardType;
uint8 mfrType;
uint8 messageType;
uint8 priority;
uint8 reserved[3];
nifTime_t timeStamp;
union {
nifAlertAnalogData_t analog;
nifAlertDiscreteData_t discrete;
nifAlertUpdateData_t update;
nifAlertStandardDiagnosticsData_t stdDiag;
} alertData;
} nifAlertData2_t;
typedef struct nifAlertAnalogData_t {
uint16
float
uint32
uint16
NI-FBUS Hardware and Software User Manual
depends on the value of
is the name of the alarm parameter or event parameter that
aldata->deviceTag
sends a confirmation to the device, informing the alerting device that the
nifAcknowledgeAlarm
call by closing the descriptor on which the call was made.
nifWaitAlert2
parameter can be
ALERT_ANALOG
is defined as follows:
subCode;
value;
relativeIndex;
unitIndex;
aldata->alertType
and
aldata->blockTag
.
nifAcknowledgeAlarm
,
ALERT_DISCRETE
.
6-62
. The
aldata
.
are the tags of the device
,
ALERT_UPDATE
. You can
, or
ni.com