1.1 Thank you

Thank you for your interest in the Beacon Line. The Beacon Line is a Bluetooth^® Low Energy infrastructure. With one gateway and up to 20 anchors in one Beacon Line you can implement many Bluetooth^® Low Energy ideas.

The Beacon Line is a battery-free, PoE-powered network solution for maintenance-free fixed installations based on wired radio nodes. You can use the Beacon Line either as a beacon network or as a beacon observation network to track moving beacons, or you can use both at the same time.

The simplicity of the Beacon Line network concept makes it easy for you to implement large-scale wireless ideas with a high degree of technical flexibility and modular expansion.

Illustration of a gateway	Anchor illustration

1.2 Hints

• All rights to this documentation and to the product(s) described therein are owned by taskit GmbH.
• All trademarks and registered trademarks mentioned herein are the property of their respective owners.
• Neither taskit GmbH nor the seller or distributor assumes any liability resulting from the use of this manual or any product described herein.
• The information in this document is subject to change without notice.
• This document has been prepared with care, however, errors cannot be excluded.
• This document may not be reproduced, edited, copied or distributed in whole or in part without written permission.
• FCC Compliance Statement: The Bluetooth^® Low Energy module used complies with Part 15 of the FCC Rules. FCC ID: TFB-1002

1.3 Warning

Warning

Warning

Warning notice

Do not connect the PoE output of the power supply to a non-PoE Ethernet port. Such an Ethernet port can be damaged or even set on fire. This power supply is intended for powering the taskit gateway. This is a simple PoE power supply. It does not protect unsuitable (non-PoE) Ethernet ports. The power supply may only be handled by qualified personal who are aware of the risks of improper use of electrical equipment. Any use other than that specified above will void the warranty. taskit GmbH accepts no responsibility for damage caused by improper use of the power supply. Disconnect the device from the power supply before maintenance work.

2.1 Beacon Line

Beacon Line is a Bluetooth^® Low Energy infrastructure and is based on a gateway with up to 20 anchors, which are serially connected and powered via a twisted pair cable (Cat 5).

2.2 Anchor

Each anchor contains a Bluetooth^® Low Energy module which is responsible for the wireless communication. The firmware has been implemented as a HCI (Host Controller Interface) controller and enables all Bluetooth^® Low Energy roles (Central, Observer and Broadcaster) and functionalities.

2.3 Gateway

The gateway enables the communication between the anchors and the Bline servers via TCP/IP. The gateway as TCP server gets its IP address dynamically from a DHCP server and can be reached via the IP address or host name (BLGD-MAC). The MAC address is mapped on the housing of the gateway (z.B. BLGD-8C8E7601441E). To communicate with the gateway a “.local” is appended to the hostname (MAC address), so in this example:

BLGD-8C8E7601441E.local

2.4 HCI

The HCI is a standardized Bluetooth^® interface for sending commands, receiving events and for sending and receiving data. According to meaning of HCI, this is used to bridge the host and controller devices.

The user has no contact with this level. Only the Beacon Line interfaces are accessible.

2.5 Bline-Server

The software was developed for Linux, Windows and macOS. The Bline server covers on one side the HCI host role and on the other side it provides a RESTful API for communication with the anchors and a TCP port for following the observer data.

This documentation explains the RESTful API and Observer data over TCP.

2.6 RESTful API

Representational State Transfer (REST) is a software architecture paradigm, that describes a unified interface between separate components in an HTTP-enabled client-server architecture.

2.7 OpenAPI

The OpenAPI Specification (formerly Swagger Specification) is a standard for describing REST-compliant application programming interfaces (API).

3.1 Beacon Line Starterkit

The simplicity of the Beacon Line network concept makes it easy for you to implement large wireless Bluetooth^® Low Energy ideas with a high degree of technical flexibility and modular expansion.

Included in delivery:

1. 1x Ethernet Gateway
2. 9x Anchor
3. 3x Bluetooth^® Low Energy Beacon
4. 1x POE (Power over Ethernet Power supply)
5. 10x Cat5-cable (5 meter length)

We connect the anchors to the gateway. The gateway is connected to the POE port of the POE power supply. We connect the LAN port to our switch (up to 1000 MBit/s).

The gateway gets its IP address dynamically from the DHCP server and can be reached via the IP address or host name (BLGD-MAC). The MAC address is mapped on the housing of the gateway (e.g. BLGD-8C8E7601441E). To communicate with the gateway a “.local” is appended to the hostname (MAC address), so in this example:

BLGD-8C8E7601441E.local

3.2 Bline server software

The Bline server software can be started under Linux, Windows and macOS.

The Bline server can connect to several Beacon Line gateways or anchors. This can be set in the Bline-Server.yaml file.

An example (Bline-Server.yaml):

Download: Bline-Server.yaml

server:
    jwt: false                              # JSON Web Token
    basepath: /bline/v1                     # HTTP Prefix
    www: vue/dist
    httpport: 8080                          # Port number for RESTful API
    scanport: 4000                          # Scan TCP port number
    errorport: 4001                         # Error Port number
    grpcport: 50051                         # gRPC Port number
    verbose: false                          # Verbose Flag
    monitor: true                           # Monitor Flag
    monitorinterval: 30                     # Monitoring Interval in seconds
lines:
    line1:                                  # Name of the gateway
        anchors: 1                          # Number of anchors connected to the gateway
        desciption: blgd-8c8e76011316       # The description of the line
        url: blgd-8c8e76011316:3001         # The IP address or hostname from the gateway
        enabled: true                       # Enabled Flag
        scan: true                          # Scan Flag
        broadcast: false                    # Broadcast Flag
    line2:
        anchors: 3
        desciption: blgd-8c8e76010477
        url: blgd-8c8e76010477:3001
        enabled: true
        scan: true
        broadcast: true

We start the Bline servers:

In Windows we start in the command prompt with the following command:

C:\beacon_line_2023\Bline-Server.230210\windows>Bline-Server.exe

Then the Bline server is started and initializes the Beacon Line:

#./Bline-Server
Bline-Server, V1.0 (24.09.2023), (C) taskit GmbH, 2023

Scan server listen to port 4000
Error server listen to port 4001

Web-Hosting: vue/dist
API Basepath: /bline/v1
⇨ http server started on [::]:8080

Connect Lines
    line1      with 1 anchors   Port: 48236 <-> blgd-8c8e76011316
    line2      with 3 anchors   Port: 48237 <-> blgd-8c8e76010477
Initialise Lines
    Waiting for Anchors
    Initialising Complete
Statup Lines     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16  17  18  19  20
    line1       S-
    line2       SB  SB  SB

3.3 Bline-Log Software

The Bline-Log software can be started under Linux, Windows and macOS.

The Bline log can log the scan data from the Bline server.

An example (Bline-Log.yaml):

Download: Bline-Log.yaml

cfgpath: .
datapath: .
logpath: log
scanport: 4000
errorport: 3001
verbose: false

In Windows we start in the command prompt with the following command:

C:\beacon_line_2023\Bline-Log.221211\windows>Bline-Log.exe

Log is started:

datapath: .
logpath: log
ScanLog ([::1]:3936) connected to tcp://localhost:4000

The observer data is redirected to csv files

For more explanation of the Observer data, see Chapter 5.

4.1.1 lines

Beacon Line Lines-settings.

Example:

#curl -X GET localhost:8080/bline/v1/lines
[
    {
        "anchors":1,
        "broadcast":false,
        "description":"",
        "enabled":true,
        "name":"line1",
        "scan":true,
        "url":"blgd-8c8e76011316:3001"
    },
    {
        "anchors":3,
        "broadcast":true,
        "description":"",
        "enabled":true,
        "name":"line2",
        "scan":true,
        "url":"blgd-8c8e76010477:3001"
    }
]

4.1.2 line/{Name}

Example:

#curl -X GET localhost:8080/bline/v1/line/line1
{
    "anchors":1,
    "broadcast":false,
    "description":"",
    "enabled":true,
    "name":"line1",
    "scan":true,
    "url":"blgd-8c8e76011316:3001"
}

Example:

#curl -X PUT localhost:8080/bline/v1/line/line3
-H 'Content-Type: application/json'
-d '{"anchors":20,"broadcast":true,"description":"","enabled":true,"name":"line3","scan":true,"url":"blgd-8c8e7601441e:3001"}'

Example:

#curl -X DELETE localhost:8080/bline/v1/line/line3

4.2.1 anchors

Example:

#curl -X GET localhost:8080/bline/v1/anchors
[
  {
    "Angle":0,
    "Description":"",
    "Fixed":false,
    "Location":"",
    "Url":"",
    "mac":"",
    "name":"line1-01"
  },
  {
    "Angle":0,
    "Description":"",
    "Fixed":false,
    "Location":"",
    "Url":"",
    "mac":"",
    "name":"line2-01"
  },
  {
    "Angle":0,
    "Description":"",
    "Fixed":false,
    "Location":"",
    "Url":"",
    "mac":"",
    "name":"line2-02"
  },
  {
    "Angle":0,
    "Description":"",
    "Fixed":false,
    "Location":"",
    "Url":"",
    "mac":"",
    "name":"line2-03"
  }
]

4.2.2 anchor/{AnchorID}

Example:

#curl localhost:8080/bline/v1/anchor/line1-01
{
  "Angle":0,
  "Description":"",
  "Fixed":false,
  "Location":"",
  "Url":"",
  "mac":"",
  "name":"line1-01"
}

4.2.3 anchor/{AnchorID}/broadcast?on={false/true}

Example:

#curl -X PUT localhost:8080/bline/v1/anchor/line1-01/broadcast?on=true
Anchor: line1-01 broadcasting is active!

4.2.3 anchor/{AnchorID}/scan?on={false/true}

Example:

#curl -X PUT localhost:8080/bline/v1/anchor/line1-01/scan?on=false
Anchor: line1-01 scanning is stopped!

4.2.4 anchor/{AnchorID}/connect/{MAC}

Note: To connect to a peripheral device, scanning of the anchor that wants to connect must be turned off.

Example:

#curl -X PUT localhost:8080/bline/v1/anchor/line1-01/connect/F6:49:C6:33:6D:B3
Anchor: line1-01 is connected to Node: F6:49:C6:33:6D:B3!

4.2.5 anchor/{AnchorID}/disconnect/{MAC}

Example:

#curl -X PUT localhost:8080/bline/v1/anchor/line1-01/disconnect/F6:49:C6:33:6D:B3
Anchor: line1-01 is disconnected from Node: F6:49:C6:33:6D:B3!

4.2.6 anchor/{AnchorID}/handle/{MAC}/{Handle}

Handle:

Finding out the structure of the Generic Attribute Profile (GATT) table of a Bluetooth^® Low Energy Peripheral device (Discovery) is an energy intensive process. To avoid it, we use the handle number on the GATT table. In this method, the Beacon Line Anchor (Central) can read and write the Characteristics values. This means that to read or write from a specific characteristic, the handle number must be known to the frontend program.

Example:

#curl localhost:8080/bline/v1/anchor/line1-01/handle/F6:49:C6:33:6D:B3/13
00

Example:

#curl -X PUT localhost:8080/bline/v1/anchor/line1-01/handle/F6:49:C6:33:6D:B3/13 -H 'Content-Type: application/json' -d '{"data":"0x01"}'
Anchor: line1-01 has written handle 13 on Node: F6:49:C6:33:6D:B3 with 01!

4.3.1 nodes

Beacon Line Nodes settings.

Example:

#curl localhost:8080/bline/v1/nodes
[{
	"AnchorList": [{
		"AnchorID": "line1-01",
		"RSSI": -21,
		"Timestamp": 1695799643418
	}, {
		"AnchorID": "line1-01",
		"RSSI": -24,
		"Timestamp": 1695799644268
	}, {
		"AnchorID": "line1-01",
		"RSSI": -24,
		"Timestamp": 1695799644477
	}, {
		"AnchorID": "line1-01",
		"RSSI": -24,
		"Timestamp": 1695799644477
	}, {
		"AnchorID": "line1-01",
		"RSSI": -24,
		"Timestamp": 1695799645318
	}],
	"Connectable": true,
	"Data": "0201060dff7b0140000000b36d33c649f6",
	"LastAnchor": "line1-01",
	"LastTime": 1695799645318,
	"mac": "f6:49:c6:33:6d:b3",
	"name": ""
}]

4.3.2 node/{MAC}

Example:

#curl localhost:8080/bline/v1/node/F6:49:C6:33:6D:B3
{
	"AnchorList": [{
		"AnchorID": "line1-01",
		"RSSI": -47,
		"Timestamp": 1695801593893
	}, {
		"AnchorID": "line1-01",
		"RSSI": -44,
		"Timestamp": 1695801593518
	}, {
		"AnchorID": "line1-01",
		"RSSI": -41,
		"Timestamp": 1695801594169
	}, {
		"AnchorID": "line2-01",
		"RSSI": -20,
		"Timestamp": 1695801593518
	}, {
		"AnchorID": "line2-02",
		"RSSI": -47,
		"Timestamp": 1695801594328
	}],
	"Connectable": true,
	"Data": "0201060dff7b0140000000b36d33c649f6",
	"LastAnchor": "line1-01",
	"LastTime": 1695801594328,
	"mac": "f6:49:c6:33:6d:b3",
	"name": ""
}

6.1 Hardware configuration

Hardware installation

Connect all parts carefully.

The Beacon Line Node (observer) is black on top and the lower side orange. The Beacon Line Wifi (gateway) is black on top and the lower side is black too. Power supply is a passive PoE connection (like Ubiquiti).

1. Connect the Beacon Line Nodes plug ´A´ goes into plug ´B´
2. Beacon Line Wifi has to be powered with the delivered power plug.

_Note: Please do not connect the last Node to any PC or other hardware. (Take a look at the warning on chapter 1.3 “warning”)

6.2 Software configuration

The Bline server can establish a connection with several Beacon Line Gateways or anchors. This can be set in the Bline-Server.yaml file.

An example (Bline-Server.yaml):

server:
    jwt: false                              # JSON Web Token
    basepath: /bline/v1                     # HTTP Prefix
    www: vue/dist
    httpport: 8080                          # Port Nummer für RESTful API
    scanport: 4000                          # Scan TCP Port Nummer
    errorport: 4001                         # Error Port Nummer
    grpcport: 50051                         # gRPC Port Nummer
    verbose: false                          # Verbose Flag
    monitor: true                           # Monitor Flag
    monitorinterval: 30                     # Monitoring Interval in Sekunden
lines:
    line1:                                  # Name des Gateways
        anchors: 1                          # Anzahl der Anker verbunden mit dem Gateway
        desciption: blgd-8c8e76011316       # Die Beschreibung der Line
        url: blgd-8c8e76011316:3001         # Die IP-Adresse oder Hostname vom Gateway
        enabled: true                       # Enabled Flag
        scan: true                          # Scan Flag
        broadcast: false                    # Broadcast Flag
    line2:
        anchors: 3
        desciption: blgd-8c8e76010477
        url: blgd-8c8e76010477:3001
        enabled: true
        scan: true
        broadcast: true

7.1 Overview

Technical data of the gateway - Overview

Interfaces

Technical data of the anchor - overview

Consumption of the main CPU and line communication

Technical data of the Bluetooth^® Low Energy module

Technical data - CPU module in the gateway

7.2 Commissions

  CE-Certification

Funk-Certification

Explanations

Passive PoETM (Power over Ethernet) is a simple way to supply power to the Beacon Line via an Ethernet cable. Passive PoETM uses free wires in the Ethernet cable (Plus 4;5 / GND 7;8) to transfer power to the device from one end to the other.

BEACON LINE

Web: www.beacon-line.com

Tel: +49(0)30 / 611295-46

Fax: +49(0)30 / 611295-10

Beacon Line, a brand of taskit GmbH

Groß-Berliner Damm 37, 12487 Berlin, Germany

Local court Berlin-Charlottenburg HRB 39014

Chief executive Dipl.-Ing. (FH) Thorsten Raulfs

7.3 Features

• Maximum Distance between nodes: 30m
• Minimum Distance between nodes: 13cm

The data transfer lines (Ethernet / RS232 / RS422) are on pin 1, 2, 3 and 6. The powersupply is positive on pin 4 and 5 and with the negative potential (usually GND) on pin 7 and 8.

It is not relevant on which end you give power to a Beacon Line (Gateway or last Node). The direction is neutral.

The nominal voltage range is from 12VDC…to….24VDC. The maximum power is 28 Volts. The minimum power is depending on your layout (number of Nodes and length of cables), but please never give less than 6VDC to a Beacon Line.

For example: One Gateway with two Nodes and 10meter cable each 12VDC is enough.

The electricity is not exceeding 400mA and usually is in a range of 200mA.

Small overvoltage will be taken by the internal mains supply circuit. High electric tension like you have sometimes in a vehicle, should buffered first or caused in damage of hardware, humans and environment.