public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Singer <steven.singer@csr.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Detecting RSSI without connecting
Date: Thu, 25 Nov 2004 12:24:23 +0000	[thread overview]
Message-ID: <41A5CEF7.8090209@csr.com> (raw)
In-Reply-To: <qszu0rfnfil.fsf@mspacman.gpcc.itd.umich.edu>

Scott W Gifford wrote:
>         Features: 0xff 0xff 0x0d 0x38 0x00 0x00 0x00 0x00
[...]
> Am I doing this wrong, or is it possible that a Bluetooth 1.2 device
> doesn't support RSSI on inquiry?

As far as I'm aware, it's not mandatory. There's a features bit that
tells you whether it's supported. If I've counted right, it's bit 6 of
byte 3 (numbering from 0 in both cases). That is, it's:

  00 00 00 40 00 00 00 00

>From the features mask you've given, it looks like this device doesn't
support it.

>                                    If this device doesn't support it,
> can anybody recommend a device available in the US that does support
> RSSI on inquiry?

Modesty forbids.

Marcel's page at http://www.holtmann.org/linux/bluetooth/features.html
really needs updating to quote more features bits now that 1.2 devices
are starting to appear.

>                  Does the feature need to be supported on both the
> inquiring device and the inquired device to get RSSI information, or
> is support on the inquiring device enough?

It needs to be supported just on the inquiring device.

It's worth noting that although the inquiring device can accurately
(one hopes) report the received signal strength, there's no
requirement for the inquired device to trasnsmit at any particular
power. This might be an issue if the inquired devices are a mix of
different power classes and from different manufacturers. You may
also have to watch the effects of fading (but if you get more than one
report for a different device then you can just take the highest
RSSI to eliminate fading effects).

However, devices that are closer will tend to have a higher RSSI than
devices that are further away, so it's often a good place to start.

	- Steven



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



-------------------------------------------------------
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

  reply	other threads:[~2004-11-25 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09  0:03 [Bluez-users] Detecting RSSI without connecting Scott W Gifford
2004-11-09  0:29 ` Marcel Holtmann
2004-11-24 20:44   ` Scott W Gifford
2004-11-25 12:24     ` Steven Singer [this message]
2004-11-25 20:11       ` Marcel Holtmann
2004-11-25 20:08     ` Marcel Holtmann
2004-11-26  9:16       ` [Bluez-users] Firmware update & HID profile (Was: Detecting RSSI without connecting) Diego Liziero
2004-11-26 17:28         ` Marcel Holtmann
2004-11-30  4:44       ` [Bluez-users] Detecting RSSI without connecting Scott W Gifford
2004-11-30  5:31         ` Marcel Holtmann
2004-11-30  6:30           ` Scott W Gifford
2004-11-30  6:41             ` Marcel Holtmann
2004-12-02  0:36             ` Scott W Gifford

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=41A5CEF7.8090209@csr.com \
    --to=steven.singer@csr.com \
    --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