Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatible list of 16-bit UUID 0x180D, 0x1859, 0xFDF3 when connecting with nRF Connect App from mobile phone #4

Open
dimitraNats opened this issue Jun 3, 2024 · 1 comment

Comments

@dimitraNats
Copy link

I downloaded the firmware zip directly on my phone and did DFU from Showcase App.
When I connect with nRF Connect App (of Nordic) which shows the Services and Characteristics, I am able to connect but the Service 0x1859 does not appear.
In the scanning page - before I connect - it shows the message "Incompatible list of 16-bit UUID 0x180D, 0x1859, 0xFDF3"

Any ideas why does this happen?

Also, I wanted to use this code with some modifications, in order to connect with movesense with another nRF52832 device. Is this possible? Can you please help me on how to do it?

@JonasPrimbs
Copy link
Owner

0x180D and 0x1859 are the custom 16-bit UUID GATT Services introduced by this firmware, as described in the README.
Since I did not find any sponsor yet who was willing to pay the fee for officially registering them at IEEE, the nRF Connect App has not implemented them and therefore shows that they are incompatible.
Therefore, the app will just display the HEX streams where you need a decoder for.

0xFDF3 seems to be the UUID of the registered Member Service of the Amersports company. Don't know how they are related to Movesense, but this might come from the Movesens firmware itself.

I'm not sure whether this firmware also works on other devices than the Movesense ECG sensors. I expect that it works on any devices that also the Movesense original firmware works on.
If you have tested the firmware on any other devices and it works, please write it down in the comments below, than I can create some kind of compatibility list to the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants