Prerequisites

1. Plug the controller into the Pi (USB cable or paired Bluetooth dongle).
2. In your code (bundle/controller.py and/or TARSmaster.py), note the default event path (/dev/input/event3) or the auto-detection logic.

Install tools

sudo apt update
sudo apt install -y evtest joystick

Identify the event device

1. List input devices: ls /dev/input/event*
2. Run evtest on each candidate until you see button activity: sudo evtest /dev/input/eventX Press a few buttons—if you see the corresponding key codes, note the event ID.

Update the code

• For the modular script (bundle/controller.py): device_path = '/dev/input/eventX' # replace with the verified path
• For TARSmaster’s auto-detect block, optionally add extra checks after the device loop: if not controller: controller = InputDevice('/dev/input/eventX')

Test

cd ~/TARS-files/bundle
python3 controller.py

Press A/B/X/Y. You should see movement logs (“move forward”, “turn left/right”, etc.).

Troubleshooting

• Permission errors? Add your user to the input group (sudo usermod -aG input pi) or run with sudo.
• Wireless controllers sometimes expose multiple event devices. Test each with evtest to find the one carrying button presses.
• If TARSmaster still fails to attach, hardcode the detected event path right after the loop that scans /dev/input.