Troubleshooting
This page covers problems with the physical suit itself: fit, electrode contact, sensors, and power. If the symptom is about pairing, connection, updates, or calibration behaviour in the apps, see Control Center - Troubleshooting. If it's about Studio behaviour (avatars, presets, capture), see Studio - Troubleshooting.
Warning
If you feel pain, dizziness, nausea, or any other physical discomfort while wearing the suit, disconnect the power bank immediately and take off the suit. See Hardware - Safety.
No haptic sensation, or it's very weak#
- Check that the electrodes have full, flat contact with bare skin. Even a slight angle or a loose fit can prevent stimulation. See Hardware - Wearing.
- Confirm nothing is between skin and electrode, and that any underwear worn underneath has no metal parts.
- Best contact happens when skin is slightly moist. Do a few light exercises to perspire; don't pour liquid on your skin.
- Confirm haptic calibration has been done for this session in Control Center - Calibration. Without calibration, sensation is set to conservative defaults (1% MIN, 30% MAX) and can feel imperceptible.
- Check global haptic power in Control Center isn't set too low. It multiplies every animation's power before minimum/maximum limits are applied.
If one specific body area (for example a single channel or zone) never produces sensation while the rest of the suit works normally, that's more likely a hardware fault in that zone. Note the affected channel and see When to contact support below.
Avatar doesn't move correctly, or mocap drifts#
- Recalibrate. 6-axis mocap calibration is not saved between sessions and must be redone after every Studio restart, or whenever the avatar stops reflecting your movement correctly. See Studio - Data Capturing.
- If you're using 9-axis mode, move away from ferromagnets and large metal objects. They interfere with the magnetometer this mode depends on. See Concept - Mocap.
- Make sure the I-pose used for calibration was clean: full height, hands straight by your sides, feet hip-width apart and flat.
- Long recordings drift more, since drift accumulates over time. This is expected behaviour of 6-axis mode, not a fault.
Power bank or connector issues#
- Check the power bank for visible damage before connecting it. Don't connect the suit to a damaged power bank.
- Confirm the power bank is charged and meets the required specification (capacity, output). See Hardware - Specifications.
- Reseat both USB-C cables: the shorter cable between power bank and jacket, the longer cable between jacket and trousers. See Hardware - Wearing.
- If the suit doesn't power on with a known-good, charged power bank, that points to a hardware fault. See When to contact support.
Biometry (PPG) readings missing or inaccurate#
- PPG measurements are extremely sensitive to sensor-to-skin contact. Recalibrate every time you put the suit on, not just once. See Concept - PPG.
- Confirm the sensor sits on the outer surface of the right shoulder, where the deltoid muscle ends.
- Confirm your device version actually carries a PPG sensor (TESLASUIT from version 4.5.6).
- Stay still for the full calibration countdown. Movement during the sample recording invalidates the calibration.
Suit feels different between sessions#
Haptic sensation depends on individual skin properties (galvanic skin response), which vary session to session. This is expected and is exactly why calibration exists — recalibrate rather than treating it as a fault. See Concept - Haptics and Hardware - Wearing.
Not a hardware issue?#
- Drops connection, won't pair, or won't update → Control Center - Troubleshooting
- Device not showing up in Studio, no haptic felt during preset playback → Studio - Troubleshooting
When to contact support#
Contact support@teslasuit.io if:
- A symptom is isolated to one specific channel, node, or sensor while the rest of the device works normally.
- A fault persists after eliminating fit, contact, calibration, and power causes above.
- You see physical damage to the fabric, electrodes, or connectors.
Include with your message:
- The affected channel, node, or area.
- Your device's hardware and firmware version (see Control Center - Device Report).
- What you've already tried.
Note
Attach the log files too. Copy the whole logs folder from %ProgramData%\Teslasuit\logs and include it with your message.
