• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 16 subscribers
  • Views 1287 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2533: RemoTI 1.4.0 NPI Max Nwk Discovery Request results

RedRat
Prodigy 140 points
Part Number: CC2533
Other Parts Discussed in Thread: CC2620

Hi,

I need to revisit the issue I had in this thread:e2e.ti.com/.../508596

We need to be able to discovery more than 10 devices.

Is there anyway to recompile or hack the library to allow more than 10 devices?

Thanks,

Red.

  • 0
    TI__Expert 6315 points

    Hi,

    You can set number of pairing entries, up to 20, in precompiler options:

    RCN_CAP_PAIR_TABLE_SIZE=20

    Note that this will require more RAM, and may not be compatible with your application. You may also be required to use CC2533F96 which has most memory of the CC25xx devices.

    You should also consider RemoTI-2.0.1 and the CC2620. It is actually a perfect fit with 20KiB RAM, and even more flash. Not to mention much lower current consumption, and an autonomous Sensor Controller Engine.

  • 0 in reply to Torbjorn Sorby
    Prodigy 140 points
    Hi Torbjorn,

    Will increasing the pairing table size increase the max discovery results?

    We are using the CC2533F96, but we're not in a position to change to cc2620

    Thanks,
    Red
  • 0 in reply to RedRat
    TI__Expert 6315 points
    Hi Red,

    RemoTI-1.4.0 implements the ZRC2.0 profile. In this case the GDP layer handles the Discovery Requests. This is unlike ZRC which utilized the auto-discovery mode in the network layer. For ZRC2.0 there are no limitations to the number of nodes that can be discovered. They all are, and they are added to a list that is dynamically allocated, then ranked. If you increase the number of pairing entries, you may run into issues of memory allocation failure. This may limit, for example, the number of nodes you can effectively discover.
  • 0 in reply to Torbjorn Sorby
    Prodigy 140 points
    Hi Torbjorn,

    We've tried changing the line RCN_CAP_PAIR_TABLE_SIZE=16, nothing changed, RCN discovery still only returns 10 discovery events before ending with discovery cnf.

    But rereading your last post, are you saying reducing the pairing table (to say 6) will increase the number of nodes that can be discovered?

    Thanks,
    Red.