• State Verified Answer
  • Replies 19 replies
  • Subscribers 89 subscribers
  • Views 9199 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

    Maximum size of an advertising packet is 31 bytes. You have to count all the over head such as the flags, length, etc. My suggestion is to reduce the device name. Let's say, make it 1 byte. Just to test.

    You can have 31 more bytes using the scan response packet. It's the second packet that the advertiser sends when receive a scan request from a scanner. You can find the use of "scanrsp" when calling ble_advertising_init() in advertising_init() in the ble_app_uart example.

    You can post your code here, so I can have a look.

Reply
  • 0

    Maximum size of an advertising packet is 31 bytes. You have to count all the over head such as the flags, length, etc. My suggestion is to reduce the device name. Let's say, make it 1 byte. Just to test.

    You can have 31 more bytes using the scan response packet. It's the second packet that the advertiser sends when receive a scan request from a scanner. You can find the use of "scanrsp" when calling ble_advertising_init() in advertising_init() in the ble_app_uart example.

    You can post your code here, so I can have a look.

Children
No Data
Related
Terms of service