search

NordicSemiconductor / Android-nRF-Connect

Documentation and issue tracker for nRF Connect for Android.
1.34k stars 313 forks source link

Oximetry Characteristic data not being parsed to string. #134

Closed ubdussamad closed 2 years ago

ubdussamad commented 4 years ago

Describe the bug It's always the case that if a SIG defined characteristic is used by the server, the data that is sent to the nRF client is parsed to a human readable string format from the simple bytes format which is sent under the hood.

For example: If a server sends a hex array: 00-00-ff-00-ff The app will parse it as: Heart rate: 255 , Something: 255

But, in case of the PLX Continuous Measurement Characteristic this does not happens, it just displays the hex values it received from the server instead of parsing it.

Even, in case that I am not sending valid data format (SFLOAT), it should (atleast) still display: Incorrect Format but it just displays the values.

Is this intentional? or just a mishap? or I totally don't know what I am doing?

To Reproduce Steps to reproduce the behavior:

  1. Create a BLE Pulse Oximeter Service (UUID:1822) (I use ESP32 as a BLE server.)
  2. Create a PLX Continuous Measurement Characteristic (UUID:2A5F) characteristic.
  3. Connect to the server and read the characteristic data.
  4. Notice that there is NO parsing of the received value.

Expected behavior I expected the value received to be parsed and shown as a string. Like: Oxygen Concentration: 90% , Heart rate: 80BPM But instead, I just get a hex string displayed as the value.

Screenshots Click here for the screen shot. (Imgur link)

Versions (please complete the following information):

Additional context

philips77 commented 4 years ago

Hello, Unfortunately not all Bluetooth sig character have parsers implemented. I'll try to add one you this one in the next release.

ubdussamad commented 4 years ago

@philips77 Thanks you for your effort, can I in any way help with this? I would love to learn how you guys do these things.

philips77 commented 2 years ago

Hi, perhaps it's a bit late, but I've started working on PLX parsers. They should be available in the next release, planned for tomorrow (Friday release!).

philips77 commented 2 years ago

Fixed internally, will be released as 4.25.4 today.