sd_ant_burst_handler_request() limit

Question

Hello, 
 according to the documenation, the function sd_ant_burst_handler_request() can return with the error code NRF_ANT_ERROR_MESSAGE_SIZE_EXCEEDS_LIMIT. When will the function return with this code, how should a caller cope with this response and is there a way to avoid this return code at all (for example limiting each chunk to a static compile time limit)? 
 kind regards, 
 Torsten

Petter Myhre · Accepted Answer

I haven't tested this myself, but could this question be helpful? 
 I know you get NRF_ANT_ERROR_MESSAGE_SIZE_EXCEEDS_LIMIT from sd_ant_broadcast_message_tx() if you try to use a message size larger than 8, but with sd_ant_burst_handler_request() I get NRF_ANT_ERROR_INVALID_PARAMETER_PROVIDED . I have contacted ANT and will update when I hear from them. 
 Edit 01.12.2014: NRF_ANT_ERROR_MESSAGE_SIZE_EXCEEDS_LIMIT should never be returned by sd_ant_burst_handler_request() . 
 The size provided must be a multiple of 8, or you will get NRF_ANT_ERROR_INVALID_PARAMETER_PROVIDED . You can actually provide the complete 1024 bytes array to sd_ant_burst_handler_request() and ANT will split the data and send it. With normal burst this will be in packets with a payload of 8 bytes. The payload can be increased by using the advanced burst, where the packets can have a payload up to 24 bytes. Please see the question linked to above.

sd_ant_burst_handler_request() limit

Top Replies