what you're looking at, and what to do
your driver is running the session from their own device. they can change patterns, intensity, electrode position, and more in real time. this page does two things: it shows you what's happening with a live feel indicator, and it bridges the signal to your local ReStim device.
you don't need to install anything. as long as your browser is open and your ReStim is running, the signal flows. if your tab goes to sleep or the connection drops, it reconnects on its own.
you always control your absolute maximum. ReDrive shapes the signal — patterns, relative intensity, electrode position — but it goes through your ReStim's master volume. whatever you've set on your hardware dial is the ceiling. the driver cannot exceed it.
ReDrive connects to your local ReStim via WebSocket. you need ReStim running on the same PC as this browser tab, with its WebSocket server enabled.
ws://localhost:12346/tcode — ReDrive uses this automaticallyif ReStim is running on a different port or address, expand the ReStim address section at the bottom of this page, change the URL, and click Apply.
for more ReStim setup help, see the ReStim GitHub.
the top card on the page gives you a live read on what's coming from the driver. it's a display only — you can't control anything from it. here's what each element means:
the glowing circle breathes in time with the signal frequency. faster breathing = higher Hz. larger and brighter = higher intensity. when the signal is paused or the driver hasn't connected yet, the orb goes dark and still.
the line below the orb names the current pattern and gives you a quick description: the frequency, pattern character, and depth. it updates as the driver changes things.
the track below the feel text has a glowing dot that slides between A and B. this shows the current electrode balance — which electrode pair is more active. when the driver is sweeping, you'll see the dot moving.
the green–blue bar shows the driver's current relative intensity setting as a percentage. this is relative to your hardware limit — 100% here means the driver has you at full relative output, not that you're at any absolute level.
only visible when the driver has started an intensity ramp. shows how far along the ramp is and where it's headed. it disappears when the ramp completes or is cancelled.
tap 📷 Set Pic on the photo card to pick an image from your device. your driver will see it in their participant panel and as a selectable overlay on their touch canvas — it's how they get a visual sense of who they're with.
the photo is resized and compressed automatically (under 400 KB, max 512 px on the longest side). it's sent directly over the session WebSocket — it's never stored on the server. the only place it persists is your own browser's local storage, so it reappears if you reload the page or reconnect.
if you want to use a portrait photo that aligns well with the touch canvas, full-body or upper-body shots with the subject centred work best. the driver's canvas is 9:16 (portrait orientation).
the bridge card shows two status indicators:
colours:
the page will reconnect automatically with exponential backoff. wait a moment. if it stays red, try reloading the page — your room code is in the URL and will reconnect you to the same session.
the page is trying to reach ReStim on your PC and failing. common causes: ReStim isn't running, the WebSocket server is off, or you're on a different machine than your ReStim. check that ReStim is open and the WebSocket server is enabled. if you're using a non-default address, update it in the ReStim address section and click Apply.
the session connection and the ReStim connection are independent. you can be connected to the session but not yet to ReStim — the driver's signal is waiting, it just isn't getting to your device yet. get the ReStim dot green and it flows immediately.
when your driver fires a poppers cue, a full-screen image appears with a countdown timer. this is a signal from your driver to inhale. the timer shows how long the cue lasts:
the overlay dismisses on its own when the timer runs out. the electrical signal keeps running during the overlay — the driver controls the timing of everything together.
poppers are a controlled substance in some regions. you are responsible for your own choices. ReDrive is just displaying a timed visual cue at the driver's direction.
the page detects when your tab comes back into focus and immediately sends a keepalive to the server. reconnection is automatic. your ReStim will resume receiving signal as soon as both connections are green again.
open the rider link again — same URL your driver sent you, or the room code on the ReDrive home page. you'll reconnect to the same live session. your driver keeps running; the signal resumes as soon as you're connected.
check both dots. if Session is green but the orb is still dark, the driver may have paused or not started yet — the feel text will say Waiting for driver…. if Session is amber or red, you're reconnecting — wait a moment.
make sure the ReStim WebSocket server is still enabled — it can get disabled if ReStim crashes and restarts. also check that your hardware master volume is turned up; if it's at zero, ReDrive has no room to work within.
keep your hand on your ReStim's power dial. your driver controls the pattern shape and relative intensity, but your hardware dial is your absolute ceiling. you can lower it or switch off your device at any moment. agree on a safe word and a comfort ceiling with your driver before the session starts.
ReDrive sends T-code commands to your ReStim — the same format used by toys and scripts across the ecosystem. it has no special access to your hardware beyond what ReStim's own WebSocket interface allows. the session server never sees your ReStim connection directly.
never run at intensities that are uncomfortable. start low, communicate with your driver, and increase gradually. if something feels wrong, turn down your hardware dial first — that's immediate. closing the browser tab stops the ReDrive signal but your hardware continues whatever state it's in until you turn it down or off.
ReDrive is early alpha software. expect rough edges. your hardware safety is always your own responsibility.