STM32WB Nucleo vs Dongle Thread Examples Connectivity issues

[FSteg.1394]

Hi

I have a WB Nucleo and a WB dongle running the STM32WB Cube CLI thread example code for both. Both are flashed with the latest thread binaries.

If I run either two nucleo boards or two dongle boards together I can connect the two with the CLI example no problem.

But if I try to connect a nucleo board to a dongle board, each board creates its own thread network and becomes the leader of that network. Note that I am running the correct example for both and I have retried this setup on different channels.

Is there some configuration / hardware difference between the two that I am missing?

Thanks for any help.

[Remi QUINTIN · Accepted solution]

This is strange. I don't see any reason for a Nucleao board and a dongle not to be on the same network.

An engineer here did the test again and it worked perfectly.

Just use the CLI commands listed in the readme.txt file of the Thread_Cli_Cmd project.

 >panid 0x1234

  Done

 >channel 12

  Done

 >ifconfig up

  Done

 >thread start

  Done

 The same sequence was done on the Nucleo board and on the dongle.

The Nucleo board starts first. On request of the state command, we get:

  >state

  Leader

On the dongle, we get:

 >state

 child

[FSteg.1394]

I have retried with the setup you mentioned above and it now works!

In my original setup the dongle was plugged into a usb port next to 2 other 2.4ghz transceivers. (Logitech Unifying and Plantronics headset).

I suspect that the proximity to these two devices may have had an effect.

Thank you for your assistance and for going through the effort to recreate the setup.

Best regards,