PS4, DFP: "Write queue for device" error
Posted: Wed Dec 28, 2016 6:10 pm
Hello everyone! I encountered the following problem: when I successfully connect everything and start driving (in DriveClub and in DriveClub VR), my wheel disconnects in about 10 seconds or in a minute after i start the race. Here's log details:
global option -l with value `log.txt'
global option -c with value `LogitechDrivingForcePro_G29.xml'
controller #1: option -p with value `COM3'
now reading arguments for controller #2
status flag is set
subpos flag is set
force_updates flag is set
GIMX 6.3 i386
Windows 7 SP1 x86
Kernel version: 6.1 (7601)
USB adapter detected, controller type is: G29 PS4.
found pass-through device 0x054c:0x05c4
Timer resolution: min=156001 max=5000 current=5000
using default refresh period: 5.00ms
0 1482783150.448500, wheel (-465)
0 1482783150.478500, wheel (-457)
0 1482783150.493500, wheel (-449)
0 1482783150.503500, wheel (-441)
0 1482783150.513500, wheel (-437)
...
Exiting
windows/async.c:165 queue_write: no space left in write queue for device (\\.\COM3)
The wheel is Logitech Driving Force Pro.
System is Windows 7 32 bit, running on a laptop.
For DIY adapter I use CP2102 adapter and Arduino Leonardo clone board. CP2102 is connected without any cables, directly into USB port.
USBDK is installed and I had no problems with controller authentication.
I use standard PS4 with the latest 4.07 firmware, trying to play DriveClub and DriveClub VR.
Everything-wheel,DIY adapter and DS4 are connected to USB hub, which is definitely not weakly powered.
In PS4 menu and in-game menus the wheel works for about 3-5 minutes or longer, but it disconnects in seconds or in a minute when I start the race and start to actively drive a car.
Energy settings for COM ports, USB hub and other devices are turned off, and the DIY adapter just works. The only issue is the disconnection, and I do not know what can I do next-have no idea about the error I got.
Any suggestions on how to solve this?
global option -l with value `log.txt'
global option -c with value `LogitechDrivingForcePro_G29.xml'
controller #1: option -p with value `COM3'
now reading arguments for controller #2
status flag is set
subpos flag is set
force_updates flag is set
GIMX 6.3 i386
Windows 7 SP1 x86
Kernel version: 6.1 (7601)
USB adapter detected, controller type is: G29 PS4.
found pass-through device 0x054c:0x05c4
Timer resolution: min=156001 max=5000 current=5000
using default refresh period: 5.00ms
0 1482783150.448500, wheel (-465)
0 1482783150.478500, wheel (-457)
0 1482783150.493500, wheel (-449)
0 1482783150.503500, wheel (-441)
0 1482783150.513500, wheel (-437)
...
Exiting
windows/async.c:165 queue_write: no space left in write queue for device (\\.\COM3)
The wheel is Logitech Driving Force Pro.
System is Windows 7 32 bit, running on a laptop.
For DIY adapter I use CP2102 adapter and Arduino Leonardo clone board. CP2102 is connected without any cables, directly into USB port.
USBDK is installed and I had no problems with controller authentication.
I use standard PS4 with the latest 4.07 firmware, trying to play DriveClub and DriveClub VR.
Everything-wheel,DIY adapter and DS4 are connected to USB hub, which is definitely not weakly powered.
In PS4 menu and in-game menus the wheel works for about 3-5 minutes or longer, but it disconnects in seconds or in a minute when I start the race and start to actively drive a car.
Energy settings for COM ports, USB hub and other devices are turned off, and the DIY adapter just works. The only issue is the disconnection, and I do not know what can I do next-have no idea about the error I got.
Any suggestions on how to solve this?