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

Chapter 6 NI-FBUS Function Reference
nifWaitAlert
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
nifAlertData_t
typedef struct nifAlertData_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;
nifTime_t timeStamp;
uint16 subCode;
uint16 unitIndex;
union {
float floatAlarmData;
uint8 discreteAlarmData;
uint16 staticRevision;
} alertData;
} nifAlertData_t;
Return Values
E_OK
E_INVALID_DESCRIPTOR
E_OBSOLETE_DESC
E_SERVER_CONNECTION_LOST
NI-FBUS Hardware and Software User Manual
sends a confirmation to the device, informing the alerting device that the alert
nifAcknowledgeAlarm
call by closing the descriptor on which the call was made.
nifWaitAlert
parameter can be
ALERT_ANALOG
is defined as follows:
The call was successful.
The descriptor you gave is invalid.
The input descriptor is no longer valid. It was closed before
nifWaitAlert
The session established with the NI-FBUS Communications
Manager for this descriptor has been closed or lost.
.
nifAcknowledgeAlarm
,
ALERT_DISCRETE
completed.
6-60
. You can
, or .
ALERT_UPDATE
ni.com