Start with the device connection
Connect a data-capable micro-USB cable from the computer to the Titan Two PROG port. The device OUTPUT port serves the gaming system in a typical wired setup. If you are checking basic recognition, connect PROG first and wait for the device to appear in Gtuner IV before adding controllers and a console. This gives you a known working connection to return to.
Once connected, check the device settings against the console or PC you intend to use. Changes such as output protocol are hardware settings. Installing a new Gamepack into a memory slot will not by itself correct a mismatch in the output protocol.
Pick the panel by the work you have
Use Online Resources when starting with a published Gamepack, script, mapping or macro. Use the Script IDE when your starting point is GPC source code that you intend to read, compile or edit. Use Input Translator when the change is a control layout or a mouse-to-stick translation, and use Macro Editor when editing a recorded timeline.
Keep your source work on the computer and program a spare slot for tests. This makes it possible to revert the device configuration without trying to reconstruct a project from whatever happens to be in the active slot.
Finish by checking live inputs
Open Device Monitor and compare a single controller input with its output. Check that the intended memory slot is active. Repeat the test with the slot unloaded if a control behaves unexpectedly. A difference that disappears when the slot is unloaded points you toward the programmed work, which is a narrower place to investigate than the entire setup.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.