Skip to content

Getting Started

A prepared WILD device moves from hardware checks to acquisition and analysis through three main steps.

1. Hardware setup

WILD device, connector, microSD, battery, probe or sensor cabling, and release-image checks before the first recording.

2. Data acquisition

WILD_console provides BLE discovery, synchronization, recording configuration, closed-loop control, and data export.

3. Data analysis

Compatible headers, timing files, decoded camera streams, processed IMU data, and spike-sorting inputs.

Before You Begin

  • Windows 10 or later for WILD_console.
  • Bluetooth 4.0 or later for BLE control.
  • A tested microSD card installed in the WILD device. Use Samsung EVO series or tested Lexar cards for first recordings; some SanDisk cards may be unreliable.
  • A battery that can boot the WILD device and sustain the planned recording mode.

Repository Assets

Asset Location
Prebuilt device images Latest GitHub release
WILD_console installers Latest GitHub release
PCB fabrication files PCB
3D-print files 3Dprint
MATLAB and Python analysis scripts Code

Recommended first path

The recommended first-device path is Hardware Setup, Data Acquisition, then Data Analysis. The WILD device SD card, battery, release image, and boot state provide the baseline for troubleshooting acquisition.

First Successful Dry Run

Goal: complete a short bench recording and confirm that the public export and analysis path works before changing advanced settings.

Minimum output folder:

  • amplifier.dat
  • analogin.dat
  • time.dat
  • info.rhd
  • CE_params.bin

Optional outputs, depending on mode:

  • adc.dat for audio workflows
  • misc.dat for camera workflows
  • device_event.*.evt files after MATLAB preprocessing
  • IMU.mat after IMU processing

Success criteria:

  1. The WILD device is discovered and connected in WILD_console.
  2. A short recording starts and stops cleanly.
  3. SD-card export completes without missing-core-file errors.
  4. The exported folder contains the expected files for the recording mode used.
  5. MATLAB or Python post-processing runs without requiring manual file repair.