• State Suggested Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 68 subscribers
  • Views 2397 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 231912
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Configuration process in nrf_mesh APP

zhengrui

Hi, I'm provisioning mesh nodes using nrf_mesh APP. After I finished it and added device into mesh network, I have some questions in configuration process.

In nrf_mesh APP we can see the procedure while provisioning,and it shows these data app send and reveive  also we can find it in GATT provisioning and Proxy file.But I dno't know how the  node received data then it need to add/bind app key ,set pulication/subscribtion address to itself.I can't find the function calls to it.Could you please tell me where to realize it?

The another qestion is that when  I  config node it can reinitialize and reconnect to APP ,they send much data and I don't understand them because I can find it have any connection about appkey and pulication/subscribtion address .

Any help will be thanked advanced.

Best Regards!

ZhengRui.

  • 0 in reply to zhengrui

    As I pointed out in my previous answer, the configuration process is implemented and taken care of in config_server.c.

  • 0 in reply to Marjeris Romero

    Of course I know that all of thses functions is defined in the structure of access_opcode_handler_t opcode_handlers[]. But which I confused is that how to jump to the here after I  received configuration messages (I mean that which function is called or where the functions are initiallized).

    That's my problem.

    Thanks advance.

  • 0 in reply to zhengrui

    Hi zhengrui,

    I am sorry but I think there is a misunderstanding, because I am not sure what you are asking for.

    The configuration server model takes care of the configuration and you don't need to implement anything yourself in the application side. It should work automatically if the project is configured in the right way. The configuration is a standardize process and is taken care of by the stack. You shouldn't be modifying the stack.

    If your application is not working then something else must be wrong. If it's not working you need to give us more details about what exactly is not working so we can help you better.

    Have you tested the nRF mesh app together with the unmodified light switch example and confirm that it works as expected?

    Best regards,

    Marjeris

  • 0 in reply to Marjeris Romero

    Hell Marjeris,

    Oh,I forgot to tell the reason why I want to understand these things.

    I am now developing  my provisioner based on nrf_mesh APP to add  other functions not only provisioning nrf MESH.So I need to change the code in nrf_mesh_light example with my PCB board.

    Best wishes,

    Zhengrui.

  • 0 in reply to Marjeris Romero

    Hi Marjeris,

    There is anoher thing about model in composition data.

    We can get element count in capabiliy data but it isn't including model information. Provisioner get model information of node after received composition data. I have read mesh profile about composition data and provisioner get mode information just via composition data,is it right?

    In configuration process I just need to receive composition data ,add and bind app key,and set publication and subscrition address to element,is there are something wrong?

    Hope you can make me clearly.

    Thanks .

    Zhengrui

Related