Discounts are available for students, enthusiasts, and small startups. Learn More >

Logic 8

8

100 MS/s

Maximum sample rate for three (3) digital and zero (0) analog channels in use. For other combinations, see Performance Calculator.

10 MS/s

Maximum sample rate for two (2) analog and zero (0) digital channels in use. For other combinations, see Performance Calculator.

USB 2.0

Black

Black

Red

Shipping to

Logic Pro 8

8

500 MS/s

Maximum sample rate for six (6) digital and zero (0) analog channels in use. For other combinations, see Performance Calculator.

50 MS/s

Maximum sample rate for five (5) analog and zero (0) digital channels in use. For other combinations, see Performance Calculator.

USB 3.0

Also works with USB 2.0, with an approximate 7x reduction in performance.

Red

Black

Red

Shipping to

Logic Pro 16

16

500 MS/s

Maximum sample rate for six (6) digital and zero (0) analog channels in use. For other combinations, see Performance Calculator.

50 MS/s

Maximum sample rate for five (5) analog and zero (0) digital channels in use. For other combinations, see Performance Calculator.

USB 3.0

Also works with USB 2.0, with an approximate 7x reduction in performance. By default, Logic Pro 16 will only enable 8 channels to comply with the USB 2.0 power specification. This can be overridden in the software, under Options->Preferences.

OSX Analyzer SDK Xcode Setup

This guide was written using the 1.1.32 Analyzer SDK, Xcode version 7.2.1, and OSX 10.10.5. However, it is likely to work with other versions as well.

Start Xcode

Click "Create a new Xcode project"

Select "Other" from the left column and "Empty" from the templates list.

Click Next.

Enter a name for your Xcode Project.

The location should be set to the analyzer SDK folder recently downloaded, "SaleaeAnalyzerSdk-1.1.32". Do not create a new folder; that will be done for you by Xcode.

Click "Create"

Back in Finder, copy the file "rename_analyzer.py" and "source" from the downloaded SDK directory into the freshly created folder, which will have the same name as your new analyzer. Shown here, the name is "XcodeAnalyzer."

Open a terminal and browse to the new project folder in the downloaded SDK folder.

Run the python script with:

python rename_analyzer.py

First, it will prompt you for the class prefix for all of the source files. All classes and files will be renamed with this prefix. If you type "I2C", the classes and files will be named with "I2CAnalyzer". Please avoid using analyzer in this name, as it will get repeated like this: "I2CAnalyzerAnalyzer".

Second, it will ask you for the name to display to the user in the "Add Analyzers" menu. This should be the user facing name and can include spaces.

Next, we need to add a target to the Xcode project. Be sure the project is selected in the Project Navigator on the left. Then click the menu highlighted below to add a target.

This is the target menu.

Select "Framework & Library" under "OS X" in the left column, and select "Library" in the main area.

Click Next.

Enter a product name. We recommend the same name as the project since there will only be one product.

Be sure to select the folder where the debug version of the custom analyzer is saved.

Once the Saleae logic software has been configured and has been closed, click Run from Xcode.

The Saleae software should launch a few seconds later. Click the "+" button on the analyzers panel and then select your analyzer. In this case, the user facing name of the analyzer was set by the Python script to "Xcode Analyzer". Yours may be different.

If your analyzer is missing, it could indicate that the dylib was not created or that the developer path was not set properly. Please review the previous steps for any possible errors.

Here is your fresh new analyzer, now added to the software. Note that our breakpoint hasn't fired yet. If you had captured data previously, it might fire now, since analyzers will automatically start processing if they are added to an existing analyzer.

Press Start to start a simulation.

Since your analyzer has already been added, the simulator will call your simulation data generator code. The analyzer also starts processing the moment data has been captured, so your break point should fire immediately.

Here you can see that the debugger was attached and your break point has been hit. You can examine variables, set new break points, or press Continue from the debug menu at the bottom.

Congratulations! You now have an Xcode project you can use to develop a custom analyzer for the Saleae software.