DIY USB- Win10 - G25- PS4 Not Work.

[Motoko]

Hi, I did have the same issue - and I could resolve it by executing gimx as admin.


Cheers,
Fennec

HI, good hint but unfortunately it wont works.

@Matlo
Is there a way to test teensy board as the cp via software?
I mean, testing pins tx/rx. I'm looking to teensyduino software but I'm not sure it is helpful.

[Motoko]

Sorry if I ask again but can't find any docs, someone know i it's possible to test teensy pins with teensyduino?

[Matlo]

Hi,
It seems possible: https://www.pjrc.com/teensy/td_uart.html

[Matlo]

Hi @Motoko,
Did you solve the issue?
It may be due to a bad contact between the Teensy and the CP2102.
The problem could also be due to the target console not being started.

[Motoko]

Hi Matlo, unfortunately I couldn't test anything, I was super busy at work. In the next days, I'll try again. I have a new clean w10 install so, maybe, something will change.

[v800290]

May be a silly question but: Where the hell is your GND connection?

[Motoko]

it's stamped on the other side of the pcb, you can see in th other pic above that.

[Matlo]

Do you still have the green cable connected to DTR?
As I said in an earlier post, it should be connected to GND...

GND Teensy -> green cable -> GND CP2102
D2 Teensy -> blue cable -> RXD CP2102
D3 Teensy -> purple cable -> TXD CP2102

[Fennec]

Hm, interesting, I'm now getting the same/very similar error message for my Driving force GT that Motoko is getting:
option -l with value `log.txt'
option -c with value `LogitechDrivingForceGT_G29.xml'
option -p with value `COM6'
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_c29a#7&131c5a71&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (PID=c29a)
ReadFile failed: timeout expired.
can't read packet header
No controller detected.
adapter_detect failed


As I mentioned earlier I had it when I installed GIMX the first time. Then I executed it as an Admin and it did work perfectly. After a while it did stop working. It was still showing me, that the config is ok, but when starting I got the above error message. I reinstalled the Logitech drivers - and it worked again. Now it does not work anymore - and I can't get it going again. I suspect that it is related to the Logitech drivers, but I don't have a clue yet what to do. Any idea Matlo?

I updated to v5.6 when I couldn't resolve the issue, no change. I'm using the DIY adapter with a Teensy and CP2102 - and it did work before. Therefore, I'm quite certain that the adapter itself is ok.

Hm, I'll fiddle around with the drivers a little more, let's see...

[Fennec]

Hm, solved it. Looks like the CP2102 driver does have an issue. I replaced the CP2102 with an FT232 and now it does work again. I wonder if the CP2102 driver has somehow been killed by a win 10 update or something...