Skip to main content

Download ScanaStudio

Windows

x64 installer · portable archive
v6.0.28 - 2026-10-22

Linux

x86_64 tarball
v6.0.28 - 2026-10-22

macOS

universal disk image
v6.0.28 - 2026-10-22

Windows USB drivers

Install these once, before connecting your device. This is the only Ikalogic installer that needs administrator rights — ScanaStudio itself installs per-user and never prompts for UAC.

Download drivers

First launch on macOS

The disk image is signed but not yet notarized by Apple. The first time you open ScanaStudio, right-click the application and choose Open, then confirm. Double-clicking it instead makes Gatekeeper refuse to run it — the download is not broken.

ScanaStudio license agreement

By downloading and using ScanaStudio, you agree to the Ikalogic Software License Agreement.

Looking for ScanaStudio V5?

The releases above are ScanaStudio V6. For older V5 releases and their release notes, click here.

About ScanaStudio

ScanaStudio is the software used to interface with all Ikalogic logic analyzers and pattern generators. At the core of its design philosophy is the belief that powerful test and measurement tools should remain intuitive and accessible. Since all our devices are computer-connected - with no built-in displays or controls - ScanaStudio serves as the central platform where engineers interact with their instruments. Whether you're capturing signals, decoding protocols, triggering on complex events, or generating test patterns, ScanaStudio offers a clean and efficient workflow. We’ve invested significant effort into creating a user interface that feels modern and frustration-free - allowing engineers to focus on debugging and validating designs, not wrestling with complicated software.

ScanaStudio v6 capturing on an SP259, decoding I2C and 1-Wire, and measuring between two markersScanaStudioSP259 demo✕+⚙?▶ Start captureDevice▾DeviceSP259Sample rate250 MS/sResolution4 nsCapture length100 MLogic level3.3 VTrigger▸Protocols▾No protocol yet.+ Add new…Views▾Packet ViewHex ViewRaw ViewMeasures ViewMarkers ViewLog ViewAnnotations▾Add markerAdd standard measureShow/hide annotations0 s2 ms4 ms6 ms8 msUART TXCH1UART RXCH2PWMCH31-Wire DQCH4I2C SCLCH5I2C SDACH6An SP259 on the benchIdleSP259 (demo)Sampling rate: 250 MS/s (4 ns)Captured: 100 M

Developer SDK

Drive your instruments from your own code. The Python, NodeJS and Rust clients are installed from their package registries; the C library is downloaded here. See the ScanaStudio SDK documentation to get started.

ScanaStudio C API

One cross-platform archive: include/scanastudio.h, an example, and the prebuilt libraries for Windows (x86_64), Linux (x86_64) and macOS (universal). There is no per-platform download to choose from.

Download scanastudio-c-0.2.13.zip
v0.2.13 — 2026-10-22
sha256 b3689fc384709dc4932260f1ad0daab67e6fc9f0fba720f9403f823e27c9c40a

The C library carries its own version number and is released independently of the ScanaStudio application.

Release Notes

6.0.28 (2026-10-22)

fiximprovement
  • on the SP259 and SP259i, a protocol trigger (a UART byte, for example) no longer misses its frame when the traffic just before it partly matched it
  • SP259 firmware 10

6.0.27 (2026-10-22)

fix
  • on the SP259 and SP259i, a second capture no longer hangs until the device is unplugged (a regression in 6.0.26)

6.0.26 (2026-10-21)

featurefiximprovement
  • decoder scripts can build protocol triggers
  • the pattern generator shows when a pattern is being built
  • crash reports now carry a stack trace for native faults and freezes
  • on the SP1000G, a stopped state clock no longer wedges the USB link
  • on the SP1000G, a capture reports the depth it actually reached, not only its last 50 ms
  • on the SP1000G, state captures no longer repeat samples at the end of a burst
  • on the SP1000G, an external trigger now sets the other trigger engine aside
  • on the SP1000G, a capture on the 10 MHz IN timebase is refused when no usable 10 MHz signal is present
  • on the SP1000G, the device is reopened correctly after a firmware reboot
  • on the SP259, the USB link is flushed before a capture, so an interrupted capture no longer leaves stale data behind
  • the interface no longer stalls while a long pattern is being counted
  • SP1000G firmware: controller 0.16.303, core 0x19

6.0.25 (2026-10-18)

featurefiximprovement
  • SP1000G timebase (internal or external), TRIG OUT polarity and TRIG IN threshold capture settings
  • SP1000G probe serial numbers, shown under the probe name
  • on the SP1000G, closing a workspace that ran the pattern generator no longer makes the next capture fail with "interface is busy" or wait 5 s
  • a portable copy can open its script library, autosave and logs folders again
  • a malformed or out-of-range protocol command is now reported instead of silently taking a default
  • SP1000G controller firmware 0.15.298

6.0.24 (2026-10-16)

fix
  • the "server unreachable" notice no longer flashes at start-up while the server is still launching, and no longer restarts a server that is still booting

6.0.23 (2026-10-15)

featureimprovementfix
  • SP259 and SP259i trigger loopback test for production benches — with TRIG OUT shorted to TRIG IN, a capture started with ext_trig_test fires its external trigger through the short (refused on other devices)
  • a Memory View per decoder, showing what a script reads out of the target, with selection, copy as raw bytes and a choice of byte order
  • pattern generator scripts can pause and resume, a decoder can resume or stop the generator, and the generator's console reaches the log as it writes
  • a script names the channels it drives, and asks before using them
  • the marker snap is a setting, with a key that reverses it while held
  • SP209 rev A firmware is checked and updated like the other revisions
  • SP259 firmware version 9 and SE254 firmware version 4
  • views open themselves when new data arrives, and a closed one is flagged instead
  • the SQ mode names every wiring it cannot run, offers to fix it, or offers the other mode
  • a workspace and its detached views are named after their file
  • the Log View scrolls smoothly through long logs, gives each line of a multi-line entry its own row, and stamps lines to the millisecond
  • a P992 channel shows its own threshold in its header
  • the dialogs share one behaviour: Escape cancels, a click beside them closes nothing, and the draggable ones drag
  • a stop pressed while a capture is still preparing cancels it, and a start sent while another is on its way is answered
  • a capture start waits for the device to be read instead of failing
  • a trigger step with an unknown cell is refused instead of being read as "don't care"
  • an SP259 capture cut short no longer leaves unread data behind for the next one
  • SP1000G resumed acquisitions placed their sync edge where the levels start
  • a generation stopped mid-start no longer freezes the generator, huge repeats play in full, and closing a workspace stops its generation
  • a generator configuration that became invalid refuses the capture instead of running it
  • generator marks are kept in a saved workspace
  • a load, save or export is answered only after its events, and only to the client that asked
  • a crashed worker thread is reported instead of hanging the workspace

6.0.22 (2026-10-05)

fix
  • on macOS, the server was stopped by the system as soon as an SP209 was opened, so no capture could start
  • on older macOS versions, parts of the waveform overlay (minimap, markers, gauges) were not drawn

6.0.21 (2026-10-05)

fix
  • on macOS, no SP209, SP259, SP1000G or ScanaQuad was detected, because macOS refused to load the USB libraries shipped with the application

6.0.20 (2026-10-04)

fiximprovement
  • on macOS and Linux, an SP209, SP259, SP1000G or ScanaQuad could go undetected because the server did not find the USB libraries installed with the application
  • when a USB library cannot be loaded, the log now says why and where it was looked for

6.0.19 (2026-10-03)

featurefix
  • a script that needs to open a file outside its own folder now asks for permission, naming the script and the path, instead of failing silently
  • on macOS the SP209 and SP209i were never detected, and only the demo device was offered
  • on Ubuntu 22.04, Debian 12 and RHEL 9, SP209 and ScanaQuad devices were not listed, because the bundled FTDI library needed a newer system than these provide
  • on Linux, an SP209i that presents itself as a plain FTDI chip could be listed but not opened
  • on Windows, the application could not start its server on a machine without the Microsoft Visual C++ runtime
  • on the SE254, after a capture was stopped while waiting for its trigger, later captures never triggered