(09-22-2015, 09:48 PM)Nefarius Wrote: [ -> ]Could you share the protocol it uses? I'd like to implement Rumble control on my Afterglow AP.2, I even mailed the vendor company but they just say it's not open, case closed 
So I was hoping it might use the same protocol since the Afterglow uses chip-on-board dies with no part number and I don't have a PS3 nor an USB capture device to reverse engineer it...
I looked through the code and unfortunately the rumble is only supported while the quadstick is emulating a Dual Shock 3, not when using the Afterglow emulation. These are the messages showing up at the Device Control endpoint (not the Joystick Interface Out endpoint which receives most of the OUT messages from the host) when rumble is being sent from a CronusMax running a controller rumble test script:
Dual Shock 3 mode, no rumble:
CALLBACK_HID_Device_ProcessOutputReport:
7FD00410 : 01 00 96 00 96 00 00 00 00 00 02 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 00
7FD00430 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dual Shock 3 mode, rumble A 100%
CALLBACK_HID_Device_ProcessOutputReport:
7FD00410 : 01 00 96 00 96 FF 00 00 00 00 02 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 00
7FD00430 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dual Shock 3 mode, rumble B 100%
CALLBACK_HID_Device_ProcessOutputReport:
7FD00410 : 01 00 96 FF 96 00 00 00 00 00 02 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 00
7FD00430 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The rumble message is not the full 64 bytes, that is just what the debug routine prints. I'm using nxpUSBlib for the USB library on an LPC2388 and the message showing up at the Device control endpoint instead of the Joystick HID interface out endpoint might be a quirk of that combination. It's been a while since I was working with that part of the code.
My Afterglow controller does not have rumble, but as far as I can tell, when the quadstick is emulating an Afterglow, the CronusMax is not sending any rumble messages. I'll try to do some more testing with a PS3 game console instead of the CronusMax.
Hello, I am currently experiencing some difficulties with this.
My Afterglow AP.2 always has the Left Motor on at max.
Hi i can't make my controller work over bluetooth. HCI wasn't in ScpControl.ini so i added it:
[HCI]
; DualShock 3 (partial) product name
SupportedName = PLAYSTATION®3
; ???
SupportedName = Navigation Controller
; DualShock 4 product name
SupportedName = Wireless Controller
; Quad Stick (
http://www.quadstick.com/)
SupportedName = Quad Stick
; RDA bt
SupportedName = RDA bt
This last one is my controller!
When i try to connect my leds controller are blinking but nothing happends.
In attachment there is the log.
Can you help me? Thank you
(09-23-2015, 12:18 PM)busamamba Wrote: [ -> ]Hi i can't make my controller work over bluetooth. HCI wasn't in ScpControl.ini so i added it:
[HCI]
; DualShock 3 (partial) product name
SupportedName = PLAYSTATION®3
; ???
SupportedName = Navigation Controller
; DualShock 4 product name
SupportedName = Wireless Controller
; Quad Stick (http://www.quadstick.com/)
SupportedName = Quad Stick
; RDA bt
SupportedName = RDA bt
This last one is my controller!
When i try to connect my leds controller are blinking but nothing happends.
In attachment there is the log.
Can you help me? Thank you
You needed add new values vid & pid yours bluetooth to ScpControl.ini in list and reinstall scp driver. You don't need add HCI, just vid & pid
Code:
[Bluetooth Dongles]
; GUID to identify supported bluetooth dongles
; DO NOT CHANGE unless you know what you are doing!
DeviceGuid = {2F87C733-60E0-4355-8515-95D6978418B2}
; HIDs of bluetooth dongles to replace drivers for
; EXPERIMENTAL: add you own HIDs here for tests
HardwareId = USB\VID_your values&PID_your values
(09-23-2015, 02:37 PM)DANTE1613 Wrote: [ -> ]You needed add new values vid & pid yours bluetooth to ScpControl.ini in list and reinstall scp driver. You don't need add HCI, just vid & pid
Code:
[Bluetooth Dongles]
; GUID to identify supported bluetooth dongles
; DO NOT CHANGE unless you know what you are doing!
DeviceGuid = {2F87C733-60E0-4355-8515-95D6978418B2}
; HIDs of bluetooth dongles to replace drivers for
; EXPERIMENTAL: add you own HIDs here for tests
HardwareId = USB\VID_your values&PID_your values
My bth dongle is already in that list
HardwareId = USB\VID_04CA&PID_300B
(09-23-2015, 12:48 AM)QuadStick Wrote: [ -> ]I looked through the code and unfortunately the rumble is only supported while the quadstick is emulating a Dual Shock 3, not when using the Afterglow emulation. These are the messages showing up at the Device Control endpoint (not the Joystick Interface Out endpoint which receives most of the OUT messages from the host) when rumble is being sent from a CronusMax running a controller rumble test script:
Dual Shock 3 mode, no rumble:
CALLBACK_HID_Device_ProcessOutputReport:
7FD00410 : 01 00 96 00 96 00 00 00 00 00 02 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 00
7FD00430 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dual Shock 3 mode, rumble A 100%
CALLBACK_HID_Device_ProcessOutputReport:
7FD00410 : 01 00 96 00 96 FF 00 00 00 00 02 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 00
7FD00430 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dual Shock 3 mode, rumble B 100%
CALLBACK_HID_Device_ProcessOutputReport:
7FD00410 : 01 00 96 FF 96 00 00 00 00 00 02 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 FF 00 01 00 01 00
7FD00430 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The rumble message is not the full 64 bytes, that is just what the debug routine prints. I'm using nxpUSBlib for the USB library on an LPC2388 and the message showing up at the Device control endpoint instead of the Joystick HID interface out endpoint might be a quirk of that combination. It's been a while since I was working with that part of the code.
My Afterglow controller does not have rumble, but as far as I can tell, when the quadstick is emulating an Afterglow, the CronusMax is not sending any rumble messages. I'll try to do some more testing with a PS3 game console instead of the CronusMax.
If I send this over the control channel the controller resets
it's definitely receiving and processing the command but rather responds with a crash than a rumble. Damn Afterglow stuff
Nefarius, I'm posting my logs...I have the fake DS3 Panhai version. Still no BT, but I see improvements, thanks!
edit: Also, using the SixAxisPairTool, I've noticed the Panhai resets the master back to 00:00:00:00:00:00. Is this a problem?
(09-23-2015, 06:41 PM)OfAnthony Wrote: [ -> ]Nefarius, I'm posting my logs...I have the fake DS3 Panhai version. Still no BT, but I see improvements, thanks!
edit: Also, using the SixAxisPairTool, I've noticed the Panhai reses the master back to 00:00:00:00:00:00. Is this a problem?
Maybe try click reset button on gamepad. I too have Panhai controller, but he normally conected over bluetooth, but no have vibration on it.
(09-23-2015, 07:01 PM)DANTE1613 Wrote: [ -> ]Maybe try click reset button on gamepad. I too have Panhai controller, but he normally conected over bluetooth, but no have vibration on it.
BETA with (possible) PANHAI Fix available!
Thanks to the user BeNeMeSh who provided his machine for tests we have progress on fake Bluetooth detection and rumble (vibration) support, you're welcome to test!
Nefarius, Thank you very much. Its working now.
just 145.81mb used!!!