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]

Hello Petter.

I want to share ALL sensor data on the network with all nodes.

So probably 1024 bytes. I have used this before, just not on nRF.

Just a quick question: 

When a node is updating, is it necessary to switch to a "dedicated" channel to update the connected slave? Or can Channel 0 be used to send the updated sensor data?

Steph

[Petter Myhre]

In S&F you have two channels. One master channel (channel 1), and one background scanning channel (channel 0). The background scanning channel listens for messages from the other nodes, while the master channels repeats the messages. The master will alternate between the latest messages received from the devices in the device registry.

S&F is already using a dedicated channel to send the updated status, the master channel, channel 1.