![]() ![]() D-Bus is an Inter-process Communication (IPC) method that allows us to make Remote Procedure Calls (RPC) between different processes. We’re going to build our peripheral directly using BlueZ’s D-Bus API. D-Bus is essentially a message bus that allows different processes running on a Linux system to talk to each other. What is D-Bus?īefore we get into BlueZ, we’ll want to have a cursory understanding of d-bus and how we use it to talk to BlueZ. To communicate with BlueZ, we’ll be using something called D-Bus. It handles both Bluetooth BR/EDR as well as BLE. What is BlueZ?īlueZ is the Bluetooth stack for Linux. However, if you’re looking for more in-depth insights into directly working with BlueZ, or for those who don’t want to use a third party library to manage their BLE connections, this guide is for you. They’re a great wrapper around Bluetooth things. ![]() While the official forks of Noble/bleno seem to have been abandoned, they have been picked up by abandonware. Julian, one of our Mobile Software Engineers, showed us how to use bleno to quickly spin up a BLE peripheral. If you don’t know what those words mean, you should first check out Adafruit’s article on BLE. This is not intended to be an introduction on BLE and assumes that the reader has some idea of what services, characteristics, and advertising are. To help remedy this, I underwent the task of creating a BLE peripheral running a GATT server on a Raspberry Pi 3+. While I’m fairly well-versed in working with BLE on an embedded device, I have so far had little experience with using BLE at a higher level. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |