From: Johan Hedberg <johan.hedberg@gmail.com>
To: yousif saeed <yufi_saeed@hotmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Listening for notifications/indications
Date: Tue, 2 Apr 2013 12:21:15 +0300 [thread overview]
Message-ID: <20130402092115.GA9284@x220> (raw)
In-Reply-To: <BAY175-W240DF9C80BE34DD37FB78DE5D20@phx.gbl>
Hi Youssif,
On Thu, Mar 28, 2013, yousif saeed wrote:
> I'm trying to communicate with a BLE module through a Linux machine
> (the module is running a heart rate profile). So far, I've been able
> to do everything I need except listening for Notifications and
> indications. I've searched through the web, forums, and even tried
> walking through the source code and still could not find the answer.
>
> I'm using kernel version 3.5 and bluez-5.3.
>
> Any help is greatly appreciated as this is part of my final year project.
>
> Thanks
> Youssif
>
> Succcessful commands used so far:
> hcitool lescan
> hcitool lecc
> gatttool -b <Mac Address> --primary
> gatttool -b <MAC Address> --characteristics
> gatttool -b <MAC Address> --char-read
> gatttool -b <MAC Address> --char-des
> gatttool -b <MAC Address> --interactive
>
> Failed commands:
> gatttool -b <MAC Address> --listen
You shouldn't need to use hcitool nor gatttool for the heartrate
profile. Instead, it should be enough to register a Heartrate Watcher
through the HeartrateManager D-Bus interface (see doc/heartrate-api.txt).
There's also a python script that will do all this for you in
test/test-heartrate. I've been able to use the script successfully with
my own LE heartrate device.
Johan
prev parent reply other threads:[~2013-04-02 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 16:47 Listening for notifications/indications yousif saeed
2013-04-02 9:21 ` Johan Hedberg [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=20130402092115.GA9284@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yufi_saeed@hotmail.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;
as well as URLs for NNTP newsgroup(s).