• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 25 subscribers
  • Views 108 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290053
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sending different messages to different nRF52840 Dongles through BLE Mesh protocol from nRF52840 DK - 1) Not able to provision , un provisioned nodes through nRF Mesh app , when nRF52840 Dongle is flashed with Mesh Light-Switch example.

user115760

I have to send small packets of different data to all six Dongles from Development Kit(DK).

Till Now:

1) I have flashed different Mesh programs to DK using Segger Embedded Studio and provisioned using nRF Mesh app. It works perfectly fine.
2) I have flashed Mesh Chat example using nRF Connect Extension in VS Code also and provisioned using Mesh app. No problem.
3) I have used the DK to flash programs to Dongle by directly connecting SWD pins to DK from Dongle. I flashed the Basic Blinky example, BLE Blinky example and even the
Mesh example to Dongle for DK using the above method.
4) The blinky and the ble examples works perfectly fine in Dongle. After flashing Mesh light switch example , I can even see that Advertisement in nRF Mesh app which is coming
from the Dongle. Therefore, the Mesh programs are flashed perfectly in Dongle from DK.

Problems:

1) I am unable to provision the unprovisioned node shown in nRF Mesh app, which is coming from the Dongle, when Dongle is flashed with light switch Mesh program.
But I can make provision when the same program is flashed to DK.I don't know what I have done wrong as the same program works on DK , but not works on Dongle.

I have followed all the steps to flash programs to Dongle from the nRF Dongle programming tutorial.
1)Preprocessor changed to PCA10059
2)Linker macros are changed as shown
And I can flash program to Dongle perfectly fine. But I am not able to provision , when it advertise the Mesh programs.

Future needs:

1) Can you please send me steps to send data to different nodes through Mesh protocol. Because when I flash Mesh serial example to DK , I am unable to send data from
Mesh app through Vendor model. I already made Mesh connection between ESP32 chips and shared data between different nodes connected to Mesh from Mesh app using Vendor Server example. Now , I want to do the same
thing in Nordic chips with Dongles as Nordic chips are industrial standard one and I like them. Would you please help me to achieve that in Nordic chips?

My DK and Dongle wire connection :

Thankyou

  • +1

    Provision solved Ticket

    I have solved that unprovisioning problem from the above ticket.

    I have also flashed
    1) Mesh Light Switch example
    2) Mesh Light Dimming example
    to the nRF52840 Dongle. It worked perfectly fine and I can provision the nodes and control the inbuilt LED through the Mesh app.

    Now, I have some problems.
    1) How to send messages to Dongle from Mesh app?
    2) How to read that data received on Dongle in PC?
    3) I want to connect a 7 Segment display to the dongle, which can show the received messages(numbers only enough) from DK or nRF Mesh app. What are the steps to
    get that?
    4) Can we flash Mesh programs to the Dongle from DK using VS Code? is there any other way to do that?
    5) After flashing Mesh Serial example, I don't get any unprovisioned nodes from it. When building it also causes error as "UART pins are not defined". How can I solve this?

    Please answer as soon as possible.
    Thankyou.

    -Vicky

  • 0 in reply to user115760

    Hi,

    I am happy to hear that you solved the initial issue. Thank you for sharing the link to the thread that helped you solved it.

    Regarding your new list of problems, I can give some short answers to some of them here. For the rest, please create separate threads with descriptive names. They span several areas of SoC development, and should be handled individually. This also makes it easier for others to find answers to their similar questions in the future.

    1) From the nRF Mesh app you connect to the a node on the Mesh network. If a model on the Dongle is subscribed to a group address, you can go to the Groups tab in the app, select the group, and use the interface.

    2) One example of sending data to and from a PC is using serial such as in the Mesh chat sample.

    3) Please create separate ticket for this hardware related question. Please note that this is a very generic question, and we cannot provide a detailed list of steps for implementing this. We, or others in the community, may have some general tips and ideas, but you are expected to do the work yourself.

    4) While our DKs can be used as programmers, and the Dongle can be programmed that way if you have the correct cables and do the programming correctly, we really recommend using DKs as a basis for development. Especially if you are going to connect other components such as segmented displays. Please note that the DFU solution delivered with the Dongle is from the nRF5 SDK, so in order to use the Dongle with nRF Connect SDK you must program it using a programmer. Note also that most mesh examples are supported on the DKs, but not listed as supported by the Dongle.

    5) Those are two separate issues, not closely related to the original question. Please create a separate ticket for the build issue. Regarding "unprovisioned nodes", do you mean "unprovisioned beacon"? If you are unable to build, then there is nothing to program onto the board. What did you put onto the board if the project did not build? It is best to start with a ticket with the question regarding your build issue, with a complete description of what you do (which example, which SDK and version, and full build log with all errors.) Then, when you have solved that issue, and been able to program the board, you can ask next questions regarding not seeing the board broadcasting, and so on. One thing at a time.

    Regards,
    Terje

Related
Terms of service