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

ANT Burst Mode and Custom Byte Size Transmission

Hi everyone,

I was not able to find a full example in the SDK or online on initializing ANT to work with burst mode. Also, I was wondering if it's possible to setup ANT with custom data byte size.

I am currently using the background scanning example in the ANT folder to send and receive data.

Thank you.

Parents
  • The changes to for example the ant_broadcast are minimal. Just use sd_ant_burst_handler_request() instead of sd_ant_broadcast_message_tx(). The channel must also be birectional to use anything other than broadcast.

  • I believe we are talking about two different examples, I'm talking about ant_broadcast while you are talking about ant_background_scanning. I don't think a background scanning channel can receive a burst message, it is not mentioned anywhere in the ANT Channel Search app note, and I couldn't get it to work in a quick test here. If a background scanning channel could receive a burst message having multiple nodes with background scanning channels wouldn't work very well, the burst messages are acknowledged, and are synchronized off eachother, so having multiple nodes acknowledging would be a problem. If you send 24 bytes, you should receive 3 RX events with 8 bytes in each, not 1 RX event with 24 bytes. I don't know exactly what you use case is, but maybe shared channels can be used? They can be used with burst.

Reply
  • I believe we are talking about two different examples, I'm talking about ant_broadcast while you are talking about ant_background_scanning. I don't think a background scanning channel can receive a burst message, it is not mentioned anywhere in the ANT Channel Search app note, and I couldn't get it to work in a quick test here. If a background scanning channel could receive a burst message having multiple nodes with background scanning channels wouldn't work very well, the burst messages are acknowledged, and are synchronized off eachother, so having multiple nodes acknowledging would be a problem. If you send 24 bytes, you should receive 3 RX events with 8 bytes in each, not 1 RX event with 24 bytes. I don't know exactly what you use case is, but maybe shared channels can be used? They can be used with burst.

Children
No Data
Related