[PS4] DIY + RPI + DFGT

[pocopoco]

Hi, I have just build my DIY adapter, configured a Raspberry and recovered my DFGT.

This is my configuration:

• DIY USB adapter:
  USB to serial adapter: USB BUB II
  AVR USB board: Teensy 2.0
  Firmware: 5.8/EMUG29PS4/atmega32u4.hex
• Raspberry Pi 2 Model B (a01041)
• the console: PS4
• the controller: Logitech DFGT
• the game: Project Cars

Once connected all seems ok, the game see a G29 steering wheel and I can configure the buttons and navigate through PS and in game menu. When I try to race I can change the on board camera, but some seconds after the DFGT can't talk with the game. Sometimes the FF turn the steering wheel all to left/right and I need to reboot all.

This is the Gimx log:

Code: Select all

global option -l with value `loggimx.txt'
grab flag is unset
GIMX 5.9 ARMv6
Raspbian GNU/Linux 8.0 (jessie)
Linux 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 unknown
Bus 001 Device 011: ID 046d:c29a Logitech, Inc.
Bus 001 Device 009: ID 054c:05c4 Sony Corp.
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
        |__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
        |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 4: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M
native mode is already enabled for HID device 01:01:04 (PID=c29a)
Detected USB adapter: G29 PS4.
using default refresh period: 5.00ms
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x81)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_TIMED_OUT (endpoint=0x01)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x81)

I have seen here a problem with kernel 4.4. Is it again a problem in 4.4.13?

Thank you

[Matlo]

I did not use GIMX on RPi lately. I can't tell if there is a kernel regression or not.
The libusb error may also be due to a bad USB cable.

[pocopoco]

Bad cable on DS4 or usb adapter?

I will wait for someone else that uses rpi to see what kernel version they have.

Thank you

[Matlo]

Check the wheel cable and the wheel power supply cable.
Also check the RPi power supply.
https://www.raspberrypi.org/help/faqs/#powerReqs

[pocopoco]

Thanks for the link. I didn't know that Raspberry Pi model B+ and 2B can supply 600mA/1.2A to downstream USB peripherals, switchable by a firmware setting (variable max_usb_current=1 in /boot/config.txt).

The wheel cable is not replaceable and seems good. Its power supply works without problems with PS3/PC.

I will try using lsusb -v command to see if I can establish the devices current power consumption (not realtime consumption, but based device manufacturers specified info). I will connect one device at a time.

Code: Select all

lsusb -v | grep -e 'MaxPower' -e 'Bus [0-9]'

I have read this post where rpi is powered by PS4. I'm using external power supply (2A).

[pocopoco]

• USB to serial converter FT232RL (USB BUB II)

  Code: Select all

  Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
      MaxPower               90mA
  

• USB to serial converter CP2102

  Code: Select all

  Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
      MaxPower              100mA
  

• This is Sony DS4, perhaps 500mA only while recharging?

  Code: Select all

  Sony Corp.
      MaxPower              500mA
  

• Logitech steering wheel DFGT

  Code: Select all

  Logitech, Inc.
      MaxPower               80mA
  

about 700mA at max

Tonight I will try the wheel and another power supply

[zblad]

Hey I have the Logitech GT Force and for some reason this has only happened twice but I can feel the force in the steering wheel before I even start playing a game (by force I mean tension). Every other time I have played with the steering wheel there is no force until I am actually playing the game. What I have noticed is when I boot the raspberry pi the wheel starts to spin the kinda glitches a stops for a second and then continues (Almost like it doesn't have enough power) So I went and order a powered usb hub that was compatible with the pi and it does the same exact thing. I am not sure if it is a power issue or what! It is like it gets interrupted during calibration and the force wont work. I had an issue similar to yours and I think it has something to do with the power supply to your rpi how many amps is that rated at? I think I am using a 5a ipad charger for mine.

[pocopoco]

Tonight I will try the wheel and another power supply

No good news

I have tried:

1. max_usb_current=1
2. 3 different power supply 2A
3. 4 usb cable
4. 2 usb-serial converter with different chip (FT232, CP1202)

I can play some minute, after I lose the wheel (main led blink) and no button response.
The problem is only in game. Before I can set button, navigate through the menus without error.

@zblad: I have no problem with wheel calibration.

[Matlo]

I did a quick test and can confirm transfer errors happen with the latest RPi firmware.
I think this is a kernel regression.

On my setup the previous (working) firmware was a 4.1 one.
It can be installed with the following command:

Code: Select all

sudo rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f

[pocopoco]

Matlo, Thank you very very much!
Are there dependency error downgrading Kernel/firmware?
Have you also used "max_usb_current=1" switch?

I will try next days.
I have also found a power supply 5.3V 2A and I will buy a 20AWG usb to micro usb cable. Then no more power issues can happen

I have notice some rpi red led blinks, also before connect any usb devices. With recent rpi, this report voltage under 4.63V (APX803 supervisor).
Source: http://elinux.org/R-Pi_Troubleshooting# ... s_blinking
IMHO is strange with 2A [original] power supply, more than one, but... . So I will see with 5.3V source, also adafruit suggests this https://www.adafruit.com/product/2297

This adapter was specifically designed to provide 5.3V not 5V, but we still call it a 5V USB adapter. We did this on purpose to solve a problem that occurs often with USB-powered gadgets: they draw so much current than the resistance of the cable causes a voltage drop, so instead of 5V, the device sees 4.75V or so. To avoid this problem, we made the adapter 5.3V and the USB cable has extra-beefy 20AWG wires! This way, even at a full 2 Amp draw, the voltage at the end wont be lower than 4.9V

Thank you