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: ultra low power wireless P2P connection

Other Parts Discussed in Thread: SIMPLICITI

Hi,

first of all - I have not used Simpliciti yet, just read several documents and sources and some questions arise:

It seems that typically one - always on - AP is required. How much power is required for this AP? What is his state most of the time? (my guess: receiver?). Is it possible to tell the AP (and all endpoints) that the AP is sleeping for the next e.g. 100ms and the endpoints transmit only when the AP is awoken?

What I want is a simple point-to-point connection with both tranceivers sleeping most of the time (both are battery powered). After both points have been synchronized they switch the tranceiver for e.g. 100ms  in sleep mode and wake up in fixed 100ms intervals to transfer some bytes and keep the sync. It should be possible to enlarge this period to one second or one minute ormuch longer. Is this possible with SimpliciTi?

In the approach above: I want to change the channels regularly on both sides (because of the crowed 2.4GHz band) eg: after 100ms: ch1, after 200ms: ch17 ,300ms ch:8 ... If there is noise at ch17 or no response, the same block will be retransmitted at ch 8 in the next interval (and so on until there is a free channel or a response). The channel tables are fixed and well known for  both points. Does SimpliciTi support this simple frequency hopping scheme?

 

Thx Leo

  • Hello.

    Actually, a simple point-to-point connection does not require an Access Point. The AP is required only in certain circumstances. See below.

    There is no provision in SimpliciTI for synchronizing peers that both can be sleeping. You would have to invent a scheme such as that you mention. But this is certainly possible.

    As for frequency "hopping" the way you describe it, in SimpliciTI this is called Frequency Agility. there is a application note on this in the code distribution.  Hopping implies a more complex, rapid channel change scheme that is not supported in SimpliciTI. For the Frequency Agility scheme that is implemented in SimpliciTI an AP is required. However, if you can solve the synchrony problem of two sleeping devices in principle you can coordinate the channels as well. There is nothing in the design of SimpliciTI prohibiting such an approach.

    The simplicity of SimplciTI allows you to invent all kinds of interesting schemes that do not enjoy native support in the protocol. This is accomplished by writing applications that provide the services the protocol lacks. You can use the Network Applications in SimpliciTI as models. The vision was to make it easy to establish peer-to-peer application connections with an infrastructure that provided some basic services. The framework was intended to be simple and fllexible, so the constrains are minimal.

    Hope this helps.

    lfriedman

     

  • Friedman,

    thank you for your response. That means I can use Simpicity as a basic frame to start with and implement my own wishes. (I wished there is a ready - made RF solution, without so much effort on my side ;-) Isn't there a market for lowest power point2point and reliable RF Links? Many applications came in my mind: wireless mouse and keyboard, cable replacement in sensor/meter applications and so on. I already tried simple RF-Link solutions, some of them need to much power on one or both sides, others do not work in noisy WLAN environments, because they use only one channel. I want to stay in the 2.45GHz band, because it is worldwide available without much changes as like in the 900MHz band.

    Leo