Hardware
Hardware output routes your input through a dedicated device — a Teensy 4.x microcontroller — so your scripts run on the device and leave as standard USB HID at up to 8,000 Hz, for deterministic timing and isolation from the host OS. Software mode needs none of this; How it works covers the software-vs-hardware split.
This page flashes a board and activates it.
What you need
- A Teensy 4.0 or 4.1 from PJRC, Amazon, or SparkFun. No soldering or wiring — just a USB cable.
- A Rebind license. You own the device; it keeps working without ongoing payment.
- The Rebind app, on the latest version — re-run the install command in the quickstart to update.
A pre-built device — pre-flashed, with a case and cable — is coming soon.
Flash your device
Plug the board in, open the Rebind app, and click the terminal icon in the lower-right corner. List connected devices — each is shown with its index:
$ devices list
[0] bootloader Teensy 4.1
vid:pid 16c0:0478
firmware none
Flash the device at that index:
$ devices flash 0
The board reboots into the Rebind firmware once flashing completes. Re-run
devices flash <#> any time to update a board. (The command is devices;
device works too as an alias.)
Activate
Your Rebind license key is emailed when you purchase. Activation ties the key to the device and is done once per board:
$ activate REBIND-XXXX-XXXX-XXXX
license activated
status active
(On failure the command prints activation failed: <message> instead.) The
license then lives on the hardware and works offline.
Verify
$ devices info
active device:
id a1b2c3d4e5f6
board Teensy 4.1
firmware 1.4.0
bus 1-2
vid:pid 16c0:0486
interfaces:
0 keyboard usage_page=0x01 usage=0x06
1 mouse usage_page=0x01 usage=0x02
2 rawhid usage_page=0xFF00 usage=0x01
If devices info shows your board with its firmware version, hardware output is
live. Run a script — its output now comes from the device.