• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 481 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.

SimpliciTi Joining/Linking request problem

Nipam Bhavsar
Intellectual 620 points
Other Parts Discussed in Thread: SIMPLICITI, CC430F6137, CC430F5137

Hello,

I am working on RTLS based project. For that purpose I am using SimpliciTi Stack and EXP-CC430RF4 evolution kits. I configure CC430F5137(Satellite Board) as an End device and CC430F6137(Base Board) as AP as Data Hub.

EDs : Asset Tag , 4 Base boards : Slave Tags , 1 Base board : Master Tag

I have attached top level diagram.


What I want to do : There are 10 Asset Tags, 4 Slave Tags and 1 Master Tag. Each Asset Tag will make a link to 4 Slave Tags and after linking, Asset Tag will transmit information periodically(5 sec) to Slave Tags. These Slave Tags will receive these information from Asset Tag and transmit those to Master Tag that is also configured as AP as Data Hub.

I have done some changes in AP as Data Hub code making for receive as well as transmit information.

Problem : First,I start up all Slave Tags and then start one Asset Tag. All Slave Tags are in "listen" mode and I see "added End device" scrolling text on LCD. It works well.

Now I am going to start 2nd Asset Tag. In this case,some time Asset Tag is added only by 1 Slave Tag, some time only by 2 Slave Tags, some time only by 3 Slave Tags. That means Asset Tag can't be joined or linked with all Slave Tags. Same way I found same result for 3rd Asset Tag, 4th Asset Tag and so on.

Is my configuration right or not?

Is this problem because Slave Tags(AP as Data Hub) are in transmit mode when Asset Tag is sending Join or Link request? 

Please provide me the solution for this.

Any help is appreciated.

Thanks,

Nipam

  • 0
    TI__Guru 56650 points

    Nipam,

    just to make sure that i understand the problem correctly: so all Slave Tags and Asset Tags are basically ED (End Device), but only Slave Tags can communicate with Master Tag (AP) in star-network like topology,while the Asset Tags can only communicate with the Slave Tages in peer-to-peer like topology. Is this correct?

    I think you can take advantage of the Token concept (http://processors.wiki.ti.com/index.php/SimpliciTI_FAQ#What_is_the_Token_used_for.3F) as follows:

    All Slave Tags are connected to Master Tag via a unique Join Token. On the other hand all Asset Tags need to connect to all 4 Slave Tags, each peer-to-peer connection shall use a unique link token. So what the asset tag needs to do is to set unique link token to Slave Tag 1 then try to link, change the unique link token to Slave Tag 2 then try to link, and so on.

    Hope this helps.

  • 0 in reply to Leo Hendrawan
    Intellectual 620 points

    Hi Leo,

    Thanks for your kind support.

    Actually Slave Tags are also configured as AP. Slave Tags will receive data from Asset Tags(ED) and will transmit those data to Master Tag(AP).

    To solve linking issue,I have used broadcasting method at Asset Tag(ED) side without using Linking method. So I can start Asset Tags at anytime.

    I am facing some other problems.

    1) The data of Asset Tags must be received by Slave Tags not received by master and data of Slave Tags must be received by master not received by Asset Tags(ED).

    How can I discard Asset Tag(ED)'s data in Master Tag(AP) and Slave Tag(AP)'s data in Asset Tag(ED)?

    2) What is the maximum value of MAX_APP_PAYLOAD and NUM_CONNECTIONS macro?

    Any help is appreciated.

    Thanks,

    Nipam