AnsweredAssumed Answered

KW41Z commissioner on mobile phone

Question asked by Evgeny Erlihman on Apr 6, 2017
Latest reply on Apr 20, 2017 by Mario Ignacio Castaneda Lopez

Hello,

 

I am evaluating the mesh capabilities of the KW41z chip, and was able to run the commissioner and node demo apps on two frdm41z board. I see that in the example there is a hardcoded meshRawCommissioningData_t structure on the node side that should be provided by the commissioner. Both documentation and the code has "Raw bytes interpreted internally as commissioning data" explanation for the contents of the meshRawCommissioningData_t, which is (in provided example): 

meshRawCommissioningData_t gRawCommData =
{
.bytes = { 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01,
0x00, 0x00, 0x00, 0x00,
BD_ADDR_ID, 0x01 }
};

 

My question is: is it possible to implement the commissioner on a mobile device and assume that everything other than the BD_ADDR_ID is constant? So the commissioner on the mobile device can just keep track of how many nodes we have in the mesh and assign/recycle BD_ADDR_ID's to new nodes?

 

Thanks,

Evgeny

Outcomes