FrameV2 / HLA Support - Analyzer SDK

Search…
The C++ analyzer SDK was created before our new, python high level analyzers were introduced.
High level analyzers allow for new analyzers to be created, which instead of processing the raw input signals recorded by the device, instead process frames produced by C++ analyzers.
When the HLA system was introduced, only a handful of Saleae created protocol analyzers produced results that could be passed into the HLA system.
However, as of Saleae Logic 2.3.43, released in early 2022, it is now possible for custom 3rd party C++ analyzers to produce results that can be then interpreted by HLAs. This requires C++ analyzers to be updated to use the new "FrameV2" API.
The FrameV2 API does not completely replace the existing "Frame" class and collection yet. The existing "Frame" class is still exclusively used to produce the displayed bubbles, and for the analyzer-specific export feature. However, If a C++ analyzer uses FrameV2, these new objects will be available to HLAs.
Additionally, FrameV2 objects replace the original Frame objects in the data table, allowing for multiple, user configurable columns, as well as a variety of data formats.
Using FrameV2
Requirements:
1.Make sure you're using the latest version of the Analyzer SDK. The newest version of the Analyzer SDK contains the new public method UseFrameV2 in the Analyzer.h header file.
2.Make sure you're using the Latest Logic software, 2.3.43 or newer. Note, analyzers that support FrameV2 cannot be loaded in older versions of the application.
3.This example assumes you already have a working C++ Analyzer, and just want to add FrameV2 support.
Usage example:
1
// Example taken from the async-rgb-led-analyzer
2
// https://github.com/saleae/async-rgb-led-analyzer/blob/alpha/src/AsyncRgbLedAnalyzer.cpp
3
​
4
// Step 1: add UseFrameV2 to your constructor.
5
AsyncRgbLedAnalyzer::AsyncRgbLedAnalyzer() : Analyzer2(), mSettings( new AsyncRgbLedAnalyzerSettings )
6
{
7
    SetAnalyzerSettings( mSettings.get() );
8
    // Add this line to your Analyzer constructor!
9
    UseFrameV2();
10
}
11
​
12
// Step 2: Create FrameV2 objects
13
// The following code goes wherever you already create and add Frame objects.
14
// Example existing Frame V1 code.
15
// Don't delete yours! It's still used to display the bubbles on the graph.
16
Frame frame;
17
frame.mFlags = 0;
18
frame.mStartingSampleInclusive = result.mValueBeginSample;
19
frame.mEndingSampleInclusive = result.mValueEndSample;
20
frame.mData1 = result.mRGB.ConvertToU64();
21
frame.mData2 = frameInPacketIndex++;
22
mResults->AddFrame( frame );
23
​
24
// New FrameV2 code.
25
FrameV2 frame_v2;
26
// you can add any number of key value pairs. Each will get it's own column in the data table.
27
frame_v2.AddInteger( "index", frame.mData2 );
28
frame_v2.AddInteger( "red", result.mRGB.red );
29
frame_v2.AddInteger( "green", result.mRGB.green );
30
frame_v2.AddInteger( "blue", result.mRGB.blue );
31
// This actually saves your new FrameV2. In this example, we just copy the same start and end sample number from Frame V1 above.
32
// The second parameter is the frame "type". Any string is allowed. 
33
mResults->AddFrameV2( frame_v2, "pixel", frame.mStartingSampleInclusive, frame.mEndingSampleInclusive );
34
​
35
// You should already be calling this to make submitted frames available to the rest of the system. It's still required.
36
mResults->CommitResults();
Copied!
Screenshots:
Once you have added UseFrameV2(), and start Adding FrameV2s, you will see them in the data table like this.
API Documentation
UseFrameV2();
Call from the constructor one time to register your Analyzer as using FrameV2 objects. Without this, the V1 Frame objects will be displayed in the data table, and you will not be able to use your C++ Analyzer with HLAs.
FrameV2 Methods
The new FrameV2 class declaration can be viewed here: https://github.com/saleae/AnalyzerSDK/blob/fc2fd81512a0c3d97a516b7f52b8c73fbd404889/include/AnalyzerResults.h#L14​
1
// used for adding a string to the FrameV2.
2
void AddString( const char* key, const char* value );
3
// used for adding a double to the FrameV2
4
void AddDouble( const char* key, double value );
5
// used for adding a signed, 64 bit integer to the FrameV2
6
// Note, when the data table shows integers in HEX mode, all leading zeros will be displayed.
7
// For data displayed as HEX, AddByteArray is preferred.
8
void AddInteger( const char* key, S64 value );
9
// used for adding a boolean to the FrameV2
10
void AddBoolean( const char* key, bool value );
11
// used for adding a single byte to the FrameV2
12
void AddByte( const char* key, U8 value );
13
// used for adding a byte array to the FrameV2. The byte array is copied.
14
void AddByteArray( const char* key, const U8* data, U64 length );
Copied!
​
Usage from an HLA
Before writing your own HLA, you can test your C++ Analyzer using the "LLA Frame V2 Tester" available in the marketplace. It's a simple utility which converts the key value pairs from the connected C++ analyzer into JSON objects, for easy inspection.
Check out our HLA data format documentation:
HLA - Analyzer Frame Format
Learn more about building HLAs here:
High-Level Analyzer (HLA) Extensions
1
// In your HLA, you could decode the FrameV2 objects created above like so:
2
    def decode(self, frame):
3
        if frame.type == 'pixel':
4
            print(frame.data['index'])
5
			print(frame.data['red'])
6
			print(frame.data['green'])
7
			print(frame.data['blue'])
Copied!
Protocol Analyzer SDK
Rename a Custom Analyzer
Last modified 5mo ago
Copy link
Edit on GitHub
Contents
Using FrameV2
API Documentation
Usage from an HLA