This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Usage of Nordic Semiconductors proprietary UART service for commercial products

As stated in the topic. We use BLE to simulate UART. As for now, we have defined our own UUIDs but there would be more straight forward to use the well defined and used one by Nordic. However, is it okay to use these UUIDs for a commercial product?

The only difference is that we allow larger MTU sizes than 23 bytes (20 effective bytes). We support MTU sizes of 247.

Parents
  • Hi

    This is not something I would recommend. The idea of the 128-bit UUID is that everyone can easily generate their own, so as not to mix up your product with all the Nordic kits running the UART example.

    This is why there is no official UART service in BLE, since the Bluetooth SIG doesn't want a load of different devices doing wildly different things using the exact same profile.

    Could you elaborate a bit more on why you find it more straight forward to use the Nordic UUID?
    Generating your own UUID at least is very straight forward :)
    https://www.uuidgenerator.net/

    Best regards
    Torbjørn

  • Hello,

    The reason we want to do this is because we run a UART service, but i understand your point. Also, if we use that profile we could easily use different already existing tools during our development. For instance we have some connectivity issues with BLE (mostly with some Android devices) and it would be useful if we could download some other apps using the same service, if for instance that one works fine we could pinpoint that it is our implementation that is bad.

    I don't know if there are any advertisement strategy associated with the nordic UART service, but we have a different one.

    So your final recommendation is that we use our own UUID, then we will keep with that (we do that now).

Reply
  • Hello,

    The reason we want to do this is because we run a UART service, but i understand your point. Also, if we use that profile we could easily use different already existing tools during our development. For instance we have some connectivity issues with BLE (mostly with some Android devices) and it would be useful if we could download some other apps using the same service, if for instance that one works fine we could pinpoint that it is our implementation that is bad.

    I don't know if there are any advertisement strategy associated with the nordic UART service, but we have a different one.

    So your final recommendation is that we use our own UUID, then we will keep with that (we do that now).

Children
No Data
Related