All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael <michael@bungtopia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] RSSI from rfcomm
Date: Wed, 25 May 2005 01:40:50 +0930	[thread overview]
Message-ID: <4293520A.9010303@bungtopia.com> (raw)
In-Reply-To: <1116366629.10063.119.camel@pegasus>

Thanks for that. I think I have code that will work now. This is the 
line that I pass to the hci_read_rssi() method: 
hci_read_rssi(client_sock, htobs(rfconn.hci_handle), &rssi, 25000)

My app doesn't have fancy error messages so I spent ages trying to work 
out why it doesnt work, no luck, but  rctest gives the error "Can't get 
RFCOMM connection information: Protocol not available (92)"

Do you know what can cause this error, or give me a head start on how to 
track it down?

Im using a complete install of fedora core 3

Thank you
-michael

Marcel Holtmann wrote:

>Hi Michael,
>
>  
>
>>I'm using pretty standard sockets to create a bluetooth connection. I 
>>can communicate fine with my J2ME app however I was wondering if it is 
>>at all possible to read the RSSI from an RFCOMM layer connection. I can 
>>read it fine if I make a lower level connection, but this is not at all 
>>suited to my application..
>>
>>So, how can I read the RSSI when I dont have access to all the data I 
>>need to pass to the hci_read_rssi() method??
>>    
>>
>
>you only need the ACL connection handle and you can get this with a
>getsockopt() call through RFCOMM. Check rctest for an example.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Oracle Space Sweepstakes
>Want to be the first software developer in space?
>Enter now for the Oracle Space Sweepstakes!
>http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>  
>




-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-05-24 16:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 23:08 [Bluez-devel] Bluetooth v2 Peter Robinson
2005-05-14 23:22 ` Marcel Holtmann
2005-05-14 23:32   ` Peter Robinson
2005-05-15  0:12     ` Marcel Holtmann
2005-05-17 15:35       ` [Bluez-devel] RSSI from rfcomm michael
2005-05-17 21:50         ` Marcel Holtmann
2005-05-24 16:10           ` michael [this message]
2005-05-24 17:05             ` Marcel Holtmann
2005-05-25  3:35               ` michael
2005-05-25  9:17                 ` Marcel Holtmann
2005-05-29 10:18                   ` michael
2005-05-29 10:36                     ` 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=4293520A.9010303@bungtopia.com \
    --to=michael@bungtopia.com \
    --cc=bluez-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.