Queue write error (PS4, DFGT)

[bombshell]

Hi there,

My setup:

PS4, Logitech DFGT, Driveclub
GIMX 5.3
Windows 7 64bit
DIY adapter made from the guide for dummies (Teensy 2.0, CP2102 serial converter)
EMUG29PS4 firmware (atmega32u4.hex), LogitechDrivingForceGT_G29.xml config


The controls and force feedback works very well, but after what seems like a random amount of time I get an error, after which controls are not working. It has happened after just 1 short race or it has happened after more than 45 minutes of play, so I don't see a pattern.

The error: "queue_write: no space left in write queue for device (0)".
Full gimx.exe log at time of error: http://i.imgur.com/OMLtDXh.jpg

What does this mean, or rather why is it happening?

Also 2 times so far, again randomly, the gimx.exe window has simply closed by itself. I don't know how to provide a log in this case, but do you know why this happens?

I don't know if it's related to my 2 error cases, but in GIMX launcher if I press the Check button, my setup says "joystick not found: PS4 controller (0)", but it starts fine anyway when I press the Start button and then press PS button on the DS4.

Hopefully you can help me, your support for Logitech wheels on PS4 is very much appreciated

[Matlo]

Hi,

The commands that are sent to the adapter are queued, and the queue size is 2.
The "queue_write" error means that there are already 2 commands in the write queue.
I suspect a USB connection issue with the CP2102 adapter.
This could due to a faulty USB cable, or a weak USB HUB.

Your other problem (gimx.exe closing unexpectedly) may have the same cause.

To generate a log file, just select "Messages>Log file" in gimx-launcher before starting GIMX.

[bombshell]

Thanks for your input.

Initially I had problems getting it to work at all, so I tried some different things with the USB drivers and other things. It turned out that I just needed to switch the Rx and Tx pin connections on the serial converter (mis-labeled?). But I might have done something wrong during the phase where I tried different things.

So I've deleted everything including the controller profiles and re-installed it all. Now the Check button says my setup is correct and I have just played a session that lasted over 2 hours without running into the queue error, so it seems to be working as it should now. I can finally play with my wheel again

[bombshell]

So I spoke too soon with my previous post. It seems to have been a lucky first session after my re-installation of everything.

The gimx.exe program still randomly closes and since my previous post I haven't been able to play anywhere near 2 hours, like I was able to in that session without seeing an error. It happens from anywhere within the first minutes of playing to maybe after 20 minutes of play.

A shortened log file example of my error: http://pastebin.com/raw.php?i=79MMdRU0

You said it most likely is because of a bad USB connection, either cables or hub. I don't use a hub, I use the 3 USB ports in my laptop.

I find it strange that I can play for such varying play times before the error happens. I would think if I had a bad USB connection that I couldn't play at all, but apparently not.

For cables I use a PS3 mini USB charging cable, a cheap male to female USB cable and the DFGT USB cable. Are the 2 first cables good enough, or can they be responsible for my error?

I have noticed that when the error happens I hear the Windows sound effect for connecting/disconnecting a USB peripheral, so that suggests that it is a bad USB connection, right?

I also hear this sound effect after I press the Start button in GIMX. Is that the correct behaviour?

Would it be possible to include some log messages in a test version to help me identify which connection is failing?

[Matlo]

I recommend you to try without the retractable USB cable.
I know the tutorial shows such cables, but shielded USB cables should be used instead.

[bombshell]

Thanks for the recommendation, Matlo.

I have now ordered a shielded male to female USB cable.

[Matlo]

Did you try connecting the CP2102 directly?

[bombshell]

I'm dumb, I thought an extension cable was necessary

I've tried it for some time now and no error, so that is promising.

[bombshell]

Hmm, this is frustrating. I'm still getting the error randomly even with plugging it directly into the USB port.

Code: Select all

src/windows/async.c:118 queue_write: no space left in write queue for device (0)

Can it be my CP2102 board itself? I have this one: NEW CP2102 USB 2.0 to UART TTL 6PIN Module Serial Converter Free Cables

I'm thinking of trying a different one, they are dirt cheap anyway.

A board with only 5 pins, but the 3 needed ones (Rx, Tx, Gnd), can that be used?

[Matlo]

What is the CP2102 driver version?