6 board status functions – Sensoray Smart A/D User Manual
Page 10

S
ENSORAY
I
NSTRUCTION
M
ANUAL
S
MART
A/D D
RIVER
FOR
W
INDOWS
Page 8
3.6 Board Status Functions
3.6.1 GetFaultFlags()
Function:
Returns a set of bit flags that indicate various fault conditions. This function may be called at any time after
SetBoardAttr()
has been called for the target board.
Prototype:
long GetFaultFlags( long hBD );
Example:
///////////////////////////////////////////////////////////////////////////
// Fetch all fault flags from board number 2.
///////////////////////////////////////////////////////////////////////////
long faults = GetFaultFlags( 2 );
Parameter
Type
Description
hBD
long
Board handle.
return value
long
Zero or more active-high bit flags, specified by the following masks:
0x00000001
Driver failed to receive expected data from board.
The onboard CPU has failed to return data in response to a command. In
the case of non-PCI models, this is often caused by an address conflict
with some other device.
0x00000002
Driver could not send command to board.
The onboard CPU has failed to accept a command. In the case of
non-PCI models, this is often caused by an address conflict with some
other device.
0x00000004
Persistent fault condition.
The board’s Fault LED either never turns on or is turned on all the time.
In the case of non-PCI models, this is sometimes the result of an address
conflict with some other device.
0x00000008
Driver failed to open.
This is usually caused by a missing or unregistered software component.
Make sure all driver software components are properly installed and
registered (see
Installation instructions above).
0x00000010
Driver function SetBoardAttr() failed to register board.
In the case of non-PCI models, this is usually caused by incorrect
specification of the base I/O address or a hardware conflict with some
other device in the system. In the case of PCI and CompactPCI models,
this is usually an indication of a board that has not been properly
detected by the BIOS. For PCI models, try terminating all applications,
then performing a hard reset and reboot.