Skip to content

protocol.md

Latest commit

 

History

History
72 lines (53 loc) · 1.83 KB

protocol.md

File metadata and controls

72 lines (53 loc) · 1.83 KB

Advanced Network Details

Most users do not need this page. Use it only when checking firewall, network, or host-app compatibility.

Connection Model

x360 Controller uses a local WebSocket connection.

  • Host device: Android phone or Windows PC
  • Client device: Xbox 360 running controlleremu.xex
  • Default port: 3000
  • Transport: WebSocket over TCP
  • Update rate: 60 Hz target

The Xbox plugin connects to the host address written in controlleremu.ini.

Basic INI Format

Android host:

[Network]
ip=<phone-ip-shown-in-app>
port=3000
host1=android|<phone-ip-shown-in-app>|3000
host2=windows|<windows-pc-local-ip>|3000
order=host1,host2

Windows host:

[Network]
ip=<windows-pc-local-ip>
port=3000
host1=android|<phone-ip-shown-in-app>|3000
host2=windows|<windows-pc-local-ip>|3000
order=host1,host2

The release controlleremu.ini uses documentation addresses, Android 192.0.2.2 and Windows 192.0.2.1, as defaults. Replace those with your actual IPs, then reboot the console after changing the file.

Controller Frames

The host sends controller state as short ASCII text frames. The frame includes:

  • controller slot
  • left and right stick positions
  • face buttons
  • D-pad direction
  • shoulder buttons
  • Back, Start, Guide, and stick-click buttons
  • analog trigger values

This is an implementation detail for compatibility checks. It is not needed for normal install or play.

Vibration Messages

The host can receive vibration status messages from the plugin. The Android and Windows apps may display or log this state when supported.

Network Tips

  • Keep console and host on the same local network.
  • Avoid guest Wi-Fi networks that isolate devices.
  • Use port 3000 unless you update both the host app and INI.
  • Use the phone IP shown in the Android app, or the PC IP shown in the Windows app PC status chip.