Skip to content

TWS: status and troubleshooting

JP150PCB 1.3PCB 1.4since 26.9.0Jan PřibyslavskýThis page does not apply to the product or PCB revision chosen in the header.

Understanding the status values

TWS status

  • Standby: TWS is enabled, but there is currently no link to the peer. Standby is also shown after TWS has been disabled.
  • Connecting: the unit is trying to connect to its peer.
  • Connected: the link to the peer is established.
  • Streaming: the link is established and audio is being streamed.
  • Unsupported: the Bluetooth module does not report TWS support. This value normally appears only briefly while the Bluetooth module is starting up, or when the module is not responding (see troubleshooting below).

Current role

  • Primary / Secondary: the unit's role in the active TWS link.
  • Unknown: no peer information is available yet. This is normal after a restart or after the peer has been forgotten, and does not indicate a fault.

Boot outcome

  • Pending: the unit is still determining its TWS state after power-up. The value usually settles within about 15 seconds.
  • NoPeer: no peer was remembered at power-up, so the unit followed its Fallback role.
  • Reconnected: the remembered peer was found and the link was re-established.
  • PeerUnreachable: a peer is remembered but did not respond at power-up. The unit works on its own and waits for that peer; it does not search for another one. Boot outcome keeps showing PeerUnreachable as a record of the power-up, even if the peer connects later; the current link state is shown by TWS status.

Troubleshooting

The units do not pair

  • Roles: one unit must be set to Primary and the other to Secondary. Two Primary units or two Secondary units never pair.
  • Old pairings: neither unit should remember a peer. Check that neither Peer table contains a row marked TWS; if one does, run Start new pairing on that unit.
  • TWS capability: Enable must be selected on both units.
  • Host: switch off Bluetooth on the host during pairing.
  • Distance: place the units close to each other during pairing.
  • Power-up order: switch on the Secondary first and the Primary a few seconds later.
  • Time: allow up to one minute for the units to find each other.

The "Remembered peer did not respond" banner appears. The other unit is switched off, out of range, or no longer has the pairing. If it is switched off or out of range, switch it on or move it closer; the units reconnect automatically and the banner disappears. If the other unit has lost its pairing, or has been reset or replaced, pair the units again: run Start new pairing on both units (one Primary, one Secondary).

Only one unit plays

  • TWS link: on the Bluetooth > TWS page, check TWS status. If it shows Standby, click Reconnect.
  • Input: make sure that the Bluetooth input is selected on the Overview tab of both units.
  • Host: make sure that the host is connected to the Primary.

The host does not reconnect automatically. This is expected when a paired unit is switched on without its peer. Connect manually from the host's Bluetooth settings.

TWS status remains Unsupported while TWS is enabled. Check the Diagnostics group. If Firmware or Device Name shows "---" or n/a, the Bluetooth module is not responding. Power-cycle the unit. If the problem persists, contact MURA LABS support.

All controls in the TWS section are greyed out. TWS capability is set to Disable. Click Enable.

The TWS capability setting is lost after a restart. This is by design: at power-up the unit sets TWS capability automatically. To keep TWS off permanently, forget the peer and set the Fallback role to Standalone (use a unit as a standalone amplifier again).

A button seems to have no effect. Read the status bar at the bottom of the MuraLink window; it explains why most requests are refused. For example, Reconnect reports "already connected" or "No peer is remembered…", and Forget peer can report that the device did not confirm the request. In that case, check the Peer table to see whether the TWS row has been removed.

Known limitations

  • Pairs only: a unit can be paired with only one peer at a time. Groups of more than two units are not supported.
  • No left/right assignment: both units play the full stereo signal. To play only the left or right channel on a unit, configure the channel routing in its DSP program.
  • One unit per connection: MuraLink connects to one unit at a time over USB, so each unit is configured separately.
  • Lone unit and host: if a paired unit is switched on without its peer, the connection to the host is not restored automatically (Known issues).
  • No host connection during pairing: a unit cannot start TWS pairing while a host is connected to it. Start new pairing disconnects the host automatically.

TWS command console

The TWS Command Console (expert mode) button opens a separate window that lists every TWS command supported by the firmware. For each command the window provides a send button, a parameter field, and the unit's raw response. The console is intended for development and diagnostics only. Several of its commands change stored settings or drop links without asking for confirmation, so do not use the console for normal setup. Everything described on these pages can be done with the standard controls. The commands themselves are in the command reference.