Game Input MultipleXer

So I set the address correctly. The controller ID is 1. I switch it off. PS3 is still running.

Now I run emu with the proper addresses and id set to 1:

# ./emu 78:XX:XX:XX:13:B1 1 00:26:XX:XX:XX:16
connecting with hci1 = xxx to xxx psm 17
can't connect to control psm
emu: can't connect to control psm: Host is down

What is wrong?

Read the FAQ, there is a part about connection errors.

Ok theres a page: http://blog.gimx.fr/?p=25 (old tutorial)

I'd appreciate to move this onto wiki so I could edit and make it up-to-date. I am interested in running those programs by myself.

lzap wrote:Ok theres a page: http://blog.gimx.fr/?p=25 (old tutorial)

I'd appreciate to move this onto wiki so I could edit and make it up-to-date. I am interested in running those programs by myself.

How could the old tutorial help you for this issue?

My guess is that your sixaxis is not a genuine one. It's probably not giving the right ps3 bdaddr. There's something about that in the FAQ...

Matlo wrote:Read the FAQ, there is a part about connection errors.

All checked already.

Oh by the way I am using a custom build on Fedora 15

EDIT1:

Damn I have got Sweex BT dongle too

EDIT2:

Well my Sixaxis in the one that was sold with my PS3. It's original. I can also read its BD address using sixpair. I was already using it for playing games on Linux (paired it with my Linux).

My issue is probably a different one

The question is if is it the Sweex dongle making these problems... Also author of the sixaxis proxy stated that he had to patch linux bluetooth stack because of some timeout error. Maybe this patch is in Ubuntu and not in Fedora.

EDIT3:

Question: what number should be provided in the second emu param?

usage: emu <ps3-mac-address> <bt device number> <sixaxis number>

I tried with "1" because my controller from which I read the BT address was assigned 1. Is this correct?

Please don't double post (same rule as in any other forum).

Is your sixaxis currently paired with your ps3? Is emu able to turn the ps3 on?

I think it's not related to the sixproxy patch.

The bt device number is the bt dongle index as given by hciconfig.

Well I am always trying everything with PS3 turned on. I did not finy anything about turning on/off my PS3 in the tutorials. So - no - emu does not turn it on. Will try everything again.

So the device number should be index by hciconfig. Nice. I think I still have one here (zero is my ThinkPad x201 laptop bluetooth).

The ticket about fake controllers is closed, but I am not sure what is the outcome. Was it the BT dongle Sweex or really his controller?

Sorry for the multi-post.

It's said in the FAQ:

Make sure the sixaxis was already paired with your PS3 (the sixaxis should be able to turn on the ps3 remotely).

It was the controller, which was a counterfeit.

If emu can't turn the ps3 on, this means the controller is giving a wrong bdaddr (i.e. not paired with the ps3 or counterfeit).

Ok so I have a working sixaxis (can turn it on). I have connedted it, written down the PS3 and sixaxis addresses.

Now when I try to run emu I got:

can't connect to control psm
emu: can't connect to control psm: Permission denied

Interesting thing: When I try to turn my sixaxis again, it is blinking and does not reconnect to PS3. I need to plug it into PS3 and hit the PS button to re-pair. Then it works again. And it has the same bluetooth adress. Strange.

Did you got it working? Is sixemugui able to turn on the ps3 remotely?