Burst transmission attempt return a 4016 error (channel closed)

RE: Burst transmission attempt return a 4016 error (channel closed)

OswaldoP — Wed, 29 Dec 2021 15:26:37 GMT

isn't 0x4022 TRANSFER_IN_PROGRESS?

Anyway, the problem was that I was trying to use the RTC0 and this caused conflicts with the SD and this was not flagged as a problem by segger, problem solved using RTC2. thank you.

RE: Burst transmission attempt return a 4016 error (channel closed)

Kenneth — Tue, 21 Dec 2021 08:04:05 GMT

You can find error code from ant_error.h, and 0x4020 is NRF_ANT_ERROR_TRANSFER_IN_PROGRESS. In other words there is already a burst transfer in progress and you need to try again later calling sd_ant_burst_handler_request().

Kenneth

RE: Burst transmission attempt return a 4016 error (channel closed)

OswaldoP — Mon, 20 Dec 2021 18:01:21 GMT

I will open a thread in the forum thank you,

if I add a delay of at least 10ms right after the channel setup, the error is no more 4016, but i have a 4020 which suggests an error in the sequence of burst transmission, is it ok to put a delay after the channel opening?

since I'm trying to transmit a payload of 136B at every interrupt ( every 64 samples an interrupt is triggered, having 512sps gives an interrupt every 125ms), is the transmission speed enough? I mean, a single burst is 1088b, let's say we have 100ms of timeslot, do 52832 transmit 1088b in a burst during this time?

I moved the "transmission request" to the main function anyway, thank you for your suggestion.

RE: Burst transmission attempt return a 4016 error (channel closed)

Kenneth — Mon, 20 Dec 2021 11:59:54 GMT

You may direct this question to https://www.thisisant.com/forum/ for ANT support, but it looks like the api return an NRF_ANT_ERROR_CHANNEL_NOT_OPENED.

You are stating that the channel is opened, but it could be a race condition, what happens if you ignore the error the first time, do you experience it all the time?

All that said, I am not sure I like the implementation of calling the burst directly from the ADC callback, I suggest you buffer up messages in the ADC callback (e.g. have two buffers of 1024bytes), and when one buffer is filled up, then you execute the sd_ant_burst_handler_request() from the main() context.

Kenneth