4.11
TRACe Susbsystem
4-33
4.11.
TRACe Susbsystem
4.11.1. BisTracData
•
Function name long BisTracData
•
Usage
Writes specified trace data
•
Argument
[IN] long lngPID
long lngTr
// Packet ID (specifies the value acquired
// by BisOpenPacket)
// Trace number
// (Analysis channel: specified with
// BIS_TRACx_xxx)
long lngStrP
// A start point (0 to 1600)
long lngStpP
// An end point (0 to 1600)
float * fltBuff // A data array pointer
long lngSize
// Total bytes of the data to be written
•
Return value
0: Normal
1: The IngStrP and IngStpP argument is incorrectly specified.
Other: Refer to Section
•
Description
Specified trace data is written into the R3755x/R3760.
For CAL data, specify a double-sized array where "Real" data is saved first, fol-
lowed by "Imag" data.
4.11.2. QryTracData
•
Function name long QryTracData
•
Usage
Reads specified trace data
•
Argument
[IN] long lngPID
long lngTr
// Packet ID (specifies the value acquired
// by BisOpenPacket)
// Trace number
// (Analysis channel: specified with
// BIS_TRACx_xxx)
long lngStrP
// A start point (0 to 1600)
long lngStpP
// An end point (0 to 1600)
float * fltBuff // A data array pointer
•
Return value
Normal (0: BIS_TRUE) or error (1: BIS_FALSE)
•
Description Specified trace data is read from the R3755x/R3760.
For CAL data, "Real" data is saved first, followed by "Imag" data. Therefore, a
double-sized array must be provided.
•
Note
Provide a large enough capacity for the memory (on the application side) where
the data is to be saved. API functions do not check the amount of available
memory where the data is to be saved.
The memory data may be damaged if the array size differs.