regarding pairing

Hi Srinivas,

For autonomous operated slaves:

The device ID of the master has to be stored in the slave's non-volatile flash memory. This could be done in the PPW Configurator in the slave's "Radio" panel. For "Pairing trigger" select "None (fixed network ID)". Then enter the 32 bit device ID of the master in the field Default network ID (hex). The device ID of a master can be seen in the "Flash programming" when connecting a CC debugger to the master. If this should be done in production so that the product is prepaired out-of-the box there are EHIF commands for reading out device ID of master and store this in the slave's flash.

For host controlled slaves:

If the slave is not connected to any network you can continously scan for masters and join any network you want. Scanning and joining is done by the host (e.g. an external MCU) controlling the PPW slave.

-Kristoffer

Kristoffer S said:

The device ID of the master has to be stored in the slave's non-volatile flash memory. This could be done in the PPW Configurator in the slave's "Radio" panel. For "Pairing trigger" select "None (fixed network ID)". Then enter the 32 bit device ID of the master in the field Default network ID (hex). The device ID of a master can be seen in the "Flash programming"

Is there any current support (or planned feature) to support a list of master device ID's (like devid1,devid2,devid3) ?   i have an application that uses a single hard-paired master and slave pair, but would like to be able to swap out the master (in case of failure, dead battery, etc.) without changing the slave end too.  Thx!