Titan Two setup for a first wired connection

Set up the device on a computer

Use the port marked PROG to connect Titan Two to the computer running ConsoleTuner Gtuner IV. Check that the device appears in the software before connecting anything else. Review the device configuration and update the firmware through ConsoleTuner’s tools if needed. Keep the provided short micro-USB cable available as a known reference when checking the other cables.

The desktop software and the console use separate connections. Unplugging PROG after configuration can help you confirm whether the adapter works as a standalone controller bridge. You can reconnect PROG later to inspect input and output in Device Monitor.

Connect the controller and host

Use OUTPUT for the cable going to the console. INPUT-A is the preferred controller position in ConsoleTuner’s basic layout. Where the host requires authentication, connect its original compatible controller by USB to INPUT-B. A controller that lights up or charges has power, but you still need a data-capable cable for its input or authentication role.

Choose the destination’s documented output protocol in Device Configuration if automatic detection fails. Some systems also need wired controller communication enabled in their own settings. Check the destination guide for that setting before assuming the adapter is faulty.

Verify a clean baseline

Start at slot 0 with no script or translator active. Test directional movement and a few buttons in a system menu or offline controller test. Add a second controller, wireless connection or stored configuration one at a time. Recording which change introduces the problem gives you a reproducible test instead of a setup in which the controller, protocol and software all change at once.