Repository navigation
Sendig different BLE characteristics #24
Description
Hello I'm currently trying using the BLE Sensor APP by STM and I would like to work around the BLE 20 bytes cap when sending information. Basically I want to know if the APP's structure given in this repository supports the receivement of two differente BLE packages, as in an example: first my tile sends information of a given set of sensors and then, after the APP has received it the tile sends out information related to a different set of sensors
What's happening now is that I'm alternating bewtween sending package 1 with a set of sensors and package 2 with completely different sensors but what's happening is that package1's info is getting on where I showcase package 2 sensor's info and vice versa. Could the problem be in sending these 2 information packets with the same UUID or is it something that the frontend is doing wrong? And so, how can I fix it?
Activity
ANPuroOsso commentedon Jan 28, 2020
Would enabling notifications of certain sensors when I'm about to receive the package corresponding to them while desabling notifications of the other package's sensors and vice versa work?
GiovanniVisentiniST commentedon Jan 28, 2020
the extractData method is called from a concurrent queue, so the is no guarantee about the order that it is executed, probably that is your problem.
you can use 2 different uuid and enable the notification on both.
ANPuroOsso commentedon Jan 28, 2020
@GiovanniVisentini Oh I see, I'm just a little confused about the "UUID", do you mean when the tile is sending characteristics there's a UUID representing the BLE package and I should make 2 differents UUID's for those messages(one for each package)? If so, how exactly can I generate a new UUID to attach to this new BLE package?
GiovanniVisentiniST commentedon Jan 28, 2020
you can see the UUID as an address where read the data, you define 2 data location one for a set of sensors and the other for another set of sensors.
then you enable the notification on this 2 Feature and you will receive the notification on different classes.
ANPuroOsso commentedon Jan 28, 2020
@GiovanniVisentini I see, so it's something primarily defined by the backend? And by that I mean the STM tile code responsible for sending the data?
GiovanniVisentiniST commentedon Jan 28, 2020
the STM Tile needs to export the UUID that you want to read, otherwise from the mobile you can read/receive notification..
ANPuroOsso commentedon Jan 28, 2020
I got that, so what you're saying is that when the STM Tile builds the package with the sensor's measurement in it's backend code to be sent to the app, also in that code it needs to be defined an UUID corresponding to that package?
ANPuroOsso commentedon Jan 28, 2020
where in APP'S code does can I find the UUID exported by the tile?
GiovanniVisentiniST commentedon Jan 28, 2020
BlueSTSDK_Android/BlueSTSDK/src/main/java/com/st/BlueSTSDK/Utils/BLENodeDefines.java
Line 239 in 1f55866
but all the UUID listed there are already manage by the sdk..
and by the way the data exported depends to the firmware that you are running..
ANPuroOsso commentedon Jan 28, 2020
So what should I implement on the app's code to handle a different UUID?
GiovanniVisentiniST commentedon Jan 28, 2020
see here:
#23
ANPuroOsso commentedon Jan 28, 2020
Sorry I still don't get it, the other thread I made was about adding external features not sending 2 different BLE packages
ANPuroOsso commentedon Jan 28, 2020
Does the tile have to send the UUID: "7e7419d5-cad5-4f01-91e2-2f3e5cd0a72c" when sending FeatureMyCustomClass data, is that what you're saying?
GiovanniVisentiniST commentedon Jan 28, 2020
the tile has to export the characteristics with that UUID..
you can use this sdk without knowing about uuid, and how the data are arriving to the mobile..
but if you want to do something custom it is better if understand how the BLE works.
otherwise we both lost time..