• State Verified Answer
  • Replies 19 replies
  • Subscribers 63 subscribers
  • Views 6663 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 108835
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF UART app works on android, not on iOS 8.4

peterh

My ANT BLE application runs on a custom board with a nRF51422, SD 310 rev 2.0.0

I can use the nRF UART app on an android phone, but on an iPhone with iOS 8.4 I can't even see the device.

I can see the device in the list in the DFU Tool in the nRF Toolbox, but in nRF UART nothing.

Are there any connection/advertising/timeout/... parameters I should be aware off, in order to use iOS for UART?

Parents
  • 0

    The NUS_SERVICE_UUID_TYPE tells the stack of the index of the base UUID that we add to the database inside the stack using sd_ble_uuid_vs_add().

    sd_ble_uuid_vs_add() function returns the index of the UUID in uuid_type as the output. You can then use the value of uuid_type for the value of m_adv_uuids.

    We use NUS_SERVICE_UUID_TYPE (=0x02) just because in the example we only have one Vendor specific base UUID, and it will be at index = 0x02. But if you have more than one you should use the value returned when you call sd_ble_uuid_vs_add.

    Note that the advertising packet setting up is a separate process with the service and characteristic initialization process. They are 2 independent setting up.

    You can see what is advertised using Master Control panel application either on PC or on Android, or with iOS you can use 3rd party app called "LightBlue"

Reply
  • 0

    The NUS_SERVICE_UUID_TYPE tells the stack of the index of the base UUID that we add to the database inside the stack using sd_ble_uuid_vs_add().

    sd_ble_uuid_vs_add() function returns the index of the UUID in uuid_type as the output. You can then use the value of uuid_type for the value of m_adv_uuids.

    We use NUS_SERVICE_UUID_TYPE (=0x02) just because in the example we only have one Vendor specific base UUID, and it will be at index = 0x02. But if you have more than one you should use the value returned when you call sd_ble_uuid_vs_add.

    Note that the advertising packet setting up is a separate process with the service and characteristic initialization process. They are 2 independent setting up.

    You can see what is advertised using Master Control panel application either on PC or on Android, or with iOS you can use 3rd party app called "LightBlue"

Children
No Data
Related