From: Jim Paris <jim@jtan.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: Bastien Nocera <hadess@hadess.net>,
linux-bluetooth@vger.kernel.org, linux-input@vger.kernel.org,
Ranulf Doswell <ralf@ranulf.net>,
"Pascal A . Brisset" <pascal44973@pabr.org>,
Marcin Tolysz <tolysz@gmail.com>,
Christian Birchinger <joker@netswarm.net>,
Filipe Lopes <falktx@gmail.com>, Alan Ott <alan@signal11.us>,
Mikko Virkkila <virkkila@kapsi.fi>
Subject: Re: [PATCH v2 0/3] Another try for the Sixaxis plugin
Date: Fri, 25 Mar 2011 11:31:05 -0400 [thread overview]
Message-ID: <20110325153105.GA26039@psychosis.jim.sh> (raw)
In-Reply-To: <20110324183247.3291e59e.ospite@studenti.unina.it>
Antonio Ospite wrote:
> With regard to that, I'd like to see some USB dumps of a Sixaxis
> talking with GameOS to check if the PS3 can turn off BT on the
> controller explicitly, can anyone help here? (Pascal? Do you have
> access to a USB analyzer?):
>
> The scenarios I am interested in are:
> 1. Connect a non-paired Sixaxis to the PS3 via USB
> 2. Connect an already paired Sixaxis to the PS3 via USB
> 3. Connect a Sixaxis already associated via BT to a PS3 via USB
Hi Antonio,
You asked me for this a while ago, sorry it took so long. I ran some
tests and put the log files here:
http://ps3.jim.sh/sixaxis/dumps/
There are comments in the file:
$ grep Comment sixaxis-pairing-tests-abbreviated.csv
0,,2,0:03.145.728,,,,,,Comment,,"1. Controller is a DS3 model CECHZC2U, bdaddr 00:24:33:E6:2C:3C"
0,,3,0:04.893.354,,,,,,Comment,,"2. PS3-1 is on and has bdaddr 00:13:a9:74:fe:57"
0,,4,0:05.592.405,,,,,,Comment,,"3. PS3-2 is on and has bdaddr 00:23:06:52:e4:e3"
0,,5,0:05.941.930,,,,,,Comment,,"4. Controller previously paired with 00:11:22:33:44:55"
0,,6,0:06.640.981,,,,,,Comment,,"5. Controller powered off with rear button"
0,,7,0:08.738.133,,,,,,Comment,,"6. About to plug controller into PS3-1 (off, wrong pairing)"
0,,285,0:16.314.138,,,,,,Comment,,"7. About to press PS button"
0,,914,0:20.841.170,,,,,,Comment,,"8. Unplugged controller"
0,,915,0:34.123.132,,,,,,Comment,,"9. Controller is now associated with PS3-1"
0,,916,0:41.113.639,,,,,,Comment,,"10. Controller powered off with rear button"
0,,917,0:41.113.639,,,,,,Comment,,"11. About to plug controller into PS3-1 (off, correct pairing)"
0,,1193,1:01.075.280,,,,,,Comment,,"12. Unplugged controller"
0,,1194,1:11.211.515,,,,,,Comment,,"13. Pressed PS button"
0,,1195,1:27.639.205,,,,,,Comment,,"14. Controller is now associated with PS3-1"
0,,1196,1:27.639.205,,,,,,Comment,,"15. About to plug controller into PS3-1 (associated with this PS3)"
0,,2311,1:41.665.351,,,,,,Comment,,"16. Unplugged controller"
0,,2312,1:44.112.029,,,,,,Comment,,"17. Paired and associated controller with PS3-2"
0,,2313,1:57.393.991,,,,,,Comment,,"18. About to plug controller into PS3-1 (associated with different PS3)"
0,,4585,2:26.172.515,,,,,,Comment,,"19. Unplugged controller"
> > The PS3 add-on keyboard, and the PS3 headset both use cable pairing. I
> > have them around, but was unable to get them to pair.
>
> I don't have the hardware so I never searched to see what the
> differences with the Sixaxis are.
I also did some quick captures of pairing the keypad (CECHZK1UC) and
original headset (CECHYA-0075). They are being paired with 00:13:a9:74:fe:57.
http://ps3.jim.sh/sixaxis/dumps/
-jim
next prev parent reply other threads:[~2011-03-25 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 10:04 [PATCH v2 0/3] Another try for the Sixaxis plugin Antonio Ospite
2011-02-25 10:04 ` [PATCH v2 1/3] Remove input/sixpair.c Antonio Ospite
2011-02-25 10:04 ` [PATCH v2 2/3] Re-add manager_get_default_adapter() Antonio Ospite
2011-02-25 10:04 ` [PATCH v2 3/3] Add sixaxis plugin: USB pairing and LEDs settings Antonio Ospite
[not found] ` <1298628292-8842-4-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2011-05-06 1:14 ` Bastien Nocera
[not found] ` <1304644488.16101.28.camel-7u+x0O+HiKDXoxyGr5pmpw@public.gmane.org>
2011-05-06 8:45 ` Antonio Ospite
2011-05-06 23:14 ` Antonio Ospite
[not found] ` <20110507011412.ba0ad1e9.ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2011-05-07 16:57 ` Bastien Nocera
2011-06-03 11:59 ` Antonio Ospite
[not found] ` <20110603135904.096660bc.ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2011-06-03 15:25 ` Bastien Nocera
2011-06-03 15:56 ` simon
2011-06-08 9:20 ` Antonio Ospite
[not found] ` <1298628292-8842-1-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2011-02-25 12:34 ` [PATCH v2 0/3] Another try for the Sixaxis plugin Bastien Nocera
2011-03-24 17:32 ` Antonio Ospite
2011-03-25 15:31 ` Jim Paris [this message]
2011-03-25 16:27 ` Antonio Ospite
2011-02-25 14:11 ` pascal44973
2011-02-25 15:49 ` Simon Kenyon
[not found] ` <4D67CF87.50600-YTvESifDTt4@public.gmane.org>
2011-02-25 16:02 ` Bastien Nocera
2011-04-30 11:31 ` Joakim Plate
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110325153105.GA26039@psychosis.jim.sh \
--to=jim@jtan.com \
--cc=alan@signal11.us \
--cc=falktx@gmail.com \
--cc=hadess@hadess.net \
--cc=joker@netswarm.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=ospite@studenti.unina.it \
--cc=pascal44973@pabr.org \
--cc=ralf@ranulf.net \
--cc=tolysz@gmail.com \
--cc=virkkila@kapsi.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).