Getting Started with Acute Test Instruments

What Is in the Box

Acute instruments ship with a consistent set of accessories, though specifics vary by model:

• The instrument (TravelLogic, TravelBus, MSO3000, LA4000, or other model)
• USB cable (USB 3.0 Type-A to Type-B or Type-C, depending on the model)
• Logic analyzer probe cables with grabber clips (for logic analyzer and MSO digital channels)
• Ground leads (short spring-ground tips and longer fly-wire leads)
• Calibration certificate
• Quick start card with download URL for the software

For MSO and TravelBus models, the box also includes oscilloscope probes for the analog channels. For the LA4000 and LA3000 bench models, a power supply is included (portable models like TravelLogic and TravelBus are USB-powered and do not require an external supply).

Check that all listed accessories are present before proceeding. If anything is missing, contact Acute North America support.

Software Download and Installation

System Requirements

• Operating system: Windows 10 (64-bit) or Windows 11 (64-bit). A native Linux app (beta) is also available for several product families: TravelBus, TravelLogic, MSO3000, TravelScope, and BusFinder / LA4000.
• USB: USB 3.0 port required (USB 2.0 will work for connection but limits data transfer speed)
• Disk space: Approximately 500 MB for the full installation
• RAM: 8 GB minimum, 16 GB recommended for large captures

Installation Steps

1. Visit the Acute North America downloads page and download the latest version of the Acute software package.
2. Run the installer executable. If Windows SmartScreen presents a warning, click More info > Run anyway — the installer is not code-signed through the Microsoft Store but is safe.
3. Follow the installation wizard. The default installation directory is fine for most setups.
4. During installation, the wizard installs USB device drivers. If Windows asks to confirm driver installation, click Install.
5. After installation completes, do not launch the software yet — connect the instrument first.

Driver Verification

After installation, you can verify the drivers are installed correctly:

1. Open Device Manager (right-click the Start button > Device Manager).
2. Look under Universal Serial Bus controllers or a dedicated Acute category.
3. The instrument should not appear with a yellow warning triangle. If it does, right-click and select Update driver > Search automatically.

Connecting the Instrument

USB 3.0 Connection

1. Connect the USB cable between the instrument and your PC. Use a USB 3.0 port (typically identified by a blue insert inside the connector) for best performance.
2. For TravelLogic and TravelBus: The instrument powers on automatically when USB is connected. An LED indicator on the instrument confirms power.
3. For LA4000 and MSO3000: Connect the power supply first, then the USB cable. Power on the instrument using its front panel switch.
4. Windows will detect the instrument and load the drivers installed earlier. This takes a few seconds on the first connection.

Verifying the Connection

Launch the Acute software. The status bar at the bottom of the window should display the connected instrument model and serial number. If the status bar shows “No device connected”:

• Try a different USB port (preferably directly on the PC, not through a hub).
• Try a different USB cable.
• Confirm the instrument is powered on (LED indicator lit).
• Reboot the PC if drivers were just installed for the first time.

Your First Capture

This walkthrough uses a TravelLogic as the example, but the software interface is the same for all Acute instruments.

Step 1: Connect Probes to a Target

For this first capture, connect to any active digital signal on your target board. A UART TX line, an I2C bus, or even a blinking LED GPIO will work. Connect:

• One or more signal probe clips to the target signal(s).
• A ground lead to the target board’s ground. Use the shortest available ground connection for best signal quality.

Step 2: Configure Channels

In the Acute software:

1. Click the channel configuration panel on the left side of the screen.
2. Enable the channels you have physically connected. Disable unused channels — this can improve sample rate on some models by allocating bandwidth to fewer channels.
3. Set the threshold voltage to match your target’s logic levels:
   • 3.3V logic: set threshold to 1.5V
   • 1.8V logic: set threshold to 0.9V
   • 5V logic: set threshold to 2.5V

Step 3: Set Sample Rate and Memory Depth

• For a first capture, start with Auto mode if available, or manually set 100 MS/s. This is sufficient for most protocols up to a few MHz.
• Set the memory depth to a moderate value. The default is usually appropriate for initial captures.
• Set the trigger position to 50% (center), giving you equal pre-trigger and post-trigger capture.

Step 4: Set the Trigger

For the simplest first capture, use a basic edge trigger:

1. Select the trigger channel (the channel connected to your signal).
2. Set the trigger type to Falling Edge or Rising Edge.
3. This tells the analyzer to start recording when it sees the specified edge.

Alternatively, select Auto trigger mode, which captures data continuously and displays the most recent buffer — useful when you just want to see what is on the bus.

Step 5: Run the Capture

Click the Run button (or press the keyboard shortcut). The analyzer arms, waits for the trigger condition, captures data into memory, and displays the waveform. You should see digital signal transitions on the active channels.

Use the mouse scroll wheel to zoom in and out. Click and drag to pan through the capture. The time axis at the top shows absolute timing. Cursor markers can be placed by clicking on the waveform to measure time intervals between events.

Setting Up Basic I2C Decode

With a successful first capture under your belt, set up protocol decoding. I2C is a good starting point because it requires only two channels and is present on nearly every embedded board.

Physical Setup

Connect two analyzer channels to SDA and SCL on your target board. Connect ground. Set the threshold voltage to match the I2C bus voltage.

Decode Configuration

1. Open Protocol > I2C Decode.
2. Assign the SDA channel and the SCL channel from the dropdown menus.
3. Set the address mode to 7-bit (the most common configuration).
4. Click OK to apply.
5. Run a new capture.

The waveform display now shows decoded I2C annotations overlaid on the raw signals: START conditions, device addresses with R/W bits, data bytes in hex, ACK/NACK status, and STOP conditions. Each field is color-coded for readability.

Interpreting the Decode

• Green address field: The 7-bit address and R/W bit. Compare to your device’s datasheet address.
• Blue data bytes: The payload. For a register read, the first byte after a write-address is typically the register pointer, and subsequent read bytes are the register contents.
• ACK (A): Device acknowledged the byte.
• NACK (N): Device did not acknowledge. On an address byte, this means no device responded at that address.

Setting Up Basic SPI Decode

SPI is the second most common protocol you will encounter. It requires 3-4 channels.

Physical Setup

Connect analyzer channels to:

• CLK (SPI clock)
• MOSI (Master Out, Slave In) — also called SDO, COPI, or SI depending on the convention
• MISO (Master In, Slave Out) — also called SDI, CIPO, or SO
• CS# (Chip Select, active low) — optional but strongly recommended

Decode Configuration

1. Open Protocol > SPI Decode.
2. Assign CLK, MOSI, MISO, and CS# channels.
3. Configure the clock polarity (CPOL) and clock phase (CPHA) to match the SPI mode used by your target:
   • Mode 0: CPOL=0, CPHA=0 (most common)
   • Mode 1: CPOL=0, CPHA=1
   • Mode 2: CPOL=1, CPHA=0
   • Mode 3: CPOL=1, CPHA=1
4. Set the bit order (MSB first is standard for most SPI devices).
5. Set the word size (8 bits is standard).
6. Click OK and run a capture.

The decode shows MOSI and MISO data for each transaction, framed by the CS# assertion. If the decode looks garbled, the most likely cause is incorrect CPOL/CPHA settings — try the other three SPI modes.

Setting Up Basic UART Decode

UART is the simplest protocol to decode because it uses only one or two channels and no clock line.

Physical Setup

Connect one channel to the TX line (transmit output of the device you are monitoring). If you want to see both directions, connect a second channel to RX.

Decode Configuration

1. Open Protocol > UART Decode.
2. Assign the TX and/or RX channels.
3. Set the baud rate. Common values: 9600, 115200, 921600. If you do not know the baud rate, try 115200 first — it is the most common default. If the decode produces garbage, try other standard rates.
4. Set data bits (usually 8), parity (usually None), and stop bits (usually 1). The shorthand “8N1” describes this most common configuration.
5. Click OK and run a capture.

Decoded UART data appears as hex values with an optional ASCII overlay. If you see readable ASCII text, the decode is configured correctly. If the text is garbled, the baud rate is likely wrong.

Saving and Exporting Data

Saving a Project

Select File > Save Project to save the entire capture state, including waveform data, decode configuration, trigger settings, and cursor positions. The project file can be reopened later for further analysis without the instrument connected.

Exporting Data

For sharing or post-processing, export captured data:

• Protocol decode table: Export decoded transactions as CSV for spreadsheet analysis or automated comparison.
• Raw waveform data: Export as VCD (Value Change Dump) format for import into other EDA tools.
• Screenshot: Capture the current waveform view as a PNG image for documentation or reports.

Select File > Export and choose the appropriate format and data range.

Where to Find Help

Acute North America Support

Contact Acute North America directly for technical support, RMA requests, and application questions. Support contact information is available on the company website’s support page.

Software Downloads

The downloads page on the Acute North America website provides the latest software releases, firmware updates, and user manuals for all instrument models. Check periodically for updates that add new protocol decoders and features.

Documentation

Each instrument model has a detailed user manual available as a PDF download. The manual covers hardware specifications, software features, and protocol decode configuration for all supported protocols.

Learn Articles

This learn section on the Acute North America website contains application-specific guides for individual protocols (I2C, SPI, CAN FD, eSPI, MIPI I3C, and more), product spotlights, and advanced configuration tutorials.

Summary

Getting started with an Acute instrument is straightforward: install the software, connect via USB, probe your target signals, and run a capture. Protocol decode for I2C, SPI, and UART requires minimal configuration — assign the correct channels, match the protocol settings to your target, and the software overlays decoded transactions directly on the waveform. From this foundation, you can explore advanced triggers, protocol-specific analysis, and the full range of Acute’s decode capabilities as your debugging needs evolve.