Prove the console-side USB link
Check that the cable going to the console is attached to OUTPUT and that it carries data. A lit Titan Two can receive USB power even when a cable or connector fails to carry data. Use the supplied short cable or another one you have already verified, and test a direct console USB port rather than an extension or hub.
Take wireless receivers and additional controllers out of the chain initially. Connect the original compatible controller to INPUT-B wherever the destination requires authentication. Test the controller and its cable directly with the console if they are in doubt.
Check the settings for this destination
In Gtuner IV, review the saved output protocol. An explicit destination setting can be helpful when automatic detection is uncertain. Check the console’s own wired communication setting if the manufacturer’s setup procedure calls for it. The appropriate setting and authentication requirements vary by console, so choose the guide for the exact system and game version.
Leave the adapter at slot 0 while testing menu movement. If that succeeds and a stored slot fails, you have a profile issue to inspect instead of a console recognition failure.
Use the fault boundary to choose the next test
If Device Monitor receives the controller but the console does nothing, focus on OUTPUT, the selected protocol and authentication. If the controller does not register in Device Monitor either, test its front input and cable first. Write down the two results before changing another setting.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.