ANT Broadcast Message through previously set up channel

[angel]

Hi Nordic,

I have a star network with 3 nodes and 2 channels. I go through the whole pairing process and start sending data without problem. Now I want to, from the master, use one of these two channels to broadcast data to all nearby ANT devices, irrespective of their channel ID. I try to do this but when I try to use sd_ant_broadcast_message_tx in one of the channels, I get this error code: 401F. What does it mean? Do I have to use a new channel just to broadcast this information? It is important to say that this broadcasting will be done very very unlikely, the normal operation of the channels is to send and receive ack messages.

Thanks Nordic!

[angel]

Ok, let me try to clarify better what I am trying to do:

1. Set slave as wildcarded and search for master.

2. In master, start communication with random channel ID. Store this number in master's flash.

3. Slave searches for master, and once they communicate, slave stores its channel ID in slave's flash. Now both nodes have same channel ID in flash.

4. What if this master now breaks and I need a different master, with a different, random channel ID? My idea was to create a special message such that, once received in the slave, it deletes the previous channel ID information in the slave's flash and sets the current channel ID to wildcard, so it can start searching for a new channel ID.

The problem is, how do I send that message?

Is it a bit more clear now?

Thanks,

Angel.

[Petter Myhre]

Ok. Let's say you are using channel 0 in the slave to connect to the first master.

Then you can do something like (I'm not sure what your use case is):

1. If the first master is unresponsive for a certain amount of time, reconfigure channel 0 to search for a new master.
2. If the first master is unresponsive for a certain amount of time, configure channel 1 to search for a new master.
3. Configure channel 1 to always search for a new master.

[angel]

Hi Petter,

Ok, that can also be done, and would probably be the easiest solution. But what if the first master just runs out of battery, for example? You will time out and look for another one.... What would make the user to do the pairing each time they run of battery... It is a feasible solution though, thanks for the help.

What I will do, first I will change the role of master and slave, will change from net slave->master<-slave to master<-slave->master. As I have physical access to this slave now, I can reset pairing through a combination of buttons, for example :) If this doesn't work, I will implement your solution.

Thanks!!