From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D7DA.0CBBFF36" Message-ID: From: "Cruz, Maria" To: Subject: [Bluez-users] bluetooth sniff mode Sender: bluez-users-admin@lists.sourceforge.net Errors-To: bluez-users-admin@lists.sourceforge.net Reply-To: bluez-users@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ users List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 1 Dec 2004 14:14:58 -0500 This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D7DA.0CBBFF36 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Marcel wrote: Hi Maria, ... I don"t know of a command that can read the current power safe mode, but you can monitor the HCI mode changed event. Regards Marcel=20 =20 Thanks Marcel, Here is the output from my command: # hcitool cmd 0x02 0x0003 0x01 0x00 0x00 0x05 0x00 0x01 0x06 0x00 0x10 0x00 < HCI Command: ogf 0x02, ocf 0x0003, plen 10 01 00 00 05 00 01 06 00 10 00 > HCI Event: 0x0f plen 4 00 01 03 08 I looked in the "BLUETOOTH SPECIFICATION Version 1.1" for the HCI Event of 0x0f. I am not confident in reading the specification. But I think this event 0x0f =3D Command Status. And the Event Parameters: (0) "00" = =3D Command currently in pending.=20 =20 Not sure if this indicates a success (or just pending not sure yet of success). Additionally, I am using bluez-libs&bluez-utils2.10. Should I reference the "BLUETOOTH SPECIFICATION Version 2.0 + EDR" instead? I found version 2.0 at "Bluetooth.org" web site. AND the version 2.0 spec is slightly different. For example the error codes listed in 2.0 are different. =20 =20 Sometimes with the hci cmd for sniff mode I get: # hcitool cmd 0x02 0x0003 0x01 0x01 0x00 0x00 0x05 0x00 0x01 0x06 0x00 0x10 0x00 < HCI Command: ogf 0x02, ocf 0x0003, plen 11 01 01 00 00 05 00 01 06 00 10 00 > HCI Event: 0x0f plen 4 02 01 03 08 =20 Here the HCI Event indicates "Status" of 0x02. =20 Version 1.1 =3D 0x02 No Connection. Version 2.0 =3D 0x02 Unknown Connection Identifier =20 Maybe it is only semantics... either way I do not understand what either really mean. For the sniff mode I have setup a bnep connection. I can ping "host", I have static IPs setup. And=20 hcitool con Connections: < ACL 00:02:72:41:2E:1D handle 1 state 1 lm MASTER =20 Should this indicate "SLAVE"? Somes times hcitool con will show SLAVE instead. Your advice on what spec to use and how to decipher hictool output is appreciated. maria =20 =20 =20 =20 =20 ------_=_NextPart_001_01C4D7DA.0CBBFF36 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Marcel wrote:

Hi Maria, … I don"t know of a = command that can read the current power safe mode, but you can monitor the HCI mode = changed event. Regards Marcel

 

Thanks Marcel,

Here is the output from my = command:

# hcitool cmd 0x02 0x0003 0x01 0x00 0x00 0x05 0x00 0x01 0x06 = 0x00 0x10 0x00

< HCI Command: ogf 0x02, ocf 0x0003, plen = 10

  01 00 00 05 00 01 06 00 10 = 00

> HCI Event: 0x0f plen 4

  00 01 03 08

I looked in the “BLUETOOTH = SPECIFICATION Version 1.1” for the HCI Event of 0x0f.  I am not confident in = reading the specification.  But I think this event 0x0f =3D Command = Status.  And the Event Parameters:  (0) “00” =3D Command currently = in pending.

 

Not sure if this indicates a success (or just = pending not sure yet of success).  Additionally, I am using bluez-libs&bluez-utils2.10.  Should I reference the = “BLUETOOTH SPECIFICATION Version 2.0 + EDR” instead?  I found version = 2.0 at “Bluetooth.org” web site.  AND the version 2.0 spec is slightly different.  = For example the error codes listed in 2.0 are different.  =

 

Sometimes with the hci cmd for sniff mode I = get:

# hcitool cmd 0x02 0x0003 0x01 0x01 0x00 0x00 0x05 = 0x00

0x01 0x06 0x00 0x10 0x00

< HCI Command: ogf 0x02, ocf 0x0003, plen = 11

  01 01 00 00 05 00 01 06 00 10 = 00

> HCI Event: 0x0f plen 4

  02 01 03 08

 

Here the HCI Event indicates = “Status” of 0x02. 

Version 1.1 =3D 0x02 No = Connection.

Version 2.0 =3D 0x02 Unknown Connection = Identifier

 

Maybe it is only semantics… either way = I do not understand what either really mean.  For the sniff mode I have = setup a bnep connection.  I can ping “host”, I have static IPs = setup.  And

hcitool con

Connections:

        < ACL = 00:02:72:41:2E:1D handle 1 state 1 lm MASTER

 

Should this indicate = “SLAVE”?  Somes times hcitool con will show SLAVE instead.  Your advice on what = spec to use and how to decipher hictool output is = appreciated.

maria

 

 

 

 

 

------_=_NextPart_001_01C4D7DA.0CBBFF36-- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users