Chapter 2 Software
2-17
2.5.13 HlsbGetInt0StatusInfo、HlsbGetInt1StatusInfo
BOOL HlsbGetInt0StatusInfo(HANDLE hlsbHandle, int mkyNo, BYTE *int0Info)
BOOL HlsbGetInt1StatusInfo(HANDLE hlsbHandle, int mkyNo, BYTE *int1Info)
Format
Obtains the information of INT0, INT1 interrupt factor retained in th internal driver
Function
Parameter
Succeeded : TRUE is returned. Failed : FALSE is returned
You can check the details of error factor by executing HlsbGetLastError.
Return value
HLSB_SUCCESS
Terminated normally
HLSB_ERR_INVALID_HANDLE
Invalid hlsbHandle has been specified.
HLSB_ERR_INVALID_PARAM
mkyNo is out of range.
NULL has been specified to *int0Info、*int1Info.
HLSB_ERR_FAILED
The process failed due to unknown reason.
Error code
hlsbHandle
Handle of HLSB-36PCI2
mkyNo
Select MKY36 whose data to obtain. Input condition is the following.
・1 : MKY36#1, 2:MKY36#2
*int0Info、*int1Info
Pointer to the storage byte area of obtained interrupt factor
Information of interrupt factors which has been occurred are accumulated.
[Note]
The configuration of parameters set to int0Info, int1Info is shown in Table 2-4.
When interrupt has occurred, the bit which corresponds to its factor turned to "1".
The arrangements of interrupt factors are same as the lower 8bit in INT0R and INT1R of MKY36.
bit
Interrupt factor
7
An interrupt occurs when scanning stops.
6
An interrupt occurs when CHECK-2 occurs.
5
An interrupt occurs when CHECK-1 occurs.
4
An interrupt occurs when DREQ is generated from satellite IC.
3
An interrupt occurs when a period of scan finished.
2
An interrupt occurs due to DR2 function.
1
An interrupt occurs due to DR1 function.
0
An interrupt occurs due to DR0 function.
Table 2-4 Internal configuration of int0Info and int1Info