Age1439_status_get, Age1439_status_get” on, Age1439 – Agilent Technologies VXI E1439 User Manual
Page 186: Status_setup_error, Age1439_status

176
Agilent E1439 Programmer's Reference
Functions listed alphabetically
age1439_status_get
Reads status register information for the module.
VXIplug&play Syntax
#include "age1439".h
ViStatus age1439_status_get(ViSession id, ViPInt16 statusPtr);
Parameters
id
is the VXI instrument session pointer returned by the age1439_init function.
statusPtr
points to the status word. The bits are defined below:
Status Bit
Definition
Description
0-1
These two bits indicate the current state of the 
measurement loop. See
“age1439_meas_status_get” on page 156
for more information about these states
2
Passed: This bit is always set to 1
3
This bit is set when the module is ready after power-on. See 
the VXIbus Specifications for more information.
4
This bit is set internally whenever any data has been written 
to the receive FIFO, or read from the transmit FIFO of the 
fiber interface within the past 500 milliseconds, 
approximately. The bit is cleared automatically when activity 
ceases on the fiber interface
5
This bit is set internally whenever an error condition occurs 
on the fiber interface. Reading the status register does not 
clear this bit. To do this, the 
function must be used explicitly. The function
can be used to read the contents of the fiber
error register. If the error is continuously present, the bit will 
not be cleared. 
6
Setup error: An invalid parameter value was requested. If an 
invalid block size was requested, the closest valid block size 
is used until a change to an interrelated parameter makes the 
requested block size valid. If a data resolution, data type, 
filter bandwidth, trigger delay, or filter decimation parameter 
was requested which would result in an inability to make a 
measurement, the previous valid parameter is used until a 
change to an interrelated parameter makes the requested 
parameter valid
7
Sync/Idle Complete: This bit is set when the most recent 
user-initiated Sync or Idle change has propagated through to 
all modules in a system. The change is a result of asserting 
Sync or forcing Idle via the Control Register or issuing a 
meas_control command or function
