ANT+ pre-event timing

[Pepam]

Hi,

I have a simple question. How should I handle situation, when need to collect data and process them before the computed data are sended via ANT+ profile which runs on 4Hz update rate? I had an idea to use repeated timer, but it is not possible, because for example when I set timer interval to 240ms to have 10ms for data processing before they are sended, the gap between data processing is getting bigger in time. Acceptable would be if the data processing would be handled 10-20ms before ANT+ data send event every time. So please, any suggestion, what should I do?

thanks,

Pepam

[Kenneth]

You should check out Radio Notification in the Softdevice Specifications. This is a callback that the softdevice can provide to the application a fixed time before an Radio event (for instance ANT data) occurs. In the nRF5 SDK I believe you should find ble_radio_notification.c that can do this for you already, it will will work for ANT also.

Best regards,
Kenneth

[Pepam]

Hi,

thanks for reply. I have implemented as it is shown on attached code. It compiles succesfull,  but handler is not called before/after events at all. Please any suggestion? 

thanks,

Pepam

void ble_on_radio_active_evt(bool radio_active)
{
     NRF_LOG_INFO("running");
}

static void radio_notification_init(void)
{
    uint32_t err_code;

    err_code = ble_radio_notification_init(NRF_RADIO_PRIORITY_HIGH,
                                           NRF_RADIO_NOTIFICATION_DISTANCE_800US,
                                           ble_on_radio_active_evt);

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



/**@brief Function for application main entry, does not return.
 */
int main(void)
{

ret_code_t err_code;
    log_init();

    err_code = app_timer_init();
    twi_init();
    
    nrf_delay_ms(100);
    int rc = 0;
    rc = setup_hoge();
    nrf_delay_ms(100);
    
            //mpu_init();
    utils_setup();
    softdevice_setup();
    radio_notification_init();
    //ble_radio_notification_init(NRF_RADIO_PRIORITY_NORMAL, NRF_RADIO_NOTIFICATION_DISTANCE_5500US, handler(true));

        create_timers(); 
    //err_code = app_timer_start(data_send, APP_TIMER_TICKS(237), NULL);
    APP_ERROR_CHECK(err_code);
    simulator_setup();
    profile_setup();

    NRF_LOG_INFO("ANT+ Bicycle Speed and Cadence TX example started.");

    for (;;)
    {
        NRF_LOG_FLUSH();
        nrf_pwr_mgmt_run();
    }
}

[Pepam]

No, ble_radio_notification_init() runs without any problem.

[Kenneth]

I do not see how this should fail. It seems to be documented for both S212 and S332:
https://www.thisisant.com/resources/212-v20-sds
https://www.thisisant.com/resources/s332-v20-sds

Maybe NRF_LOG_INFO() for some reason doesn't work?

[Pepam]

NRF_LOG_INFO() is okay, I can see that handler doesnt run on inserted breakpoints anyway. I'll let you know  about any progress.

Thanks

[Pepam]

Hi Kenneth, 

I solved it with a help from this Tutorial. I have copied the code from tutorial and it worked. Don't know why, because both codes do exactly the same thing, but now it's working. 

Regards

[Pepam]

Hi Kenneth, I have other problem with radio notification. I have added timer measuring to SWI1_IRQ handler to see if the timing is correct. Radio notifications are configured to fire handler on inactive radio event, 2480us after radio has been disabled, but when I print time that have passed from previous event, it is a bit weird. It shows 11ms and then 235ms. These numbers occur periodically. It looks like something using the SWI1 handler also? Please see attached print screen with code.

Regards,

Pepam

[Kenneth]

The radio nofification signal may also be triggered by other activity such as timeslots due to flash operations or other radio activity (e.g. searching, BLE if you support that) etc. Can this be the case here?

Maybe it is better idea to sync on an event from ANT, e.g. start an app_timer on EVENT_TRANSFER_TX_COMPLETED event that timeout before the next ANT interval?

[Pepam]

Hi Kenneth, thanks for reply and idea. But please could you explain me or point to some threads where could I learn in which way should I work with EVENT_TRANSFER_TX_COMPLETED event? How should I sense this event? Is it possible to interconnect it via PPI and fire timer task start after this event? Or does it have some interrupt handler? My goal is to let cpu sleep as much as possible due to power consumption so hope that it is not required cpu to wait and be listening for this event. 

[Kenneth]

Typically in ant_evt_handler() you will get an EVENT_TX. Then you can start an single shot app_timer that for instance will timeout after 240ms (this might be a reasonable timeout if for instance the ANT interval is 250ms), then on the timeout handler you can run sensor sampling and write to new data to ANT using sd_ant_broadcast_message_tx().

Best regards,
Kenneth