Since the beginning of my work with the sixaxis emulator (once again, based on the great work of Jim Paris), I have been looking for a way to get a dump of the bluetooth packets that are received and sent by a real sixaxis.
In May of this year, I was told by a reader of my blog that another French guy called Mikael Bouillot developed a sixaxis proxy. He is sharing his work on his website. I didn’t get it work after some early tests and didn’t go further until a few days. I asked Mikael some help to get his proxy working on my side, and he gave me the solution on a silver platter!
I’m now able to get the dump of the connection of any sixaxis.
Thanks to the analysis of these dumps, I hope to solve the following issues:
- the sixaxis emulator can’t be started if the PS3 is already started
- another instance of the emu process doesn’t work (probably the same issue as 1.)
- since the 3.50 firmware version, some more requests are sent by the PS3
Stay tuned, some great stuff should come very soon!
Hello Matlo How did you manage to use sixproxy? Was a patch necessary? I would like to give it a try if its not too difficult
Hi Joe!
You are the one who pointed out the sixaxis proxy, thanks a lot for that 🙂
Mikael gave me a bootable system with a patched kernel, but I'm not allowed to share the file.
It seems that the key to get the sixproxy work is a specific combination of kernel+module versions. And only one out of my 3 dongles works (the broadcom one).
If I have enough time after analyzing the dumps, I will try to make my own bootable system and I will share it.
Your welcome 🙂 Do you notice a significant decrease in input delay with the patch?
I'll wait patiently it looks like your on your way to make some progress in your project 🙂
I didn't noticed any latency difference, and my goal was not to use the sixaxis proxy to play.
It would be interesting to measure/compare the latency.