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

Hi, Do the S140 version 6.1.1 SoftDevice does have full support for S=2(500 kbps) ?

if yes how can i choose between S=2 and S=8, where the change should take place, at the advertising init ?

Parents Reply
  • Hi.

    I was able to compile the projects in SDK 15.0, and debug them. But I did not get any errors, here is my output:

    Central:

    <info> app: BLE UART central example started.
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: Connecting to target 914819FB65EE
    <info> app: Connected to target
    <info> app: RSSI : -35 dBm
    <info> app: ATT MTU exchange completed.
    <info> app: Ble NUS max data length set to 0xF4(244)
    <info> app: Discovery complete.
    <info> app: Connected to device with Nordic UART Service.
    <info> app: RSSI : -25 dBm
    <info> app: RSSI : -36 dBm
    <info> app: RSSI : -26 dBm
    <info> app: Disconnected.
    <info> app: ADV. report
    <info> app: ADV. report
    <info> app: Connecting to target 914819FB65EE
    <info> app: Connected to target
    <info> app: RSSI : -24 dBm
    <info> app: ATT MTU exchange completed.
    <info> app: Ble NUS max data length set to 0xF4(244)
    <info> app: Discovery complete.
    <info> app: Connected to device with Nordic UART Service.
    

    Peripheral:

    <info> app: Debug logging for UART over RTT started.
    <info> app: Connected
    <info> app: Data len is set to 0xF4(244)
    <info> app: Debug logging for UART over RTT started.
    <info> app: Connected
    <info> app: Data len is set to 0xF4(244)
    

    Is the problem still NRF_ERROR_INVALID_PARAM? I'm a bit unsure what the problem is now.

    Best regards,

    Andreas

Children
Related