Easy bluetooth wrapper in Qt
-
I want to build a mobile app (Android) in Qt that will talk to my Linux server. Both devices will be running Qt apps that I will develop. I want the two devices to talk using Bluetooth, so I've been looking for an easy way to do that. The Linux app will be the "server", and the mobile will be the "client" from a Bluetooth perspective.
From my first pass of reading about Bluetooth and Bluetooth LE, this looks pretty complicated. I'm hoping that Qt has made a nice simple wrapper that will make my life easier. But looking at the docs it still seems I need to learn a LOT about Bluetooth LE.
Is there an example Bluetooth client and server app available somewhere in the Qt archives? If not, can someone recommend a good source (website or book) that will help me along the learning curve?
-
Hi,
Did you already check the examples from the module ?
Depending on how you want to implement your system, the chat example might be fine otherwise, a combo of the heart rate server and game.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
Hi,
Did you already check the examples from the module ?
Depending on how you want to implement your system, the chat example might be fine otherwise, a combo of the heart rate server and game.
@SGaist I looked at the chat example and it might be close to what I want. The example does not mention anything about pairing...is that not required for BLE?
I'm trying to implement the equivalent of SPP, but I want to use BLE to ensure IOS support. Would the chat example provide the equivalent of a network socket connection between 2 devices?
I found a couple of articles which discuss implementing the equivalent of SPP over LE:
Article 1
Article 2But it's not clear how these would differ from the chat example? Why create a READ attribute and a WRITE attribute (as shown in the above to articles) to move data in either direction if the chat example creates a readable/writeable socket?
-
@SGaist I looked at the chat example and it might be close to what I want. The example does not mention anything about pairing...is that not required for BLE?
I'm trying to implement the equivalent of SPP, but I want to use BLE to ensure IOS support. Would the chat example provide the equivalent of a network socket connection between 2 devices?
I found a couple of articles which discuss implementing the equivalent of SPP over LE:
Article 1
Article 2But it's not clear how these would differ from the chat example? Why create a READ attribute and a WRITE attribute (as shown in the above to articles) to move data in either direction if the chat example creates a readable/writeable socket?
@ocgltd I have be coding Bluetooth app for months now. I do not code 24/7, however. if you like i could share my experiences, but prefer not here.
I would have to say this - majority of Bluetooth example code is based on very old C code which is based on "bluez" library. QT "Bluetooth module" is also based on "bluez" library. QT examples follow the "bluez" library ways of NOT documenting the code. It is frustrating to get the code working only to find / receive undocumented "bluez" errors...As far as "pairing " goes - yes I believe one of the QT example has no pairing code at al....
it is peculiar that QT can "scan" for remote devices WITHOUT pairing...I also found that :"socket" is used by accident and again not explained in QT code ...
I do not want to discourage you, but I call it as I see it.
PS
The there are few gems like this in documetati0nIf address is default constructed, services will be discovered on all contactable Bluetooth devices.
-
@SGaist I looked at the chat example and it might be close to what I want. The example does not mention anything about pairing...is that not required for BLE?
I'm trying to implement the equivalent of SPP, but I want to use BLE to ensure IOS support. Would the chat example provide the equivalent of a network socket connection between 2 devices?
I found a couple of articles which discuss implementing the equivalent of SPP over LE:
Article 1
Article 2But it's not clear how these would differ from the chat example? Why create a READ attribute and a WRITE attribute (as shown in the above to articles) to move data in either direction if the chat example creates a readable/writeable socket?
@ocgltd I do not have a deep knowledge of BLE but based on the articles you linked, it would be possible to implement the chat example with a custom service.
The chat example uses a Bluetooth standard protocol that is not available in Bluetooth LE.
