Linux bluetooth development
 help / color / mirror / Atom feed
From: Ichigo Bleach <sara200t@hotmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Is "HCI_Read_Rssi" is the only option to get	RSSI	value from "Non-discoverable" Device?
Date: Wed, 15 Oct 2008 14:07:48 -0500	[thread overview]
Message-ID: <BLU127-W16B80F725862BEFF8D88BF88300@phx.gbl> (raw)
In-Reply-To: <1224084214.4764.14.camel@californication>


Thank you Marcel for your reply.

As you pointed out, I went back and read the spec and found that it is absolutly true.

My understanding, Read_RSSI will give the result after compare with the golden recieve power range, instead the Inq_result_with_rssi will just give me the real power recieve in dBm.

I think I would be better off go with the inquiry option. However, my next concern is:

1.) Can the Non-discoverable mode device response to the inquiry_result_with_rssi of the connected device or not-conected but pair device(Known the address)?

Thank you very much for your time.

Best regards,


> From: marcel@holtmann.org
> To: bluez-users@lists.sourceforge.net
> Date: Wed, 15 Oct 2008 17:23:34 +0200
> Subject: Re: [Bluez-users] Is "HCI_Read_Rssi" is the only option to get RSSI value from "Non-discoverable" Device?
>
> Hi,
>
>> I am trying to develop bluetooth positioning system. I am at the point of successfully getting the RSSI value using the Inquiry_result_with_rssi with no problem.
>> However, as the security is concerned, I do not want leave the other Bluetooth device in discoverable mode. Therefore, sending inquiry_result_with_rssi will not work any more due to, in non-discoverable mode, the other Bluetooth will not reply to my inquiry.
>
> the RSSI value you get from Inquiry_Result_With_RSSI and from Read_RSSI
> are _not_ the same.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users

_________________________________________________________________


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-10-15 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 12:11 [Bluez-users] Is "HCI_Read_Rssi" is the only option to get RSSI value from "Non-discoverable" Device? Ichigo Bleach
2008-10-15 15:23 ` Marcel Holtmann
2008-10-15 19:07   ` Ichigo Bleach [this message]
2008-10-23  4:52     ` Marcel Holtmann

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=BLU127-W16B80F725862BEFF8D88BF88300@phx.gbl \
    --to=sara200t@hotmail.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