linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Transmit Power Level (TPL)
Date: Tue, 30 May 2006 16:18:55 +0200	[thread overview]
Message-ID: <1148998735.11251.3.camel@localhost> (raw)
In-Reply-To: <20060530140840.52436.qmail@web50504.mail.yahoo.com>

Hi Mahtab,

> I have been trying to work on the various signal strength values
> (RSSI, LQ & TPL) for quite sometime now. Though I am successful in
> getting RSSI & link quality (LQ) for my dongles (from both hcitool
> command & my own program), I always get Transmit Power level (TPL) as
> 0 - I have tested in various distances.
> My dongles are either ISSC or Broadcom-based (no CSR dongles) - all of
> them support "power-control" feature.

maybe ISSC and Broadcom simply don't implement it correct. Get yourself
a CSR based dongle and retest.

> And Marcel, I had also digged your code and saw that, you take a
> parameter for transmit power level calculation (the "type" field) in
> "hci_read_transmit_power_level" function and you set the parameter as:
> type = (argc>1) ? atoi(argv[1]) : 0;

Why don't you read the specification. If you give it 0 it will request
the current power level and with 1 it request the maximum power level.

> Finally, I only see "Get_Link_Quality" and "Read_RSSI" in bluetooth
> specification 1.0.B - no mention of "Transmit Power Level" there. My
> dongles are bluetooth 1.2, so, is there a possibility that they didn't
> provide transmit_power_level status value similar to that previous
> specification.

You should double check with "hcidump -X -V" that they really not report
and error and hcitool is doing it wrong. But it can happen that they
didn't actually implement transmit power level at all and they always
return the value 0.

> I think bluetooth specification 1.0.B is the free one available till
> now. If later versions are available, could anyone please provide me
> the link.

The current Bluetooth specification is version 2.0 and you should always
use this one.

Regards

Marcel




_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-05-30 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 14:08 [Bluez-users] Transmit Power Level (TPL) Mahtab Hossain
2006-05-30 14:18 ` Marcel Holtmann [this message]

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=1148998735.11251.3.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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).