All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Barry Byford <31baz66@gmail.com>
Cc: Jason Anderssen <j@keyinitiative.com>,
	Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: Eddystone scanning - TLM packet
Date: Thu, 11 Aug 2016 14:29:00 +0300	[thread overview]
Message-ID: <CABBYNZJN0tq8E3x3PZSw5Ee0M4Y8ZugjMZmQLNaEqY0GT3negw@mail.gmail.com> (raw)
In-Reply-To: <CAAu3APY6aF9BckMfuH+2Ua7M=oHZuf7ghJVKT0t0_j0mSLyEBA@mail.gmail.com>

Hi All,

On Thu, Aug 11, 2016 at 11:01 AM, Barry Byford <31baz66@gmail.com> wrote:
> Hello Jason,
>
>
> On 11 August 2016 at 02:53, Jason Anderssen <j@keyinitiative.com> wrote:
>> Hi,
>>
>> I have successfully written code to scan for iBeacons using bluez, I was wondering if there is a link to some example or doc that explains how to detect the eddy stone different frames, for example, the main one I am after is the  Eddystone-TLM data which can be interleaved.
>> Any help or direction I can search would be fantastic.
>
> The different Eddystone frames are identified at the start of the
> service data. TLM is 0x02 as detailed in the spec at:
> https://github.com/google/eddystone/blob/master/protocol-specification.md
>
> You may also find this beacon cheat-sheet useful that was posted on Twitter:
> https://twitter.com/josryke/status/763006284052463617


Btw, I will be sending patches to add support for creating advertising
instance with bluetoothctl, so if all goes well it would be possible
to do this with bluetoothctl.

-- 
Luiz Augusto von Dentz

      reply	other threads:[~2016-08-11 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  1:53 Eddystone scanning - TLM packet Jason Anderssen
2016-08-11  8:01 ` Barry Byford
2016-08-11 11:29   ` Luiz Augusto von Dentz [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=CABBYNZJN0tq8E3x3PZSw5Ee0M4Y8ZugjMZmQLNaEqY0GT3negw@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=31baz66@gmail.com \
    --cc=j@keyinitiative.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 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.