All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emiliano Heyns <emiliano.heyns@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] hcitool scan times
Date: Sat, 19 Feb 2005 14:17:17 +0100	[thread overview]
Message-ID: <ac72cfc80502190517509a7859@mail.gmail.com> (raw)
In-Reply-To: <4216700F.5010106@gmx.ch>

On Fri, 18 Feb 2005 23:45:35 +0100, Marco Trudel <mtrudel@gmx.ch> wrote:
> > OK, thanks. This could actually work to my benefit if I disable the
> > hcitool cache --
> 
> you're welcome...
> 
> > the device could take the time the user takes from
> > walking into range to being at the device for detecting,
> 
> I don't know what you mean with this...
>
>  > if you walk
> > out of range before that you were only passing the device. Good. Now I
> > only have to look at average office walking speeds to see how great I
> > want this radius to be :)
> 
> I don't understand that as well, but it sounds very interesting. Can you
> explain what you're doing? Just curious...

We have a kiosk where you have to select your name from a list before
you can do anything useful. You pick your name from a scrollist. What
I want to try is to install a bluetooth adapter on the device, allow
people to register their BT toys (phone, palm, whatever), and have the
device scan for BT devices in the vicinity. If it recognizes a
registered device, it could pre-select your name from the list, for
convenience.

If BT scan was super-fast, anyone standing at the device would be
bothered by anyone else passing by with a BT gadget active. With a 13
sec discovery time, and given the right range,  passers-by would be
out of range before actually being picked up. And if the range is just
wide enough, the scan would start at the edge of that range, and would
finish some seconds after you're standing at the device. It'd take
some tweaking, but since people usually slow their pace before
stopping, it could work.

 > by the way: do you know that a device does not have to answer to an
> inquiry? if a device is busy or just decides to not answer to an inquiry,
> that's ok (defined in bluetooth specification, my experience showed this as
> well)...

If we'll be using this (it's just a friday afternoon experiment at
this point) it's just an add-on for convenience. There will actually
only be a minority of our users that will be carrying active BT
gadgets.

Emiliano


-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-19 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18  9:24 [Bluez-users] hcitool scan times Emiliano Heyns
2005-02-18 18:49 ` Marco Trudel
2005-02-18 22:30   ` Emiliano Heyns
2005-02-18 22:45     ` Marco Trudel
2005-02-19 13:17       ` Emiliano Heyns [this message]
2005-02-21 23:07 ` 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=ac72cfc80502190517509a7859@mail.gmail.com \
    --to=emiliano.heyns@gmail.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 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.