public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Stockwell" <dstockwell@frequency-one.com>
To: "Khairulmizam Samsudin" <xource@gmail.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RSSI value in floating point
Date: Sun, 22 Jun 2008 17:41:22 -0500	[thread overview]
Message-ID: <001a01c8d4b9$192e4480$6701a8c0@freqonedev> (raw)
In-Reply-To: 485DB200.7000509@gmail.com


[-- Attachment #1.1: Type: text/plain, Size: 1720 bytes --]

The constraint is actually in the Bluetooth Specification, which specifies that RSSI is a single signed octet (byte) with a range of -127 to +127 in dB.  I have attached a screenshot of the section for you.

If you wish, you can return the signed integer returned from BlueZ and convert it yourself to a float, but recognize that the underlying value is an integer.

If you have not done so already, suggest you get a copy of the Bluetooth specification, which describes the BT protocol and stack in detail.  The specification is available from the Bluetooth SIG, at http://www.bluetooth.org/ 

Best regards,

David Stockwell
  ----- Original Message ----- 
  From: Khairulmizam Samsudin 
  To: BlueZ development 
  Sent: Saturday, June 21, 2008 8:59 PM
  Subject: Re: [Bluez-devel] RSSI value in floating point


  1. Thanks. That saved me a lot of time
  2. Assuming that I purchase a development kit. Would it be possible to modify bluetooth stack to achieve the objective?

  Regards
  xource

  Marcel Holtmann wrote: 
Hi,

  I have inspect bluez-libs codes and seems that some modification can 
make it happen. However, would the devices it self return RSSI in 
floating point?
    
simple answer is no. The RSSI is a signed integer.

Regards

Marcel



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
  

[-- Attachment #1.2: Type: text/html, Size: 3553 bytes --]

[-- Attachment #2: RSSI.JPG --]
[-- Type: image/jpeg, Size: 53292 bytes --]

[-- Attachment #3: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

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

      parent reply	other threads:[~2008-06-22 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21  3:20 [Bluez-devel] RSSI value in floating point Khairulmizam Samsudin
2008-06-21  4:57 ` Marcel Holtmann
2008-06-22  1:59   ` Khairulmizam Samsudin
2008-06-22 21:24     ` Andrew Kohlsmith (lists)
2008-06-22 22:07       ` Marcel Holtmann
2008-06-23  1:02         ` Andrew Kohlsmith (lists)
2008-06-22 22:41     ` David Stockwell [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='001a01c8d4b9$192e4480$6701a8c0@freqonedev' \
    --to=dstockwell@frequency-one.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=xource@gmail.com \
    /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