That's where the software is currently stuck. The PANHAIs just don't send the 3rd connection request for the HID Service channel which the originals do just fine. What I've discovered so far is, that the actual pairing (sadly people misuse this term all the time the flashing LEDs do not necessarily indicate a pairing problem) works fine, it's the L2CAP connections which fail after responding to a connection and configuration request. The Logs the toolkit produces won't help much since the inner workings of the protocols involved aren't logged it would add too much of an overhead. I don't have much time either since I'd like to focus on development rather than reverse engineering. Since my knowledge of the whole Bluetooth specification (if I recall correctly, v4 has nearly a 1000 pages.) is very limited I wasn't yet able to decipher those dumps. I managed to tap into the communication between the Bluetooth controller chip and the micro controller (they communicate via UART thankfully) and actually could dump the streams they exchange when connecting to a genuine Sony PlayStation 3. Restarting now.I got some different "breeds" of those PANHAIs donated a few month ago and had them disassembled. Starting now.ĮCHO DS3 Service is running. REM Check to see if Ds3Service is runningįOR /F "tokens=3 delims=: " %%H in ('sc query "Ds3Service" ^| findstr " STATE"') do (ĮCHO DS3 Service is not running. Here it is if you would like to use it: OFF
I am also using Windows 10, so it should work for you. I made a quick batch script and threw it in an EXE for when I need to do this. The controller should now power on and sync automatically. Stop Ds3Service if it is currently running Start with the controller unplugged from the PC and powered off The controllers would show up but the service would not switch them to a 360 controller.Īfter I figured out a surefire process to get everything to work everything went smoothly. Sometimes it would work and sometimes nothing would make a difference. I frequently swap controllers between a couple of PCs and it was a nightmare trying to figure out the culprit. As a few others have said, the service most likely stopped working for some reason and needs to be restarted or is closed all together.
0 kommentar(er)
