Bouvrie, a reader of this blog, reported issues getting the sixaxis emulator to work.
The connection isn’t successful, even with a dongle that has a chip know to work (CSR bluecore4).
The result of our investigation – see issue 74 – is that the sixaxis doesn’t give the right ps3 bdaddr (bluetooth device address). It always gives the same wrong bdaddr.
Obviously, with a wrong ps3 bdaddr, the sixaxis emulator can’t connect to the ps3.
The reason why this sixaxis doesn’t give the right baddr is simple: it’s a fake one 🙁
Sounds like another teensy program is on the way…
Actually, I *think* I found an alternative way to get my proper PS3 bdaddr (basically by pairing a Windows Mobile smartphone with it & scanning the registry for the device pairing information). Now if I can figure out how to overrule the btaddr in sixemugui (or workaround the gui completely I gueess) I'd be golden.
Oh and FYI, editing sixpair.c, trying to set the fake bdaddr to the actual master bdaddr doesn't seem to change much:
user@ubuntu:~$ sudo ./sixpair_mod
Current Bluetooth master: XX:XX:XX:XX:XX:45 (the one reported by the fake controller)
Setting master bd_addr to XX:XX:XX:XX:XX:c0 (the one from my pairing)
user@ubuntu:~$ sudo ./sixpair_mod
Current Bluetooth master: XX:XX:XX:XX:XX:45 (still the fake one…)
Setting master bd_addr to XX:XX:XX:XX:XX:c0
It'd be nice if the sixemugui app would support commandline overrides to the detected addresses?
Plug the sixaxis, plug the bt dongle.
Start sixemugui.
File→Save
Open ~/.sixemugui/config (~ is your homedir)
Change the second value to the right ps3 bdaddr.
Save & Quit
Back to sixemugui: File→Refresh
I hope this helps!
File→Refresh doesn't work, it only refreshes the dongle list.
Restart Sixemugui instead.
Would it be possible to get this address by USB? Like when you are doing pairing with the teensy because your dongle address is fixed or because you don't want to leave your stock controller useless…what if that teensy app grabbed the BT address while plugged in, stored it, and then downloaded it back to the linux machine when plugged back in there? That way, people who have a clone controller or a 3RD party usb-only controller could still get this working?
Just a thought…I know you are busy and this is probably very low on your "To Do" list.
Yes it's possible, and it's already on my "unofficial" todo list.