BLE Interface¶
Some devices are equipped with a Bluetooth Low Energy (BLE) interface.
Note
The firmware does not support this function yet. It will be added in a future firmware update.
The device supports the following mode of operation:
- Gateway mode: The device operates as a BLE peripheral and provides access to CAN data to any connecting BLE central device such as a PC, smartphone, or tablet.
Note
BLE prioritizes low power consumption over data throughput and does not guarantee data delivery. BLE is not suitable for high-bandwidth CAN traffic. For high CAN bus loads, use a Wi-Fi-based CAN bridge.
Terminology¶
This table defines terminology used in this documentation.
| Term | Description |
|---|---|
| BLE | Bluetooth Low Energy. A wireless technology optimized for short range and low power consumption. |
| central | A BLE role that initiates connections (for example, a smartphone or PC). Also referred to as client in configuration objects. |
| peripheral | A BLE role that advertises services and accepts connections (for example, a Proemion device). Also referred to as server in configuration objects. |
| service | A collection of BLE characteristics exposed by a peripheral. |
| characteristic | A data endpoint within a BLE service used to read, write, or notify data. |
| Gateway mode | Operating mode in which the device acts as a BLE peripheral and provides CAN data to any connecting BLE central device such as a PC, smartphone, or tablet. |
BLE peripheral¶
When operating as a BLE peripheral, the device advertises a service that exposes data endpoints, referred to as characteristics. A BLE central device scans and connects to the peripheral to exchange the data.
Proemion bridge service¶
The Proemion bridge service is the BLE service used to exchange CAN data. A BLE central device scans for this service, connects to it, and uses it for data transfer.
The service UUID and the characteristic UUIDs are configurable. By default, they use the same values as the fixed bridge service on other Proemion devices.
| Characteristic | BLE properties | Description |
|---|---|---|
| Read | Read, Notify | Sends data from the peripheral to the central device. |
| Write | Write | Receives data sent from the central device to the peripheral. |
Note
All data is transferred using the Proemion Byte Command Protocol. For more information, see Byte Command Manual.
Pairing and access control¶
Access to the BLE peripheral is protected by pairing instead of a whitelist. By default, pairing requires bonding and a fixed passcode, which the device displays during the pairing process.
| Object | Name | Default | Notes |
|---|---|---|---|
0x30FF:0x06 |
Authentication Request | 0 |
Secure: pairing with bonding, attributes require authentication |
0x30FF:0x08 |
BLE Security Passcode | 999999 |
Fixed passcode used during pairing; write-only |
0x30FF:0x0D |
Delete all bonded devices | - | Removes all paired devices; they must pair again |
Configure device as a BLE peripheral¶
To operate the device as a BLE peripheral, configure the CANopen objects listed below.
| Object | Name | Value | Notes |
|---|---|---|---|
0x3008:0x09 |
BLE Enable | 1 |
Enabled |
0x30FF:0x03 |
Device Name | (unique name) | Set a unique name for the peripheral |