Logic 2.x Instructions

First, click the options button at the bottom-right of the software, and select "Preferences."

Then, in the Preferences window, scroll to the bottom until you reach the Custom Low Level Analyzers section.

Use the browse button to select the directory that contains your compiled custom protocol analyzer.

• Windows -> .dll

• Linux -> .so

• MacOS -> .dylib

Finally, save the dialog and restart the software. Your custom analyzer should now appear in the list of available protocol analyzers!

Logic 2 MacOS Instructions

If you see the following error after restarting the software on MacOS, please follow these extra steps.

Failed to load custom analyzer... Unable to load library...

1. Open the Terminal (open Spotlight -> search "Terminal" -> press enter)

2. navigate to the directory containing your custom analyzer (e.g. cd ~/Downloads/mylla)

3. run the following command, replacing libYourCustomAnalyzer.dylib with your analyzer's file name:

   install_name_tool -change @executable_path/libAnalyzer.dylib @rpath/libAnalyzer.dylib libYourCustomAnalyzer.dylib

4. close the terminal, and open the Logic 2 application again.

This will change how the custom analyzer library locates the libAnalyzer.dylib library, which has a different relative path than the older Logic 1.x software.

You may see the same error on Linux or Windows. If this happens, there may be a problem with the custom analyzer you are trying to load. Please contact the analyzer author or Saleae support.

Logic 1.x Instructions

These instructions show how to set up the Saleae software to load custom protocol analyzers.

• First, open the Options menu and select Preferences.

• Navigate to the Developer tab and click Browse in the "Search this path..." section.

• Browse to the location where the .dll, .so, or .dylib analyzer library is stored.

• Click "Select Folder"

• Save the preferences.

• Close the software. Custom analyzers won't be loaded until the software is restarted.

Can't Find the Options Button?

Please refer to the article below. You may be running an older version of our software.

​