← labopen tactile · pebble in the hand →

Tactile · pebble in the hand

A hardware simulation of the Tactile pebble, an M5Stack AtomS3R held in one hand, made for working out how it should be used without a bench, a cable or the device. The 3D device on the screen runs the firmware's own reader: the C that ships on the pebble (firmware/main/afterword.c), compiled unchanged to WebAssembly. Everything it decides (pace, pause, focus, enter, exit, the first-use tutorial) is the firmware deciding it. The simulation supplies only what the device would feel: a hand, and the IMU in it.

Holding it

The reader, in the firmware's words: turn clockwise and keep it turned to speed up; return upright to keep the new pace; turn counter-clockwise through a pause into reverse; stay paused for 400 ms to focus the word; tip the top edge away for 300 ms to enter a linked word; tip it toward you to come back out to the exact word you left. First use teaches all of this, one capability at a time.

What it shows

Realism

The hand is a critically damped spring toward your intent. To it you can add physiological tremor (8–12 Hz), a walking gait (1.8 Hz: vertical bob, fore-aft surge and wrist sway, which the accelerometer reads as tilt), BMI270-like sensor noise and a gyro bias. The IMU is sampled at 100 Hz and the reader runs every 20 ms on the latest every-other sample, as on the device.

A haptic preview pulses the phone on focus, enter, exit and refusal: a sketch of P4's LRA, for asking which moments deserve a touch before there is a motor to give one (Android only: iOS has no vibration API).

What it is not

Findings so far

From the headless checks (devtools/tactile.test.mjs), with a scripted operator that does only what the screen and hint line ask:

Updating the device

The core is generated from a tactile checkout:

TACTILE=../tactile node cells/lab/devtools/tactile-core.mjs

That compiles afterword.c with a small freestanding libc (devtools/tactile/libc), runs the firmware's own regression (tests/afterword.c) against the same WebAssembly, drives a native gcc build and the WebAssembly through one scripted session and requires them to agree on every tick, then writes client/tactile/core.gen.ts with the firmware version, commit and the reader's constants. Then node cells/lab/devtools/tactile.test.mjs (the operator, axes and realism checks) and node cells/lab/devtools/tactile-shot.mjs (screenshots at phone size).