Homebrew Project Testers wanted: BtEmbedded, a new bluetooth stack

  • Thread starter Thread starter mudrik
  • Start date Start date
  • Views Views 5,668
  • Replies Replies 62
  • 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.
 

Site & Scene News

Popular threads in this forum