Game Input MultipleXer

Posted: **Tue Jan 31, 2017 2:53 am**

Following the DIY "for dummies" page, I've built one using this converter and a teensy 2.0 with pins running EMUPS4PAIRING/atmega32u4. I'm getting this error log:

Code: Select all

global option -l with value `log.txt'
global option -c with value `Dualshock4.xml'
controller #1: option -p with value `COM4'
now reading arguments for controller #2
status flag is set
subpos flag is set
force_updates flag is set
GIMX 6.3 x86_64
Windows 10 (or later) x64
Kernel version: 10.0 (14393)
windows/async.c:344 async_read_timeout: ReadFile failed: timeout expired.
can't read packet header
gimx.c:208 SDL_main: no adapter detected

I've read around and see other people getting this error.
I've tired:

[*]switching the TXD and RXD
[*]changing out the jumper cables
[*]reinstalling usbdk
[*]using different usb cords
[*]using different ports
[*]rebooting

Any ideas what the issue could be? This is driving me crazy.

Posted: **Tue Jan 31, 2017 10:02 am**

Hi,
Please post a picture showing the wiring.

Posted: **Tue Jan 31, 2017 8:58 pm**

https://imgur.com/a/IqIiO

Posted: **Tue Jan 31, 2017 9:11 pm**

The correct wiring is:
D2 -> TXD
D3 -> RXD

Posted: **Tue Jan 31, 2017 9:16 pm**

I've tried both ways, but I checked again just now to be sure and it's still producing the same error when wired that way.

Posted: **Wed Feb 01, 2017 11:18 am**

Sorry, I did not realize that you loaded the EMUPS4PAIRING firmware, which is not made for the DIY USB adapter.
You should use the EMUPS4 firmware, or any other firmware listed on the wiki:
https://gimx.fr/wiki/index.php?title=DI ... nd_drivers

Posted: **Wed Feb 01, 2017 7:17 pm**

Thanks, that seemed to be part of the problem. I changing the firmware out which seemed to help. I ran it and it threw a new error asking for the DS4 to be plugged in, so I did that. Then, I ran it again and it actually grabbed the mouse and didn't throw an error. However the input wasn't getting to the PS4. I closed the program and it opened a text file with all the inputs I had made, but at the bottom it was just "libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)" repeating over and over.

Posted: **Wed Feb 01, 2017 7:18 pm**

I forgot to mention that now I can't connect anymore like it was before I closed it.

Posted: **Wed Feb 01, 2017 7:23 pm**

Also, the cmd window that pops up before it fails reads: windows/gprio.c:23 gprio: failed to set priority class

Posted: **Wed Feb 01, 2017 8:14 pm**

Generally transfer errors are due to bad cables. Try to change the DS4 cable.
If it does not help, please post a full log file.

Game Input MultipleXer

PS4 DIY USB "no adapter detected"

PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"

Re: PS4 DIY USB "no adapter detected"