From: Dave West <westdwestd@yahoo.co.uk>
To: bluez-devel@lists.sourceforge.net
Cc: roger.kermode@smartinternet.com.au
Subject: [Bluez-devel] bluetooth hardware that is discoverable by default?
Date: Fri, 21 Jan 2005 02:07:42 +0000 (GMT) [thread overview]
Message-ID: <20050121020742.55149.qmail@web25003.mail.ukl.yahoo.com> (raw)
Hi there,
I have very simple requirements for a bluetooth
'beacon' that is discoverable, but nothing else (ie.
it responds to discovery requests, but you don't need
to connect to it or anything). At the moment I am
using a D-Link USB dongle where the USB powerlines are
soldered to an external power supply. This supplies
power to the beacon, but it still needs to connect to
a linux/bluez equipped laptop (with USB power
disconnected as it draws its power externally) to
bring up the device and make it discoverable.
Immediately disconnecting the bluez laptop you then
have a cheap standalone beacon as long as the power
remains.
I'm wondering is there any way to have a beacon like
this where you don't have to connect it to a laptop
after its been powered up to make it discoverable? My
searches on google and looking at the bluez code make
me think that normally a HCISETSCAN ioctl is sent to
the device with SCAN_INQUIRY|SCAN_PAGE option to make
it discoverable. My question is are there any dongles
out there that become discoverable immediately when
they are powered without having to send them a HCI
command? One of you who have written drivers for
these things might know....
Or if there aren't, can anyone suggest another way I
might go about making or designing a cheap self
powered bluetooth beacon that is discoverable on
powerup? I may want to manufacture these beacons in
some quantity later.
Thanks,
David
___________________________________________________________
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-01-21 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 2:07 Dave West [this message]
2005-01-21 9:36 ` [Bluez-devel] bluetooth hardware that is discoverable by default? Peter Wippich
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=20050121020742.55149.qmail@web25003.mail.ukl.yahoo.com \
--to=westdwestd@yahoo.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=roger.kermode@smartinternet.com.au \
/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