RE: Radio Notification Problem

Vidar Berg — Mon, 29 Jun 2020 12:45:47 GMT

Hello,

I'm not sure why the notification type option was removed from the library. I assume it must have been done to simplify the API a bit. However, the SD function to enable radio notifications should pretty straight forward to use directly without the library, so I would suggest doing that instead.

Eg., something like this:

void RADIO_NOTIFICATION_IRQHandler()
{ 
    // radio notification ISR
}

void radio_notification_enable()
{
    uint32_t  err_code;

    err_code = sd_nvic_ClearPendingIRQ(RADIO_NOTIFICATION_IRQn);
    APP_ERROR_CHECK(err_code);
    
    /* Interrupt priority is set to 6 by the Softdevice */
    err_code = sd_nvic_EnableIRQ(RADIO_NOTIFICATION_IRQn);
    APP_ERROR_CHECK(err_code);

    err_code = sd_radio_notification_cfg_set(NRF_RADIO_NOTIFICATION_TYPE_INT_ON_INACTIVE, 
                                             NRF_RADIO_NOTIFICATION_DISTANCE_NONE);
    APP_ERROR_CHECK(err_code);
}

[quote userid="81150" url="~/f/nordic-q-a/63082/radio-notification-problem"]That 10 ms corresponds to the 10 ms in the scan .interval. If I change the .interval to 20 ms is the interrupt changes to 20 ms.[/quote]

I suspect the reason you are only getting radio notifications for the scan events and not the advertisement events may be that there is too little time between the events. Here is an excerpt from the Softdevice specification stating that notifications may be dropped if the distance is to short (link):

When there is sufficient time between Radio Events (t_gap > t_ndist), both the ACTIVE and nACTIVE notification signals will be present at each Radio Event. Two radio events with ACTIVE and nACTIVE signals illustrates an example of this scenario with two Radio Events.

Only enabling the nACTIVE signal or reducing tprep should increase the chance of getting a notification signal for every radio event.