Coyote

Coyote is the currently supported e-stim hardware path in MotionStim. Device control is derived from synchronized motion data so output follows playback timing rather than manual trigger timing.

Coyote 3.0 product details

Based on the official Dungeon-Lab product page, Coyote 3.0 is presented as a compact wireless e-stim powerbox with app integration and websocket control support. The listing also describes optional PawPrints wireless button accessories for interactive trigger scenarios, and it publishes certifications including FCC, CE, RoHS, and REACH.

The same page describes the standard package as the unit plus electrodes, wires, strap, and charging cable, with multiple bundles that add accessories. You can verify current availability and bundle details directly on the official Coyote 3.0 page.

Connection and control model

After connection, MotionStim maps timeline events to device output. Control values are generated from script timing and current playback position, so pauses, seeks, and resume actions stay aligned with one source of truth.

For the broader e-stim overview, start on E-Stim in general.

Where Coyote fits in the workflow

In a typical session, the script defines timing, the player defines current position, and Coyote is the output layer. That separation reduces tuning confusion, because you can isolate whether a behavior comes from source data, playback state, or runtime shaping.

  • Script layer: defines motion events over time.
  • Playback layer: controls timeline state, seeks, and synchronization.
  • Output layer: translates synchronized values to the connected device.

Setup checklist

  • Confirm the device and channel routing before playback starts.
  • Run a short sync check after any seek or file change.
  • Tune comfort and response with modulators instead of rewriting source scripts.

Continue with Funscripts to understand motion-file timing, then review Modulators for session-specific tuning.