Network commissioning in SamR21 using Bitcloud 3.2

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

 

We were having some problem with some end-devices, due to some reason they were losing network and then rejoining after sleep. So we were thinking to use NWK_JOIN_VIA_COMMISSIONING in end-devices.

 

When I tried to study the AVR2050_BitCloud_Developer_Guide(for Bitcloud 3.2) for same, it only explains how to use commissioning on ZLL but not with WSNDemo. Since in WSNDemo the we have only seen nwk join using ZDO_StartNetworkReq(), so I was not sure if I can use NWK_JOIN_VIA_COMMISSIONING in WSNDemo(Bitcloud 3.2) with SAMR21.

 

Can you please confirm if we can use commissioning with WSNDemo or not, and if possible can you give a link or an example explaining how I can achieve it? Or can we use the same method as in ZLL and implement in WSNDemo?

Last Edited: Fri. Oct 16, 2015 - 12:23 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

What exactly do you expect from it?

 

There is nothing special about ZLL application, you can do all the same things in WSNDemo. But why not figure out the real problem instead?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

While I was checking how ZLL joins network and I found this in bitcloud.

 

typedef struct _NWK_JoinControl_t
{
  NWK_JoinMethod_t method;

  bool secured;

  bool discoverNetworks;

  bool annce;

  bool clearNeighborTable;
} NWK_JoinControl_t;

 

static NWK_JoinControl_t joinControl =
{
  .method = NWK_JOIN_VIA_COMMISSIONING,
  .annce = true,
  .discoverNetworks = false,
  .secured = true,
  .clearNeighborTable = true
};

 

CS_WriteParameter(CS_JOIN_CONTROL_ID, &joinControl);

 

If I update join control before calling ZDO_StartNetworkReq(), will it work? Or Do I need to do some other changes?

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

It will work, but I personally have no idea what NWK_JOIN_VIA_COMMISSIONING is doing. It is some extension designed for ZLL, it may or may not work in your case. It may also depend on some specific stack settings. That's why I'm asking what do you expect from it?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

Last Edited: Wed. Aug 12, 2015 - 05:21 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

alexru wrote:

What exactly do you expect from it?

 

We just want that after the end-device has joined once, it won't need to search nwk ever again, even after restart.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

There are legitimate reason for ED to scan for a network. What if its parent forgot about it? ED will be essentially cut off from normal communication.

 

To save network parameters you can use PDS, but if device needs to rejoin, it must be able to.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the Info.

 

We'll be taking care parent not forgetting as ED will surly send data within time-out unless it's dead and having a threshold for nwk rejoin via commissioning to enable ED to rejoin after certain retries.