Can't connect Dual Shock 4

[Michael Cassera]

So I purchased a Dual Shock 4 controller to use with my newly purchased Unijoysticle 2 and I've had no luck getting it to connect.  I've tested the controller with my Linux box and it connect and worked properly without any issues.

I've followed the troubleshooting guide. Cleared the Unijoysticle and set the controller to scan mode with now luck.  I've upgraded the firmware from 3.0.0-rc0 to 3.0.0-rc1 and still no luck. 

Here is the upgrade:

$ esptool --port /dev/ttyUSB0 --baud 115200 --before default_reset --after hard_reset write_flash 0x0000 bluepad32-unijoysticle-full-v3.0.0-rc1.bin
esptool.py v2.8
Serial port /dev/ttyUSB0
Connecting......
Detecting chip type... ESP32
Chip is ESP32D0WDQ5 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 10:97:bd:d2:46:74
Enabling default SPI flash mode...
Configuring flash size...
Auto-detected Flash size: 4MB
Erasing flash...
Took 2.92s to erase flash block
Wrote 608256 bytes at 0x00000000 in 59.2 seconds (82.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

And here is the Unijoysticle on bootup. after this, it just sits there.

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6620
ho 0 tail 12 room 4
load:0x40078000,len:14780
load:0x40080400,len:3784
entry 0x40080694
[0;32mI (29) boot: ESP-IDF v4.4-114-g7c986a64c7 2nd stage bootloader [0m
[0;32mI (29) boot: compile time 17:06:45 [0m
[0;32mI (29) boot: chip revision: 3 [0m
[0;32mI (33) boot_comm: chip revision: 3, min. bootloader chip revision: 0 [0m
[0;32mI (40) boot.esp32: SPI Speed      : 40MHz [0m
[0;32mI (45) boot.esp32: SPI Mode       : DIO [0m
[0;32mI (49) boot.esp32: SPI Flash Size : 4MB [0m
[0;32mI (54) boot: Enabling RNG early entropy source... [0m
[0;32mI (59) boot: Partition Table: [0m
[0;32mI (63) boot: ## Label            Usage          Type ST Offset   Length [0m
[0;32mI (70) boot:  0 nvs              WiFi data        01 02 00009000 00006000 [0m
[0;32mI (78) boot:  1 phy_init         RF data          01 01 0000f000 00001000 [0m
[0;32mI (85) boot:  2 factory          factory app      00 00 00010000 00100000 [0m
[0;32mI (93) boot:  3 coredump         Unknown data     01 03 00110000 00010000 [0m
[0;32mI (100) boot: End of partition table [0m
[0;32mI (104) boot_comm: chip revision: 3, min. application chip revision: 0 [0m
[0;32mI (112) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=16214h ( 90644) map [0m
[0;32mI (153) esp_image: segment 1: paddr=0002623c vaddr=3ffbdb60 size=05850h ( 22608) load [0m
[0;32mI (162) esp_image: segment 2: paddr=0002ba94 vaddr=40080000 size=04584h ( 17796) load [0m
[0;32mI (170) esp_image: segment 3: paddr=00030020 vaddr=400d0020 size=51c34h (334900) map [0m
[0;32mI (291) esp_image: segment 4: paddr=00081c5c vaddr=40084584 size=127bch ( 75708) load [0m
[0;32mI (322) esp_image: segment 5: paddr=00094420 vaddr=50000000 size=00010h (    16) load [0m
[0;32mI (334) boot: Loaded app from partition at offset 0x10000 [0m
[0;32mI (334) boot: Disabling RNG early entropy source... [0m
[0;32mI (346) cpu_start: Pro cpu up. [0m
[0;32mI (346) cpu_start: Starting app cpu, entry point is 0x40081200 [0m
[0;32mI (0) cpu_start: App cpu up. [0m
[0;32mI (362) cpu_start: Pro cpu start user code [0m
[0;32mI (362) cpu_start: cpu freq: 160000000 [0m
[0;32mI (363) cpu_start: Application information: [0m
[0;32mI (367) cpu_start: Project name:     bluepad32-app [0m
[0;32mI (372) cpu_start: App version:      3.0.0-rc1 [0m
[0;32mI (378) cpu_start: Compile time:     Feb  6 2022 17:06:41 [0m
[0;32mI (384) cpu_start: ELF file SHA256:  56a2394a274bd24e... [0m
[0;32mI (390) cpu_start: ESP-IDF:          v4.4-114-g7c986a64c7 [0m
[0;32mI (396) heap_init: Initializing. RAM available for dynamic allocation: [0m
[0;32mI (403) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM [0m
[0;32mI (409) heap_init: At 3FFB7CD8 len 00000328 (0 KiB): DRAM [0m
[0;32mI (415) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM [0m
[0;32mI (421) heap_init: At 3FFD0DC8 len 0000F238 (60 KiB): DRAM [0m
[0;32mI (427) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM [0m
[0;32mI (434) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM [0m
[0;32mI (440) heap_init: At 40096D40 len 000092C0 (36 KiB): IRAM [0m
[0;32mI (448) esp_core_dump_flash: Init core dump to flash [0m
[0;32mI (452) esp_core_dump_flash: Found partition 'coredump' @ 110000 65536 bytes [0m
Bluepad32 (C) 2016-2021 Ricardo Quesada and contributors.
Version: v3.0.0-rc1
BTStack: Copyright (C) 2017 BlueKitchen GmbH.
Hardware detected: Unijoysticle 2+
[0;32mI (511) gpio: GPIO[5]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (521) gpio: GPIO[12]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (531) gpio: GPIO[13]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (541) gpio: GPIO[14]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (551) gpio: GPIO[16]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (561) gpio: GPIO[17]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (571) gpio: GPIO[18]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (581) gpio: GPIO[19]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (591) gpio: GPIO[21]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (591) gpio: GPIO[22]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (601) gpio: GPIO[23]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (611) gpio: GPIO[25]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (621) gpio: GPIO[26]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (631) gpio: GPIO[27]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (641) gpio: GPIO[32]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (651) gpio: GPIO[33]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 [0m
[0;32mI (661) gpio: GPIO[15]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3 [0m
Platform: unijoysticle2
Gap security level: 2
Periodic Inquiry: max=5, min=4, len=3
[0;32mI (681) BTDM_INIT: BT controller compile version [30c8196] [0m
[0;32mI (681) system_api: Base MAC address is not set [0m
[0;32mI (691) system_api: read default base MAC address from EFUSE [0m
[0;32mI (701) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07 [0m
BTstack up and running at 10:97:BD:D2:46:76
HCI not ready, cannot send packet, will again try later. Current state idx=1
HCI not ready, cannot send packet, will again try later. Current state idx=2
BTstack up and running on 10:97:BD:D2:46:76.
Stored link keys:
.

Any ideas to point me in the right direction would be awesome.  

Thanks,

Mike

[Ricardo Quesada]

Hi Mike,

The output looks good to me.

Also, if the DualShock 4 can connect to the Linux machine, that's a good sign.

It is weird that it doesn't even appear in the log... usually you should see something like "00:xx:yy:zz:11:22 discovered..." and then it will try to connect to it.

I assume that you are trying to connect it using the "Share + PS" button, correct?

https://www.pcmag.com/how-to/how-to-use-a-ps4-dualshock-4-controller-on-a-pc

Another thing to consider:
 - is it a genuine or a clone? Could you send me the link from where you purchased it?

    DualShock 4 is one of the better supported gamepads by the Unijoysticle.

    But I only tested it with Genuine controllers, and with the 8bitdo in Mac mode (which is Dualshock 4 mode) and it works Ok.

    But I haven't tried any clone.

 - Make sure the gamepad is not trying to connect to a PlayStation or a PC.. or a phone... make sure all those devices are NOT in "discover new bluetooth devices".

... and please, try connecting again... perhaps 3 or 4 more times.  Thanks.

--
You received this message because you are subscribed to the Google Groups "Unijoysticle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unijoysticle...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unijoysticle/a6b8dce3-82de-40a2-bc3e-155c67728431n%40googlegroups.com.

[Michael Cassera]

It was the phone. 

I had turned off the bluetooth on the computer earlier when I was trying to connect, I didn't think about the phone. I guess the phone is always in connect mode?

Regardless, I turned off the bluetooth on my phone and tried again and it connected right away. Tried a few games and it works great.  

As for where I got the controller, it is a Sony refurbished controller from New Egg. 

https://www.newegg.com/p/2J5-00M5-00014?Description=dualshock%204&cm_re=dualshock_4-_-2J5-00M5-00014-_-Product&quicklink=true 

Thanks so much for the quick response and pointing me in the right direction,

Mike

[Ricardo Quesada]

Great. good to know that it is working Ok now.

Regarding the phone, it's weird... My understanding is that they are not in "discover" mode by default.

Not sure whether the problem was with the phone... or something else... strange.

To view this discussion on the web visit https://groups.google.com/d/msgid/unijoysticle/c1b4d163-b3fb-4e23-8617-f7679d3b2a75n%40googlegroups.com.

[Ricardo Quesada]

update:

I ordered DualShock 4 and DualShock 3, both refurbished, from NewEgg.

They connect Ok, but it seems that they are fakes. Status:

 - DualShock 3 fake: Player LED and rumble: Not working

- DualShock 4 fake: Lightbar LED and rumble: Not working.

... perhaps it is a bug in Bluepad32... or perhaps they just don't work... I'll need to dig further.

[Michael Cassera]

Thanks for the update. Sucks to hear New Egg is settling fakes. Good to know.