Windows + DIY cable + G27 not working

[Matlo]

I think you did not load the right firmware. The teensy ++ 2.0 has the at90usb1286 chip, not the atmega32u4.

[bertie]

Flashed the at90usb1286 firmware onto the Teensy instead, GIMX log is exactly the same. Detects Teensy/CP2104 as "G29 PS4" but still can't find G27 connected to PC.

How is it searching for the G27? Based on USB ID? The Logitech Profiles shows "G27 Racing Wheel on ID 1"

[Matlo]

Did you try to detect G27 inputs using gimx-config? What's the device name?
I wonder if the device name is different from the one in the config.
This would explain why GIMX does not find the device.

[bertie]

YESSSS!!

Wasn't sure what you meant, as a bit of a noob, but then thought about...

Loaded gimx-config and opened the LogitechG27_G29.xml and chose the X button assignment and clicked Modify, then aut-detect. Came up as a "G27 Racing Wheel" instead of "Logitech G27 Racing Wheel USB".

So opened the xml file in Wordpad, quick search and replace, re-launched gimx-launcher and WORKS!!

Thanks for all your help!!!!

*loads up Drive Club...

[Matlo]

I think the device name issue may be caused by the Logitech Gaming Software.
Which version did you install?

[bertie]

Latest from their site, am using the Windows 7 x32 PC now as cleaner install. Think Device Manager says v5.9.x?

One other thing, the PS4 turns the DS4 off after so long, so had to power that off via PS4 menu first otherwise G27 stopped working. As well as my PC going to sleep! Doh

[Matlo]

Is directx installed and up-to-date? I think it may affect how the device is recognized.

[rodrigozli]

I was having the same problem. GIMX wasn't detecting G27, so I changed tha names on XML file, just like you did.
Open GIMX again, this time the check function sad everything was ok, then I tried the start button and get this:

Driver file operation error. Failed to open device symlink \\.\UsbDk (Failed to get error description for error code: 0x2)
option -l with value `log.txt'
option -c with value `LogitechG27_G29.xml'
option -p with value `COM3'
status flag is set
subpos flag is set
force_updates flag is set
native mode is already enabled for HID device \\?\hid#vid_046d&pid_c29b#6&178a5105&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (PID=c29b)
Detected USB adapter: G29 PS4.
libusb_get_device_list: Other error.
No controller was found on USB buses.
adapter_detect failed

Any suggestion? What should I do now?

[bertie]

Looks like your PS4 controller isn't found.

Check USBDK is installed properly (re-install direct from the installer in the sub-dir) and the right x32/x64 version.

[Matlo]

@rodrigozli
Please start another topic if you have any further issues.