how to know sleep period of node(s110)

RE: how to know sleep period of node(s110)

FormerMember — Wed, 15 Jul 2015 11:49:25 GMT

k.thank you for your valuable comments....

RE: how to know sleep period of node(s110)

Wojtek — Wed, 15 Jul 2015 11:42:06 GMT

I am not really into iot sdk, cause i am using standard S110/120.

If Your radio is off and not maintaining connection for time longer than supervision time (it is set during connection parameteres negotiation), connection is terminated. I see no difference between not using radio for some time and turning it off and not using it anyway.

RE: how to know sleep period of node(s110)

FormerMember — Wed, 15 Jul 2015 11:33:05 GMT

i am not taling about that sleep time..which is time between two connection events....

i am talking about ,if the entire radio is off for some time (sleep),then upon wake up will it start advertising or will it directly connect to master...my use case is nrf 51 in iot(soft device) scenario...

RE: how to know sleep period of node(s110)

Wojtek — Wed, 15 Jul 2015 11:26:04 GMT

It will not terminate immediately, but device will wake up on RTC to maintain the connection. Here You can find better description:

devzone.nordicsemi.com/.../

also, read about connection supervision timeout if You are curious.

RE: how to know sleep period of node(s110)

FormerMember — Wed, 15 Jul 2015 11:18:11 GMT

Thank you for the answer... If the device is in sleeping mode,the link layer connection will terminate or still it maintain...

RE: how to know sleep period of node(s110)

Wojtek — Wed, 15 Jul 2015 10:16:47 GMT

It depends of how You will implement it. There is no pre-defied behavior, You have to write code that will handle this situation somehow. S130 can hold the data until destination s110 is available. Or it can discard it. Or it can... blink led. Depends of your code...
Sleeping means that nrf51 is in lower power consumption mode. It doesn't transmit/receive at the moment. It can return to normal work mode (wake up) by some interrupt (gpio, timer etc).When You wake up You can manually start advertising (or scanning if You are using central enabled softdevice...). There is no pre-defined automatic behavior. You have to write code.

Here You can find informations that could help start with Your developement: devzone.nordicsemi.com/.../

RE: how to know sleep period of node(s110)

FormerMember — Wed, 15 Jul 2015 10:05:23 GMT

my exact question is one s110 device wants to talk with another s110 device through s130 device. if first s110 device is sends data to s130 ,the s130 has to send the data to second s110,but the second s110 is sleeping.In this case what will happen..?

and one more doubt is.. sleeping means, the difference time between connection events only..? if the radio is off in sleeping period,will it start advertising again or it will directly talk with master(previously they connected and the device has gone to sleeping period for some time)...

RE: how to know sleep period of node(s110)

Wojtek — Wed, 15 Jul 2015 08:14:05 GMT

Peripheral (s110) cannot connect to other s110 anyway. If You want to use central/peripheral role in your "nodes" then You could try using s130 softdevice and switch between scanning/advertising.

About packets - it depends of what do You call a packet. If it is the advertising packeet, it will be lost automatically if no device is scanning at the moment of advertising. If You mean packets during connection - they will be immediately received be the peer.

You could try describe Your problem more precisely, or just check nordics example apps to understand what is the typical program flow.

RE: how to know sleep period of node(s110)

FormerMember — Wed, 15 Jul 2015 04:37:26 GMT

yes..that is correct but,some other peripheral wants to send the data to this peripheral,but this device is sleeping...in that case what will happen to packets..? how much time it will wait to send data to peripheral...?

RE: how to know sleep period of node(s110)

Wojtek — Tue, 14 Jul 2015 11:55:05 GMT

If Your peripheral is awake, You should put it in advertising state. Your central should be scanning (all the time maybe?), so You'll get event when it gets advert packet from peripheral.

Re-think Your roles - in my design it is peripheral who samples data - when it collects enough data it starts advertising, central immediately connects to it and peripheral sends collected data to central.