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.
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.
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.
