From: Marcel Holtmann <marcel@holtmann.org>
To: Santiago Carot-Nemesio <sancane@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Heart Rate Profile API
Date: Sun, 04 Mar 2012 20:57:49 -0800 [thread overview]
Message-ID: <1330923469.3392.154.camel@aeonflux> (raw)
In-Reply-To: <1330770910-7992-1-git-send-email-sancane@gmail.com>
Hi Santiago,
> doc/heartrate-api.txt | 72 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 doc/heartrate-api.txt
>
> diff --git a/doc/heartrate-api.txt b/doc/heartrate-api.txt
> new file mode 100644
> index 0000000..5dcaa52
> --- /dev/null
> +++ b/doc/heartrate-api.txt
> @@ -0,0 +1,72 @@
> +BlueZ D-Bus Heart Rate API description
> +****************************************
> +
> + Santiago Carot-Nemesio <sancane@gmail.com>
> +
> +Heart Rate Profile hierarchy
> +============================
> +
> +Service org.bluez
> +Interface org.bluez.HeartRate
> +Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX
> +
> +Methods dict GetProperties()
> +
> + Returns all properties for the interface. See the
> + Properties section for the available properties.
> +
> + RegisterWatcher(object agent)
> +
> + Registers a watcher to monitor heart rate measurements.
> +
> + Possible Errors: org.bluez.Error.InvalidArguments
> +
> + UnregisterWatcher(object agent)
> +
> + Unregisters a watcher.
> +
> + Possible Errors: org.bluez.Error.InvalidArguments
> + org.bluez.Error.NotFound
> +
> + Reset()
> +
> + Restart the accumulation of energy expended from zero.
> +
> + Possible Errors: org.bluez.Error.NotSupported
> +
> +Properties boolean ResetSupported [readonly]
> +
> + True if energy expended is supported.
> +
> +Heart Rate Watcher hierarchy
> +============================
> +Service unique name
> +Interface org.bluez.HeartRateWatcher
> +Object path freely definable
> +
> +Methods void MeasurementReceived(dict measure)
> +
> + This callback is called whenever a heart rate measurement
> + is received from the heart rate device. The unit for the
> + Value is expressed in beats per minute (bpm). The energy
> + field is optional and represents the accumulated energy
> + expended in kilo Joules since last time it was reset.
> + Furthermore, the device will be automatically reset when
> + it is needed.
> + The Contact field, if present, indicates that the device
> + supports contact sensor, besides it will be true if skin
> + contact is detected. The optional interval field is an
> + array containing RR-Interval values which represent the
> + time between two R-Wave detections, where the RR-Interval
> + Value 0 is older than the Value 1 and so on.
> +
> + Dict is defined as below:
> + {
> + "Value" : uint16,
> + "Energy" : uint16,
> + "Contact" : boolean,
> + "Location" : ("Other", "Chest", "Wrist","Finger",
> + "Hand", "Ear Lobe", "Foot"),
values are lower-case and either one word or connected via -. Also I
think it is earlobe and not ear lobe. Oxford dictionary please ;)
Regards
Marcel
next prev parent reply other threads:[~2012-03-05 4:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 10:35 [PATCH] Heart Rate Profile API Santiago Carot-Nemesio
2012-03-03 11:48 ` Anderson Lizardo
2012-03-05 1:51 ` Johan Hedberg
2012-03-05 4:57 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 8:08 Santiago Carot-Nemesio
2012-03-02 8:55 ` Santiago Carot
2012-03-02 23:57 ` Johan Hedberg
2012-03-03 0:05 ` Anderson Lizardo
2012-03-03 10:30 ` Santiago Carot
2012-02-20 9:54 Heart Rate Profile v.2 Santiago Carot-Nemesio
2012-02-20 9:54 ` [PATCH] Heart Rate Profile API Santiago Carot-Nemesio
2012-02-23 16:06 ` Anderson Lizardo
2012-02-24 8:00 ` Santiago Carot
2012-02-17 10:37 RFC Heart Rate API Santiago Carot-Nemesio
2012-02-17 10:37 ` [PATCH] Heart Rate Profile API Santiago Carot-Nemesio
2012-02-17 12:00 ` Anderson Lizardo
2012-02-20 9:54 ` Santiago Carot
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=1330923469.3392.154.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sancane@gmail.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