public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: John Whitmore <arigead@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Missing manual? - GAP Central connecting to multiple peripherals.
Date: Thu, 4 Jul 2019 22:26:45 +0100	[thread overview]
Message-ID: <20190704212644.GA13491@n14xzu> (raw)

BLE at the wrong end of a learning curve and trying to piece things together.

Perhaps I could just give a rough outline of the project. I want a Linux
device to listen for advertisements from a particular BLE sensor and connect
to those sensors, as and when they appear. Once connected, the Linux device
can send commands to the sensor, to turn on/off an LED or request sensor data
from each of the connected sensors.

The Linux kernel is 4.15 is an Ubuntu 16.04 based system.

I was looking at the latest bluez-5.50 doc directory but didn't see a file for
gap.txt, but adapter-api.txt looks like the API I'm looking for.

I'm trying to do this from Python, so currently thinking of using DBus
interface, another learning curve to address.

So after all that a specific bluex questions. I'm missing things, and possibly
incorrectly assuming that I need a certain kernel specified for bluez5.50, but
can't see any mention of versions of bluez relating to versions of kernel.

Secondly bluez-5.50 appears to be building an applicaiton, so I assume that
application has to be running to interface to Linux Kernel bluetooth stack and
handle the DBus API. So bluez should be a system service just started on
powerup?

Thanks for any help, I get the impression that this list is predominately for
guts of the Linux Kernel's bluetooth stack, but user side list is hard to
find.

Thanks again

John

             reply	other threads:[~2019-07-04 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 21:26 John Whitmore [this message]
2019-07-05  7:29 ` Missing manual? - GAP Central connecting to multiple peripherals Barry Byford
2019-07-07 11:27   ` John Whitmore

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=20190704212644.GA13491@n14xzu \
    --to=arigead@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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