CC1310: Stack 15.4 What are Non-Sleepy Devices that are Frequency Hopping and Usage?

Sanchitha Dias

Intellectual 795 points

Part Number: CC1310

Hi Guys,

1) Could I please know about NON-SLEEPY devices that are frequency hopping in STACK 15.4.

2) The usage of them.

3) Can this function be used to communicate in-between sensor devices (Mesh Networking) ?

over 7 years ago

0 YiKai Chen over 7 years ago

Guru 735685 points

As I know, TI 15.4 Stack doesn't support NON-SLEEPY device.

0 Sanchitha Dias over 7 years ago in reply to YiKai Chen

Intellectual 795 points

Hi Chen,

Ohh is that right..... So is it only for FH mode?

Thanks for the quick response Chen.

0 YiKai Chen over 7 years ago in reply to Sanchitha Dias

Guru 735685 points

As I know, TI 15.4 Stack doesn't support non-sleep device for all mode.

0 PrashanthS over 7 years ago in reply to YiKai Chen

TI__Expert 8765 points

Hello Sanchitha,
TI 15.4 g stack does support Sleepy and Non-Sleepy nodes. Both do Frequency hopping. A node can be made non-sleepy in a case where high throughput is required and or the response time has to be low at the cost of being always on. A non sleepy node does not have to poll the collector for data while the sleepy node polls for the data.

For more information refer to the documentation here.
dev.ti.com/.../TI 15.4-Stack Overview.html

3. TI 15.4g stack is star topology. It may be possible to make a non-sleepy device to act as a relay and do an additional hop that gears towards a mesh, that is some thing you can do on your own.

Regards,
Prashanth

0 YiKai Chen over 7 years ago in reply to PrashanthS

Guru 735685 points

Sanchitha Dias Sorry to give wrong information, I didn’t notice TI 15.4 Sensor supports nonsleepy mode. It seems that you can set ApiMac_attribute_RxOnWhenIdle to make it. PrashanthS is this correct?

0 Sanchitha Dias over 7 years ago in reply to PrashanthS

Intellectual 795 points

Thank you very much for your help Prashanth. That's what I was worried about achieving using STACK. Also if possible could you please guide me or provide me with a hint to look at what area in STACK implementation to change the existing protocol to add this extra protocol.

I believe this is direct Sensor to Sensor communication.

Regards,
Sanchitha.

0 Sanchitha Dias over 7 years ago in reply to YiKai Chen

Intellectual 795 points

That is alright Chen, There nothing to be worry as you have done for me. :D. Thank you.....

0 PrashanthS over 7 years ago in reply to Sanchitha Dias

TI__Expert 8765 points

Hello Sanchitha,

Direct sensor to sensor communication is possible. To achieve that one can specify the destination sensor address instead of the coordinator address in the API. This can be set in ApiMac_attribute_coordShortAddress. One can initiate a Asynchronous frame exchange for two non-sleepy sensor nodes to communicate with each other. dev.ti.com/.../ti154stack-overview.html

Regards,
Prashanth

0 Sanchitha Dias over 7 years ago in reply to PrashanthS

Intellectual 795 points

Hi Prashanth,

Exactly that's what I need to do. Does it mean that all the non sleepy devices should have an unique short address and everyone should aware of all the addresses?. Also could you please elaborate or specify the steps that I need to follow to achieve this.

Thanks again,
Kind Regards,
Sanchitha.

0 PrashanthS over 7 years ago in reply to Sanchitha Dias

TI__Expert 8765 points

Hello Sanchitha,

Are you talking about direct communication between two non sleepy nodes of the same PAN network or 2 different PAN networks? If it is the same one you should have the node address accessible. We did not explore much into implementing this, so I cannot say much about how it is done. Since the stack conforms to WISUN specifications such node to node communication is possible but was not implemented or tested. This is something you will have to do on your own if you decide to do so.

Regards,
Prashanth

0 Sanchitha Dias over 7 years ago in reply to PrashanthS

Intellectual 795 points

This is in the same network Prashanth. So as I have understood the address of the non-sleepy device is accessible from any sensor? Where it should be saved in the NV?. I have another question where is this possible to achieve with sleepy devices?.

Thank you very much Prashanth.
Kind Regards,
Sanchitha.

0 PrashanthS over 7 years ago in reply to Sanchitha Dias

TI__Expert 8765 points

Hello Sanchitha,

After talking to the design team, now I understand that each node has neighbor table with 3 entries. Nodes can communicate directly with only the nodes in these 3 entries. This table is in RAM, not in NV. I don't think this is possible with sleepy devices as they don't know when to be awake for communicating.
Can you give us information on what you are trying to achieve and why? This may aid us decide to add such features in future releases.

Regards,
Prashanth

0 Sanchitha Dias over 7 years ago in reply to PrashanthS

Intellectual 795 points

Hi Prashanth,

Thank you very much for your answer. That information means a lot.

Well my goal is to communicate between two Sleepy, Frequency Hopping devices (Sensor nodes) and I want it to consume lowest power as possible (uA's). But this isn't possible with a Non-Sleepy device. At least If I could find a method that turn off the RF Core, that would also be really helpful.

Kind Regards,
Sanchitha.

0 PrashanthS over 7 years ago in reply to Sanchitha Dias

TI__Expert 8765 points

Hello Sanchitha,

The power consumption is managed by the stack and it is already optimized for the lowest possible levels. The RF core operations on the TI 15.4g stack are at a lower level that is not accessible through the API.

Regards,
Prashanth

Sub-1 GHz

Sub-1 GHz forum

CC1310: Stack 15.4 What are Non-Sleepy Devices that are Frequency Hopping and Usage?