• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 52 subscribers
  • Views 496 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC26X2R1: BLE mesh nodes provisioning

Manikanth Chintoju
Intellectual 520 points

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSCONFIG

Hi TI,

  I have configured two nodes with Relay + Proxy configuration. Now using SimpleLink starter app I have provisioned one and later the other. But when I provisioned the second one  I was not able to see the previous one i.e., first one .Correct me if something is wrong with process, I have followed all the things mentioned in guides of TI and Simplelink Academy.

I want to have data transfer  from one node to other using publish subscribe paradigm, I see TI mesh app supports only Generic OnOff server so I opted other mesh apps in which they are supporting other features ,why 0xC000 every time, is there any significance for it.

  • 0
    TI__Guru** 101570 points

    Hi,

    Thank you for reaching out.

    May I kindly ask you to specify which SDK version you are using?

    I'll ask an expert to help.

    Best regards,

  • 0 in reply to Clément
    Intellectual 520 points

    simplelink_cc13x2_26x2_sdk_5_20_00_52,

    Please review it as soon as possible I'm stuck

  • 0 in reply to Clément
    Intellectual 520 points

    On my little research I see that it is the problem with UUIDs(might be) if so please tell me how to change the UUIDs for each device. In one of the documentation it  is shown to to manipulate or choose various UUIDs from Mesh_menu but that doesnot really working for me can please provide better idea of how to set UUIDs for each node differently so that I won't get this kind of issue of nodes missing on the mesh android app.

  • 0 in reply to Manikanth Chintoju
    TI__Mastermind 25810 points

    Hey Manikanth,

    I apologize for the trouble you are having. I was able to test the app out after doing the following on the embedded side:

    1. Navigate to MESH INIT Menu
    2. Navigate to MESH set UUID prior to provisioning
    3. Select  UUID for first node
    4. Select MeshInit unprovisioned beacon
    5. Repeat steps for second node, choosing a new UUID for the second node.

    I do see the nodes properly displaying as individual nodes in the app. Can you make sure to clear the Bluetooth device history on your phone by navigating to General settings? Additionally, navigate to the SimpleLink Starter app, and go to the mesh menu. Hit the settings icon and let's reset the network and remove the nodes from there as well.

    Manikanth Chintoju said:
    I want to have data transfer  from one node to other using publish subscribe paradigm, I see TI mesh app supports only Generic OnOff server so I opted other mesh apps in which they are supporting other features ,why 0xC000 every time, is there any significance for it.

    0xC000 is the first possible Group Address as defined in the Mesh specification, Section 3.4.2 Addresses. You can change this to any valid group address you'd like.

  • 0 in reply to Ammar N
    Intellectual 520 points

    I don't see any option showing MESH INIT Menu.

    Can you explicitly explain how to navigate to MESH INIT Menu.

  • +1 in reply to Manikanth Chintoju
    TI__Mastermind 25810 points

    Hey Manikanth,

    Thanks for sending that screenshot, it helped clear things up on my end. The option under mesh init to change UUID was not made available in the ERPC example code unfortunately. I have filed a ticket to add this in a future release. There are a few ways to work around this issue in the meantime:

    1. You can edit the python script directly and add in a prompt to configure the UUID. This option should allow you to change the UUID in real time (prior to provisioning of course). You can open up ble_mesh_erpc_app.py and modify line 333 to take in a custom defined UUID rather than the fixed UUID being used. I would leverage the embedded array inside simple_mesh_node.c::MeshApp_setUUID and write some code to randomly choose one of the options from the array.
    2. You can set the UUID on the embedded side, by modifying the SysConfig file and going to BLE Mesh>Provisioning Data Configuration>UUID. This option unfortunately requires you to compile a separate image for each node and to rebuild the project for each node.

    I hope this helps.

  • 0 in reply to Ammar N
    Intellectual 520 points

    I have tried second one for quite a number of times by taking some UUIDs from simple_mesh_node_menu.c(where some UUIDs are provided) but it seem like the UUID is not changing after compiling and flashing.

    Anyway I'll try with the first one meanwhile.

  • +1 in reply to Manikanth Chintoju
    TI__Mastermind 25810 points

    After thinking about this, #2 may not work since the Python script independently passes in the hardcoded fixed UUID, which will overwrite whatever is set in SysConfig.

    I will communicate this limitation in the ticket I mentioned earlier. We can add some custom code to work around this, but I think option #1 is the best path forward.

  • 0 in reply to Ammar N
    Intellectual 520 points

    I worked out in the you directed it went well. Thankyou.

    I want some further information such as how to use a relay node like its applications is to relay message. How can I send a message is there any packet format to do so in such way that the relay node passes the info to required destination node address .

    Any sample demo would be much helpful.

    Thankyou.

  • +1 in reply to Manikanth Chintoju
    TI__Mastermind 25810 points

    Hey Manikanth,

    Let's take this opportunity to continue the discussion in a new thread. Can you create a new thread with this question or any follow up?

    There isn't anything extra to do to to "enable" the relay node: The stack handles the message forwarding, so the application layer doesn't have to.