https://devzone.nordicsemi.com/f/nordic-q-a/5754/gazell-ble-evaluationHi, I am evaluating the use of Gazell and BLE as a possible solution for my project. I had heard that there was a way to have both BLE and Gazell running on a device at the same time, however I have not found a demo that does this. There is a demo thaten-USTelligent Community 13Thu, 26 Nov 2015 15:28:20 GMThttps://devzone.nordicsemi.com/thread/20108?ContentTypeID=1Thu, 26 Nov 2015 15:28:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f752c15c-2a8a-462a-8db2-99d3e82492e5ovrebekk<p>I just made an example combining the ble_app_uart project with a Gazell device, using the timeslot API.</p> <p>You can find the example here:<br /> <a href="https://github.com/NordicSemiconductor/nrf51-ble-gzll-device-uart">https://github.com/NordicSemiconductor/nrf51-ble-gzll-device-uart</a></p> <p>You can have a look at it and do some testing if you like.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/20107?ContentTypeID=1Thu, 26 Feb 2015 13:17:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:447cc350-ed02-4d1b-91ce-d894aace207eAsbj&#248;rn<p>Yes, it is possible to have Gazell running in the timeslots. There&#39;s a NRF_GZLL_MODE_SUSPEND option available to have timers running when you are outside the time slots. This enables you to keep the links, but still live by the time slots that the softdevice give you.</p> <p>It works for both host and devices, but keep in mind that you will have to play by the time slots you are given. So if you have a lot of BLE traffic, Gazell will be limited by this.</p> <p>Average current consumptions is difficult to predict. It depends on how often you are in either receiver or transmit mode. This is what will bring your average up. Ballpark would be estimated as for 4 timeslots with RX and TX operations every second would add 30-40 uA to you average.</p><div style="clear:both;"></div>