Hardware¶

Hardware documentation covers the WILD device architecture, onboard sensors, optional modules, mechanical assembly, power choices, and release-image compatibility for supported device revisions.

Device

Architecture

Sensors

IMU, audio, camera

Opto module

Stimulation

USB-GPIO

Trigger alignment

Mechanical

Mounts and enclosures

Power

Battery, SD, mode power

Releases

Firmware images

Hardware Asset Map¶

Hardware area	Repository path
Datalogger PCB	PCB/Datalogger
Opto module	PCB/Optomodule
Camera unit	PCB/CameraUnit
USB-GPIO board	PCB/USBboard
USB-GPIO firmware	Firmware/WILD_USB_GPIO.hex
Opto-module firmware	Firmware/Opto_module.hex
Mechanical parts	3Dprint
Battery table	LipoBattery_selection.csv
Prebuilt device images	Latest GitHub release

Manufacturing Workflow¶

For a new WILD device build, start with the Fabrication page. The workflow covers fabrication parameters, PCBA submission, special components, manual soldering notes, and first DFU image installation.

Compatibility Record¶

Document the following for each supported WILD hardware build or dataset:

Record	Why it matters
PCB or device revision	Distinguishes connector layout, sensor options, and supported release images.
Release tag and image filename	Ties behavior to a reproducible device image.
WILD Console version	Defines the export and control tool behavior used in the session.
SD-card model	Affects boot reliability and long-session write stability.
Battery model	Affects boot margin, runtime, and peak-load behavior.
Enabled modalities	States whether the session used ephys, IMU, audio, video, stimulation, or external sync.

Bring-Up Checklist¶

Before the first recording on a newly assembled WILD device:

Confirm that the PCB revision, assembly files, and intended release image match.
Use the USB-to-4-pin bench cable and USB power meter for the first power check.
Install the first validated .hex release image through WILD Console Advanced DFU update.
Confirm battery polarity and boot stability.
Confirm microSD insertion and basic discoverability.
Confirm BLE connection and synchronization state.
Run a short recording, export it, and verify the expected files before any animal session.

Visual Asset Policy¶

Public hardware visuals should be traceable to real WILD material: device photographs, CAD or EDA exports, microscope images, measured drawings, software screenshots, or hand-authored diagrams derived from measured hardware. AI-generated device photographs or device-like renders are excluded from WILD hardware documentation.