Homebrew Project Testers wanted: BtEmbedded, a new bluetooth stack

  • Thread starter Thread starter mudrik
  • Start date Start date
  • Views Views 7,167
  • Replies Replies 73
  • Likes Likes 17
Done!

WUPC does indeed auto-rotate very slowly. All buttons, dpad and sticks working fine.

Cool! So I we can forget about this controller for a while :-)

DS3 = virtual controller model appears inverted, and facing the back. I pressed L2, R2, L1, R1,Up, Down, Left, Right, Select, Start, Square, Triangle, Cross, Circle, L3, R3, and PS (can't see if it's doing anything at any point, but I pressed them anyway). When you press the PS button, the virtual controller faces front, and auto-exits the app.

DS4 = tried a sync, nothing. Immediately after, a USB connection, which pops up the virtual controller, and then auto-exits.

OK, I've added more logging to the DS3 controller, but it looks like the last part of the logs is missing. I wonder if you took out the SD card too quickly? Or maybe (more likely, actually) the program did not quit cleanly, but rather crashed, so it didn't save all the logs. Anyway, now I've disabled the accelerometer, so the controller should appear in the correct position, and you should be able to see if the buttons are pressed.

As for the DS4, it might go one step further with the BT connection, though I'm not sure. The controller is asking for a PIN code, to which this time we'll reply that we don't have one. Let's see how it reacts :-)

https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu10
 
  • Like
Reactions: niuus
I wonder if you took out the SD card too quickly? Or maybe (more likely, actually) the program did not quit cleanly, but rather crashed, so it didn't save all the logs.
Nope, I didn't. I always let it reach and load entries in the HBC again. Remember what I described about the PS button.

Anyway, now I've disabled the accelerometer, so the controller should appear in the correct position, and you should be able to see if the buttons are pressed.

As for the DS4, it might go one step further with the BT connection, though I'm not sure. The controller is asking for a PIN code, to which this time we'll reply that we don't have one. Let's see how it reacts :-)

https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu10
I think the DS4 pin is always 0000, same as DS.

Be back with in 10 with results.
Post automatically merged:

DS3 = after the USB connection, the virtual controller appears. No button response from anything, except PS button, which makes it auto-exit.

DS4 = tried a sync, nothing. Immediately after, a USB connection, which pops up the virtual controller, and then auto-exits.
 

Attachments

Last edited by niuus,
  • Like
Reactions: mudrik
Nope, I didn't. I always let it reach and load entries in the HBC again. Remember what I described about the PS button.

That's very strange. Here's another version that prints the logs to the screen (for the rest it has only minor changes). Can you please plug in the DS3 controller and verify if it continuously sends reports (at least when you press buttons) or if it stops printing very early (as the textual log does)? I wonder if it could be that the USB requests to the controller somehow interfere with writing to the SD card (though this would be very weird).

https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu11

No need to test other controllers. If the output is not too fast (and it increases when you press a button), taking a video would help.
 
That's very strange. Here's another version that prints the logs to the screen (for the rest it has only minor changes). Can you please plug in the DS3 controller and verify if it continuously sends reports (at least when you press buttons) or if it stops printing very early (as the textual log does)? I wonder if it could be that the USB requests to the controller somehow interfere with writing to the SD card (though this would be very weird).

https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu11

No need to test other controllers. If the output is not too fast (and it increases when you press a button), taking a video would help.
DS3 = connected by USB, waited for it to be "recognized" in the screen text. After that, pressing buttons doesn't report anything on screen, not even the PS button, which doesn't exit from the app now. Pressing reset did not close the app either. I had to force console power off by holding the button. No log was created.
 
I have a question after trading, is there any form to merge this with fakemote, but adding support to clone/fake ds4, ds3 and a large etc, of controllers?
 
I have a question after trading, is there any form to merge this with fakemote, but adding support to clone/fake ds4, ds3 and a large etc, of controllers?

Fakemote uses the embedded-game-controller library, so any USB controllers that we add to it will also become usable in fakemote. Bluetooth controllers unfortunately cannot be supported by Fakemote in its current form.

One thing that I'm planning to do is to try to patch games via brainslug (https://github.com/Chadderz121/brainslug-wii), which, if works, should be more reliable and also support BT controllers.
 
  • Love
  • Like
Reactions: lauty29 and XFlak
Fakemote uses the embedded-game-controller library, so any USB controllers that we add to it will also become usable in fakemote. Bluetooth controllers unfortunately cannot be supported by Fakemote in its current form.

One thing that I'm planning to do is to try to patch games via brainslug (https://github.com/Chadderz121/brainslug-wii), which, if works, should be more reliable and also support BT controllers.

Interesting i mean, i tried fakemote but i can't get working My clone Dualshock 4 controller, but with this is better, your work is amazing
 
Hi again, @niuus! I'm working on something else at the moment, but there's one more thing I need to clarify about the Wii U controller: you got it to work just pressing a button, or did you had to press the Sync button everytime? I'm asking because I read in the wiibrew wiki that the controller shuts itself down immediately if the data connection is established without first performing the authentication (which EGC is *not* currently doing), so I need to understand if this is true or if it can actually work on an unauthenticated connection.
 
  • Like
Reactions: niuus
Hi again, @niuus! I'm working on something else at the moment, but there's one more thing I need to clarify about the Wii U controller: you got it to work just pressing a button, or did you had to press the Sync button everytime? I'm asking because I read in the wiibrew wiki that the controller shuts itself down immediately if the data connection is established without first performing the authentication (which EGC is *not* currently doing), so I need to understand if this is true or if it can actually work on an unauthenticated connection.
Hey @mudrik! As I mentioned here, I just press almost any button for it to power on and "sync" when I enter the app. That's the only difference with any other app that has WUPC support currently: those turn the controller on automatically after a brief LED power off/power on when you go from the Homebrew Channel to the app. EGC Controller Test needs you to turn the controller On manually. I think the last version where everything was perfect for the WUPC was wiiu9.
 
Last edited by niuus,
  • Like
Reactions: mudrik
Is there any chance to connect third party ps3 USB controller
I have a Hori arcade stick for ps3
Yes, there is chance, if you are willing to spend some time to help test the changes. The first information I need is the USB product and vendor ID the device reports. Does it also have BT support? In any case, you could try the program I attached to this thread (maybe this version) and then send me the egc-sdl-test.log that will be created in the SD card?

Please start the program when the controller is disconnected, then connect it and try pressing some buttons. Quit with the Wii's Reset button.
 
  • Like
Reactions: Bariq7 and niuus
Hello @mudrik
About my DS3 arcade stick the full name is HORI REAL ARCADE Pro.V3 (PS3) i tried to contact it to the program via USB port when the program starts unfortunately every time I try to connect it I get a DSI error message and when I open the Folder in my SD card there is egc-sdl-test.log file but it empty.
And about your questions it doesn't support BT My controller USB ID is
VID: 0x0 FOD
PID : Ox0022
Revision: 0x1000
USB HID device

The Windows device description is
(USB Input Device.) If it matters
 
About my DS3 arcade stick the full name is HORI REAL ARCADE Pro.V3 (PS3) i tried to contact it to the program via USB port when the program starts unfortunately every time I try to connect it I get a DSI error message and when I open the Folder in my SD card there is egc-sdl-test.log file but it empty.

Thanks for trying it! It's strange that it crashes, it should do nothing if the device is not recognized. Do you have a regular Wii, or what console are you using? I've now added your IDs to the program, so that it should connect, but if it crashed before I suspect it might crash now as well: https://github.com/embedded-game-controller/egc-sdl-test/releases/tag/0.3-wiiu12
 
  • Like
Reactions: Bariq7
Thanks for adding my controller's ID, I'm using the OG Wii 001-RVL
i have another unmodded wii with different region i think it's a US Wii , i also tried the DS3 stick on Nintendont it didn't work maybe because it a third party controller, anyway I will try this new version on my both wiis maybe something changed
 
Last edited by Bariq7,

Site & Scene News