Product tour
Artisan Glove is a sensing-glove design for recording hand contact, vibration and video. Its source connects a physical sensing stack to the electronics, firmware, recording format and browser tools needed to inspect an acquisition.
Explore one complete design journey
- Open the cuff. Run
python3 tools/serve.pyfrom the repository root, then openhttp://127.0.0.1:8070/. Choose Open to see the main board, battery and camera, then Exploded to separate the housing and service parts. Select a component to inspect it. You are looking at dimensioned engineering geometry and component envelopes. - Follow a sensing location. Open the visual assembly guide. Follow the V3 sensor stack, cut pattern and wire labels reused by V4. Each location has a pressure-sensitive film cell and a separate PVDF vibration channel.
- Trace the hardware. Open the main KiCad project, canonical routing candidate and schematic. Use component/reference and net maps to follow that location through its analogue front end and ADC. The dorsal hand tile is a separate native design with fabrication outputs.
- Execute the acquisition logic. Run the host checks. The real C++ acquisition core processes modelled electrical samples, emits packets, and exposes timing/queue/error metadata. The Python and JavaScript decoders check those produced bytes. This gives you a reproducible software boundary before building electronics.
- Inspect the device experience. Open
http://127.0.0.1:8070/device/. The bundled monitor exposes a hand contact map, wrist camera, selected vibration waveform, spectrum, labels and acquisition health. It waits for actual cuff data. After hardware bring-up, the cuff serves this UI on its private Wi-Fi network; firmware setup explains Wi-Fi/BLE and packet channels. - Prepare a physical build. Use the BOM, print manifest and factory acceptance guide. Close main-board routing and process acceptance first, then measure actual timing, calibration, optics, thermals and endurance against the status checklist.
Product areas
| Area | Actions and results | Source |
|---|---|---|
| Design viewer | Assemble/explode, rotate and select actual generated parts; inspect envelopes and nominal fit. | enclosure/viewer.html and viewer.js |
| Assembly | Place twenty sensing pairs, fit the cuff and dorsal IMU, follow keyed harness branches. | guide/assembly.html, sensors/ |
| Main board and hand tile | Edit native circuits/placement/routing and use designator/MPN BOMs. | electrical/, interfaces/hand-tile/ |
| Device monitor | Inspect contact, camera, selected waveform/spectrum, labels, battery and loss counters. | software-preview/, http.cpp |
| Acquisition and storage | Follow ADC scan timing, dual IMUs, camera ownership, timestamped packets and SD recording. | firmware/tactile_v4/main/, PROTOCOL.md |
| Reuse and verification | Run sanitizer cases, independent packet decoders and nominal STL audits. | tools/tactile_v4/, verification guide |
Where to go next
Setup gives the shortest working path. Module map locates the source. Architecture explains ownership and data flow. Design history explains the sensing stack, separate IMUs, camera correction and engineering tradeoffs. Current status tells you which evidence is already reproducible and which measurements a physical build needs.