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.

Some questions about simpliciTI and TI wireless sensor monitor.

Other Parts Discussed in Thread: SIMPLICITI

Hello everyone!

I've been working with the "Ez430 wireless sensor monitor"  for some days, and many things caught my eye while using it. I use the Ez430-RF2500, and IAR 5.4.

Here are some questions I had while studying this code... If anyone could help, I would be extremely grateful!


1) The speed of wireless communication between an access point and an end device is way to slow (about 1 second!)... Is there a way to speed this things up? (Or control the velocity via software?)

2)  Would it be possible to connect a PC and the end device directly via the wireless board of the PC?

3) About those semaphores... How can we create more of them or destroy them all? I ask because I tried commenting all the sSelfSemaphore "if statement", and then erasing its declaration and also its calling in the ISR, and the program stopped working properly.

4) In which library are those commands "SMPL_send" and "SMPL_receive"?

5) Last question! When we send data, two of the arguments of the function SMPL_send are the "MSG" (the buffer where is the info we want to send) and the Lenght of the msg [which is 3]. However, when we receive this info (in the AP), We declare a MSG and a Lenght without sizes... How simpliciTI knows when the info is over?

 Thank you for your attention (and patience =P)!

  • Hi,

    I am not an expert on SimpliciTI, but I am working with this stack too and I try to help you where I am able to do it.

    1) Speed of radio communication is related with radio register configuration. This registers are in /mrfi/smartrf/your_radio/smartrf_your_radio.h. This file has a default configuration, but you can change the values using the software smartRT Studio provided by Texas Instruments, and substituting the old configuration.

    2) I don not understand you well in this. My advice, if you want to communicate ED and PC, use the serial port, but you have to implement it on ED code.

    3) These semaphores are flags, so you can create all you want if you need it. About destroy them, these semaphores, sJoinSem, sPeerFrameSem, etc, are dedicated to "say" what the main loop has to do, that is to say:

    * ) sJoinSem = there is a incoming  join frame, the AP has to listen to ED.

    *) sPeerFrameSem = there is a message to the AP, AP has to manage it.

    You can destroy them, but then, the code does not work properly, unless you create another flags with the same function.

    4) These two functions are in "nwk.api".

    5) Well, I do not know if you are talking about this, but the SMPL_Receive has the argument "len", according to documentation: "pointer to receive length of received message"

    Sorry for this later response, but i have missed this post in my  readings. I hope that it help you.

    Best regards.

**Attention** This is a public forum