Scan And Forward and Burst mode - configure/dynamic reconfiguring?

[Steph van Schalkwyk]

I'm using the Scan and Forward mode to relay sensor data. 

My requirement is for roughly 256 Bytes per message.

Question: Is it recommended to switch to a private channel once a device discovery is made or when a sensor datum changes?

In other words: Once the device cache contains device identities, should one cycle through those identities INDEPENDENT of the Scan and Forward communications? 

Scan and forward uses Channel 1 for Master, Channel 0 for Slave in discovery mode. Is it recommended to open another channel and pause the beacon on Channel 1 in order to transfer data to the slave(s)?

All help gratefully accepted.

[Petter Myhre]

The S&F uses the standard payload size of ANT, 8 bytes, and not all is used for data. With advanced burst this may be increased to 24 bytes, but that is max. 

Could you explain a bit more about what kind of functionality you want? That is not provided by S&F? It is a bit difficult to give recommendations when I don't know what you are trying to achieve here. 

[Steph van Schalkwyk]

Petter

Why is there a 24 byte limit on advanced burst? 

S

[Steph van Schalkwyk]

#define ADV_BURST_MODES_SIZE_24_BYTES ((uint8_t)0x03) ///< 24-bytes packet size for maximum 60kbps advanced burst transfer rate ?

[Petter Myhre]

Because the ANT spec defines it as the limit.