Teledyne LeCroy Automation API for Bluetooth Analyzers - Manual (Page 54)

48
Automation API for CATC Bluetooth Analyzers CATC Ver. 1.40
2.4.12 ITrace::AnalyzerErrors
Retrieves trace file errors
Parameters
long error_type – type of error collection you want to retrieve; the following values are
valid:
0x00000001- Loss of Sync
0x00000002- Partial Header
0x00000004- Payload Length Modulo Bad
0x00000008- Payload Length Too Short
0x00000010- Payload Length Too Long
0x00000020 – Payload Missing
0x00000040 – HEC Bad
0x00000080 – CRC Bad
0x00000100 – Uncorrectable FEC errors
analyzer_errors - address of a pointer to the AnalyzerErrors object primary interface
Return values
ANALYZERCOMERROR_INVALIDERROR - invalid error type specified
Remarks
AnalyzerErrors object is created via this method call, if call was successful.
Example
WSH:
CurrentDir = Left(WScript.ScriptFullName, InstrRev(WScript.ScriptFullName,
"\"))
Set Analyzer = WScript.CreateObject("CATC.Merlin")
Set Trace = Analyzer.MakeRecording (CurrentDir & "Input\test_ro.rec")
Set Errors = Trace.AnalyzerErrors (16) ' Payload Length Too Long
C++:
IBTTrace* bt_trace;
. . .
IAnalyzerErrors* analyser_errors;
try
{
analyser_errors = bt_trace->AnalyzerErrors(error_type).Detach();
}
catch ( _com_error& er)
{
if (er.Description().length() > 0)
::MessageBox( NULL, er.Description(), _T("BTAnalyzer client"),
MB_OK );
else
::MessageBox( NULL, er.ErrorMessage(),_T("BTAnalyzer client"),
MB_OK );
return 1;
}
. . .
analyser_errors->Release();
HRESULT AnalyzerErrors (
[in] long error_type,
[out, retval] IAnalyzerErrors** analyzer_errors );