Page 1 of 1
Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Mar 14, 2021 1:20 am
by Megahurtz
I just installed a Brook Wireless Fighting Board into an Astro City mini stick (it was a nightmare!). I've run into a strange problem with the mister though. The board defaults to PS4 mode when plugging in the USB cable. However, the mister doesn't detect the stick at all and won't register any inputs.
If I force the board into PS3 or PC mode, it works. I haven't tried Switch mode. I haven't gotten around to trying the Bluetooth pairing yet, but any idea why the PS4 mode completely fails?
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Mar 14, 2021 3:14 pm
by Megahurtz
Minor update after some more testing. PS3 mode works. Switch mode works. PS4 mode doesn't. PC mode doesn't.
I've also been trying to get it to show up in the Bluetooth pairing script in PS4 and PC mode, but neither of those work.
Bluetooth works fine with it on my PS5, so it would seem that something is up with the mister.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Mon Mar 15, 2021 10:48 pm
by Megahurtz
Did a little more experimenting. For reasons I can't explain, the stick is working in DS4 wired mode now. I can't pair it with the mister though. I'm able to successfully get the stick to enter pairing mode and my laptop can see it presenting itself as "DULASHOCK 4 Wireless Controller", but the mister does not see it at all.
I'm on mister v210305 OS v210315 and using a Zexmte BT dongle. The dongle works fine with my 8bitdo M30 BT, but nothing with the Brook board.
Is there anything I can try or a way to see more detailed info about what BT devices the mister sees?
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Wed Mar 24, 2021 11:12 pm
by Megahurtz
I figured out the USB IDs that are not working. When is PS4 mode, the usb hid device reports as 054c:09cc, which is a Dual Shock 4 (2nd Gen) [CUH-ZCT2x]. When I did my testing with a DS4 earlier, it should be noted that it was a 1st gen/CUH-ZCT1x that worked. In PC/X-input mode, it reports an ID of 0c12:0e32, which I can not find a reference to online.
Can anyone confirm a 2nd gen DS4 works with mister?
My next step is going to be adding an LED to the stick so I can tell when it is entering pairing mode.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sat Mar 27, 2021 12:14 am
by Megahurtz
Wired DS4 2nd gen works fine. I installed a LED but it isn't much help. It lights up when the stick is first plugged in and then turns off after a few seconds. I've come across posts that mention this is done to conserve battery life. Either I haven't been able to put the stick into pairing mode or the LED doesn't blink when that begins.
I think I'm going to try a fresh mister install to a new sd card to rule out any of my mister config.
Where does mister store the joystick definitions? Are they the media/fat/config/inputs/input_xxxx_xxxx_v3.map files? I noticed I already had one there for 054c:09cc. Wondering if the config from a legit DS4 could be interfering with the Brook board...
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Mar 28, 2021 3:01 pm
by Megahurtz
Tried deleting my input_054c_09cc_v3.map file and re-registering the stick in PS4 mode. No go. I did however figure out a reliable way to enter pairing mode when the board is set to PS3. Simply plug the stick in, unplug, then tap home/PS. That will begin pairing but I still haven't been able to get the mister to see it.
I put Mr. Fusion on a spare SD card and ran that to set up a clean install. Mister did not detect any inputs from the stick in PS4 mode when attempting to define it. I ran the update script on the new install. Still nothing detected in PS4 mode. Then I had the thought that maybe since mister asks to press right on the dpad to begin defining, that maybe when in PS4 mode the board was defaulting to LS mode. I tried manually toggling it to LS, DP, and RS modes just to see if any of them would be able to start the definition process. No such luck. I think I can rule out any of my own mister settings as causing problems at this point.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Mon Mar 29, 2021 11:30 pm
by Megahurtz
Here is what lsusb -v reports for the stick in PS4 mode:
Code: Select all
Bus 001 Device 007: ID 054c:09cc
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x054c
idProduct 0x09cc
bcdDevice 1.00
iManufacturer 1 Sony Interactive Entertainment
iProduct 2 Wireless Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 225
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 71
bInCollection 2
baInterfaceNr( 0) 1
baInterfaceNr( 1) 2
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0101 USB Streaming
bAssocTerminal 6
bNrChannels 2
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 2
bSourceID 1
bControlSize 1
bmaControls( 0) 0x03
Mute Control
Volume Control
bmaControls( 1) 0x00
bmaControls( 2) 0x00
iFeature 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 3
wTerminalType 0x0402 Headset
bAssocTerminal 4
bSourceID 2
iTerminal 0
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 4
wTerminalType 0x0402 Headset
bAssocTerminal 3
bNrChannels 1
wChannelConfig 0x0000
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 5
bSourceID 4
bControlSize 1
bmaControls( 0) 0x03
Mute Control
Volume Control
bmaControls( 1) 0x00
iFeature 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 6
wTerminalType 0x0101 USB Streaming
bAssocTerminal 1
bSourceID 5
iTerminal 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 1
bDelay 1 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 32000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 9
Transfer Type Isochronous
Synch Type Adaptive
Usage Type Data
wMaxPacketSize 0x0084 1x 132 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 6
bDelay 1 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 1
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 16000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0022 1x 34 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 507
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 5
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0001
Self Powered
And then here is what my legit DS4 v2 reports:
Code: Select all
Bus 001 Device 005: ID 054c:09cc
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x054c
idProduct 0x09cc
bcdDevice 1.00
iManufacturer 1 Sony Interactive Entertainment
iProduct 2 Wireless Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 225
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 71
bInCollection 2
baInterfaceNr( 0) 1
baInterfaceNr( 1) 2
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0101 USB Streaming
bAssocTerminal 6
bNrChannels 2
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 2
bSourceID 1
bControlSize 1
bmaControls( 0) 0x03
Mute Control
Volume Control
bmaControls( 1) 0x00
bmaControls( 2) 0x00
iFeature 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 3
wTerminalType 0x0402 Headset
bAssocTerminal 4
bSourceID 2
iTerminal 0
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 4
wTerminalType 0x0402 Headset
bAssocTerminal 3
bNrChannels 1
wChannelConfig 0x0000
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 5
bSourceID 4
bControlSize 1
bmaControls( 0) 0x03
Mute Control
Volume Control
bmaControls( 1) 0x00
iFeature 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 6
wTerminalType 0x0101 USB Streaming
bAssocTerminal 1
bSourceID 5
iTerminal 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 1
bDelay 1 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 32000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 9
Transfer Type Isochronous
Synch Type Adaptive
Usage Type Data
wMaxPacketSize 0x0084 1x 132 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1
bInterfaceSubClass 2
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 6
bDelay 1 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 1
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 16000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0022 1x 34 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 507
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 5
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 5
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
The differences are:
The second to last bInterval right near the bottom of each report. The real DS4 reports 5 while the Brook board reports 1.
Device status: 0x0001 for the Brook and 0x0000 for the DS4.
Bus powered vs self powered.
Here is dmesg for when the Brook board is connected:
Code: Select all
[ 2074.223989] usb 1-1.3: new full-speed USB device number 8 using dwc2
[ 2074.314159] usb 1-1.3: New USB device found, idVendor=054c, idProduct=09cc, bcdDevice= 1.00
[ 2074.314172] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2074.314179] usb 1-1.3: Product: Wireless Controller
[ 2074.314186] usb 1-1.3: Manufacturer: Sony Interactive Entertainment
[ 2074.333240] HID usage: 0x00010005, original interval: 1
[ 2074.333251] JS: endpoint->bInterval=1, interval=1
[ 2074.333256] HID usage: 0x00010005, applied interval: 1
[ 2074.333261] HID usage: 0x00010005, original interval: 5
[ 2074.333265] JS: endpoint->bInterval=5, interval=1
[ 2074.333269] HID usage: 0x00010005, applied interval: 1
[ 2074.333836] sony 0003:054C:09CC.0007: failed to retrieve feature report 0x81 with the DualShock 4 MAC address
[ 2074.344675] sony 0003:054C:09CC.0007: hidraw2: USB HID v81.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-ffb40000.usb-1.3/input3
[ 2074.344685] sony 0003:054C:09CC.0007: failed to claim input
The failed to retrieve feature report 0x81 with the DualShock 4 MAC address and especially the failed to claim input look suspicious... The Brook board is creating an event file in /dev/input but does not register as a js.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Apr 04, 2021 6:17 pm
by Ganondork
I did not succeed in connecting any mode. How exactly do you pair in PS3 mode? Step by step? And what dongle are you using?
Edit: Nevermind, I just realised that you also just managed to establish wired mode here.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Apr 11, 2021 3:19 pm
by Megahurtz
Ganondork wrote: ↑Sun Apr 04, 2021 6:17 pm
I did not succeed in connecting any mode. How exactly do you pair in PS3 mode? Step by step? And what dongle are you using?
Edit: Nevermind, I just realised that you also just managed to establish wired mode here.
Entering PS3 pairing mode is easy. Hold down 1P while plugging the stick in to force it to PS3 mode. The stick will work wired at that point. Unplug the usb cable and tap the PS/home button. The stick will enter BT pairing mode.
Unfortunately I can't get it to actually pair with the mister. I'm using a Zexmte BT dongle that has a CSR 8510 chipset.
Sorgelig says the PS4 and PC modes not working are a problem with the Linux kernel. After spending two or three weeks trying to get it working, I gave up for a while. I should go back and experiment with trying to get it working wirelessly again. I wanted to try that BT dongle on a PC to see if I could get the stick to pair to it. Porkchop thought the inability to pair, when it had been able to in the past based on his spreadsheet results, may have been due to changes in the BT pairing process that occurred last year.
I emailed Arcadeshock support and Brook support about the issues and never even got a response from either of them :\
has your experience with the WFB been, Ganondork? Same as mine, or are you seeing anything different?
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Apr 11, 2021 5:22 pm
by Brettster
I have just converted a fight stick to wireless with the Brook wireless fighting board, and this is working fine for me on MiSTer with BT wireless.
I'm using this USB BT Dongle
https://www.amazon.co.uk/gp/product/B08BHPQNJP/ Just a generic one by the looks of it
I paired the Stick using the PC input mode (held back and pressed the Home button) the LEDs blink fast) and the MiSTer sees it as a wireless controller.
The 1P LED light is on solid and then its just a matter of going into define joystick in the MiSTer OSD
not sure if it matters or not but I did update the Brook to the latest 1.5 fw
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Apr 18, 2021 5:00 pm
by Megahurtz
That is bizarre! I can't get the mister to even respond to any inputs when attempting to complete the define joystick routine. Any chance you could find out which chipset your BT dongle is using? Mine is a CSR 8510.
I also updated the WFB to the latest firmware (which is like a year old, IIRC).
I'm at a complete loss as to why mine won't work wired but yours does... Can you try the PS4 mode (hold down 2P when plugging in) and see if that works for you?
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Apr 18, 2021 8:58 pm
by Brettster
Not sure where to find the chipset info, my PC doesn't load drivers for it as my motherboard has BT built in.
as for holding down 2P, When I hold P2 and plug in the USB cable it just does nothing and goes into Charging mode on the stick.
If I unplug and then press the home button it connects as Player 1 via BT.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Mon Apr 19, 2021 10:55 pm
by Megahurtz
How did you initially pair the stick to your BT module? I’ve tried holding down the OSD button on the I/O board to enter pairing and also tried running the BT pairing script from the scripts menu. Neither can see my stick.
I’ve confirmed the stick pairs and works wirelessly with a PS5 and Switch, so I know it’s capable of working. Switch mode doesn’t seem to have any way of invoking the pairing process since the joycons have a physical sync button that the WFB doesn’t support.
I’m going to try reflashing the board from a different PC and see how that goes.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Mon May 10, 2021 6:43 pm
by hernan43
This thread (mostly) solved my issue with this board. I've been able to use it wirelessly just fine but had never gotten it to work wired. PS3 mode did the trick. I _thought_ I had tried it before but obviously I didn't as it is working great wired now.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Tue May 11, 2021 1:18 am
by Megahurtz
Brettster helped me work through some troubleshooting this past Saturday. We discovered that his board *didn't* work in PS4 mode when wired, matching my experience. He recorded a couple videos of him pairing the board to the mister using the BT pairing script. I couldn't get it to work at that time, but the next morning was still thinking about it and what possible differences we could have. We were both up to date on the software side of mister, had flashed the newest Brook firmware, and were using BT dongles that utilized the same CSR 8510 chipset.
Then it struck me that in his videos, Brettster had his stick unplugged when pairing it but mine was always plugged in. BINGO! That turned out to be the key.
With the stick unplugged, I was able to press the home button to turn it on, enter pairing mode, run the BT script, and the mister COULD SEE THE STICK!! I spent the better part of two months going crazy trying to figure this out and it turned out all I needed to do was not have the stick plugged in.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Tue May 11, 2021 1:25 am
by Megahurtz
hernan43 wrote: ↑Mon May 10, 2021 6:43 pm
This thread (mostly) solved my issue with this board. I've been able to use it wirelessly just fine but had never gotten it to work wired. PS3 mode did the trick. I _thought_ I had tried it before but obviously I didn't as it is working great wired now.
The tricky part is that the stick will function in PS4 mode after you plug the wire in, provided you paired it to BT beforehand. This has caused some confusion thinking that it works wired. I suspect it is like a DS4 on the PS4 where by default it always communicates via BT, even when plugged in. The Brook board has a "tournament mode" option you can activate with button combos that disables BT communication and operates only over wired usb, but I'm presuming this would lead to a non-working stick on the mister (for PS4 mode).
PS3 or PC mode might be better if you want the stick to toggle between using BT and sending data over USB. I've spent enough time just getting this working. Someone else can test that out
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Jul 25, 2021 5:10 am
by FrAshi
Just wanted to say thanks for this thread, your determination and reporting your findings. I just put together a stick with a WFB just for Mister and couldn’t get anything going. This thread solved my problem and I’m up and running on Bluetooth. Gracias!
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Jul 25, 2021 12:33 pm
by Megahurtz
You’re welcome! I spent so much time banging my head against the wall trying to figure this out, so I’m glad I was able to save someone else the trouble.
I still have a second Astro City stick I was planning on modding with another WFB. The whole ordeal was so traumatizing that I keep putting it off though
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Jul 25, 2021 2:08 pm
by FrAshi
The funny thing is that was exactly my original plan - I bought a WFB thinking about throwing it in the Astro City Mini stick, but once I realized that it would require drilling the case to get the cable/headset connector, I changed courses and bought a DIY case.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Aug 29, 2021 12:17 pm
by Megahurtz
I was hoping that the linux update this week would resolve issues with the wired mode operation of this board but it looks like nothing has changed. PS4 and PC/Xinput mode are still no go.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Wed Jun 14, 2023 10:52 pm
by Drexl
So, I got one of these to mod a stick and have been having trouble with it. Here's what I've seen when holding down a button and connecting it wired, and how it gets detected:
1P = PS3 controller - stick works wired, but will not pair wirelessly
2P = PS4 controller - stick does not work wired, but will pair wirelessly
1K = Nintendo Pro Controller - stick works wired, will pair wirelessly but the Mister won't respond to the stick unless it's wired
2K = Zeroplus Controller (whatever that is) - stick does not work, won't pair - this is Xbox 360 mode on the PC
I was hoping to switch between the MiSTer and PC, but it looks like I'll have to go through the whole process of connecting wired and re-pairing. I think the issue is that apparently it will only remember one unit of a console at a time. So since I have to use DS4 mode for both, I have to start over since it's a different "PS4." They have a video showing it switching between PS4 and Switch without powering down the consoles, but those are 2 different consoles.
BTW, there is a new firmware update released last week, after 3 years. It claims to have added wireless Xinput mode, but I haven't been able to get this working on MiSTer or PC.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Wed Sep 13, 2023 4:25 pm
by uKER
Did anyone ever get wireless Xinput to work?
The board works wireless on PS3, PS4 and Switch modes for me, just not Xinput.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Thu Sep 14, 2023 6:16 pm
by uKER
PSA: I finally figured out how to enable Wireless Xinput.
Full story here.
Short story:
-
Plug in USB cable while holding 2P to turn on the controller in PS4 mode.
-
Unplug cable.
-
Press Home to turn joystick on in wireless mode.
-
Press Home + 3K for 10 seconds to switch controller to Wireless Xinput mode (there's no hint of this way of switching modes anywhere else)
-
Press share + home for 2 seconds to enable Bluetooth pairing.
At this point the controller should become visible as "Wireless Fighting Board" (not "Wireless Controller" or anything else). Only when you see this name you'll know you're in the right mode.
Re: Brook Wireless Fighting Board (PS4 mode)
Posted: Sun Jan 21, 2024 3:58 pm
by Jocker
Sorry to bother you, I registered for this forum to ask you an important question for me... I'll tell you my problem:
I recently purchased a Brook Wireless board.
I have 2 problems:
1 - It only seems to work if I have a battery connected, even though I have a cable connected directly to the PC, if I don't have a battery it's like I have nothing. is this normal?
2- Assuming that problem 1 is normal, I cannot charge the battery in any way, I am thinking of connecting the board with a phone charger (5v / 0.8A), could you tell me step by step how to charge it? I tried with the cable but it didn't work at all.
Note: Always connect it to a PC (try with 3 different PCs)
I also tell you that when the battery seems to be about to run out, it enters an infinite loop where it detects and stops detecting the board, this is because it is not charged.
Thank you!